openstack team mailing list archive
Mailing list archive
Re: Quantum - can't reach VMs, VMs can't reach metadata
Where are you pinging from? Displaying the ifconfig -a output on all nodes
could be useful.
Federal SE Team Lead
JNCIE-SP, BCNE, BCFP
Arista Networks, Inc.
Support: : 866-476-0000
On Thu, Jan 31, 2013 at 4:29 PM, Evan Todd <et1337@xxxxxxxxx> wrote:
> - Deployed with Juju
> - Folsom
> - Three nodes, all on the same network:
> - Quantum gateway running GRE tunnels (default supported by juju charm)
> - Cloud controller
> - Compute
> The gateway has another interface to a public network.
> I created a private logical network in quantum and booted a VM in it. I
> added SSH and ping rules to the security group. From the quantum gateway
> (or anywhere else), I can't ping it. Also, the VM log shows that it gets
> the correct IP address.
> ci-info: lo : 1 127.0.0.1 255.0.0.0 .
> ci-info: eth0 : 1 10.0.0.3 255.255.255.0 fa:16:3e:f0:bf:72
> ci-info: route-0: 0.0.0.0 10.0.0.1 0.0.0.0 eth0 UG
> ci-info: route-1: 10.0.0.0 0.0.0.0 255.255.255.0 eth0 U
> I also hadn't set up the metadata service yet since the juju charm doesn't install it. I tried installing it on the cloud controller and configuring the metadata_host on the quantum gateway to point to it. I still can't ping 169.254.169.254 from anywhere. Should that go on the quantum gateway itself instead?
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp