Revision history [back]

click to hide/show revision 1
initial version

Maybe DNS - try pinging 8.8.8.8 from an instance. If that works you can set the dns_nameservers on private subnets and dhcp will push it out to the instances.

quantum subnet-update <subnet-of-net1-id> --dns_nameservers 8.8.4.4 8.8.8.8

Maybe DNS - try pinging 8.8.8.8 from an instance. If that works you can set the dns_nameservers on private subnets and dhcp will push it out to the instances.

quantum subnet-update <subnet-of-net1-id> --dns_nameservers 8.8.4.4 8.8.8.8

Update: after re-reading this it seems you have an all-in-one on an ESX-VM with a NIC with 172.25.27.5 and you want to use this same NIC for your floating IPs. The doc says that the NIC used for external access (connected to br-ex) should not have an IP.

http://docs.openstack.org/trunk/openstack-network/admin/content/install_quantum-l3.html

Maybe it is a DNS problem - try pinging 8.8.8.8 from an instance. If that works you can set the dns_nameservers on private subnets and dhcp will push it out to the instances.

quantum subnet-update <subnet-of-net1-id> --dns_nameservers 8.8.4.4 8.8.8.8

Update: after re-reading this it seems you have an all-in-one on an ESX-VM with a NIC with 172.25.27.5 and you want to use this same NIC for your floating IPs. The doc says that the NIC used for external access (connected to br-ex) should not have an IP.

http://docs.openstack.org/trunk/openstack-network/admin/content/install_quantum-l3.html

Update: The floating IPs and router_gateway showing status DOWN has been fixed here.