Revision history [back]

For now the acceptable solution seems to be :-

Setting up Multi-Node OpenStack RDO Havana + Gluster Backend + Neutron VLAN on CentOS 6.5 with both Controller and Compute nodes each one having two Ethernet adapters per Andrew Lau

http://bderzhavets.blogspot.ru/2013/12/attempt-to-reproduce-getting-started.html

Solutions on F20 not via packstack :-

http://kashyapc.fedorapeople.org/virt/openstack/neutron-configs-GRE-OVS-two-node.txt http://kashyapc.fedorapeople.org/virt/openstack/Two-node-Havana-setup.txt

For now the acceptable solution seems to be :-

Setting up Multi-Node OpenStack RDO Havana + Gluster Backend + Neutron VLAN on CentOS 6.5 with both Controller and Compute nodes each one having two Ethernet adapters per Andrew Lau

http://bderzhavets.blogspot.ru/2013/12/attempt-to-reproduce-getting-started.html

Solutions on F20 not via packstack :-

http://kashyapc.fedorapeople.org/virt/openstack/neutron-configs-GRE-OVS-two-node.txt http://kashyapc.fedorapeople.org/virt/openstack/Two-node-Havana-setup.txt

Please , view :-

“Setting up Two Physical-Node OpenStack RDO Havana + Gluster Backend for Cinder + Neutron GRE” on Fedora 20 boxes with both Controller and Compute nodes each one having one Ethernet adapter

and also Bugzilla report

For now the acceptable solution seems to be :-

Setting up Multi-Node OpenStack RDO Havana + Gluster Backend + Neutron VLAN on CentOS 6.5 with both Controller and Compute nodes each one having two Ethernet adapters per Andrew Lau

http://bderzhavets.blogspot.ru/2013/12/attempt-to-reproduce-getting-started.html

Solutions on F20 not via packstack :-

http://kashyapc.fedorapeople.org/virt/openstack/neutron-configs-GRE-OVS-two-node.txt http://kashyapc.fedorapeople.org/virt/openstack/Two-node-Havana-setup.txt

Please , view :-

“Setting up Two Physical-Node OpenStack RDO Havana + Gluster Backend for Cinder + Neutron GRE” on Fedora 20 boxes with both Controller and Compute nodes each one having one Ethernet adapter

and also Bugzilla report

For now as temporary workaround following steps help :-

Several restarts of services

# service openstack-nova-scheduler restart 
# service openstack-nova-conductor restart

Testing procedure here