Folsom-Quantum-metadata server issue

Asked by vj

Installed Folsom services on a single node.
nova-compute/nova-api/nova-volume/Quantum/OpenVSwitch/l3-agent/dhcp-agent
I have turned off use_namespaces and Overlapping IPs to make the above configuration work like the traditional nova-network setup. I have configured metadata_host and metadata_port correctly in l3-agent.ini file.

In the console log, VM fails to access the metadata service.
wget: can't connect to remote host (169.254.169.254): No route to host

However, I am able to launch a VM. I am able to ping and ssh into the VM using private ip address. I am also able to ping/ssh from another VM using the private ip address.

Usually, n nova-network setup, if there is an error in accessing metadata service, it would result in ping/ssh FAILURE. With quantum, it seems to work.

Any clue to fix this issue is appreciated.

Thanks,
VJ

Question information

Language:
English Edit question
Status:
Answered
For:
neutron Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
yong sheng gong (gongysh) said :
#1

I don't think 'Usually, n nova-network setup, if there is an error in accessing metadata service, it would result in ping/ssh FAILURE. With quantum, it seems to work.'. ping relies on right networking on VM, and ssh relies on security group rule of nova and ssh server on VM. These features have no much relathionship with metadata service.

Revision history for this message
yong sheng gong (gongysh) said :
#2
Revision history for this message
yong sheng gong (gongysh) said :
#3

read http://docs.openstack.org/trunk/openstack-network/admin/content/adv_cfg_l3_agent_metadata.html
also please use:
linuxnet_interface_driver=nova.network.linux_net.LinuxOVSInterfaceDriver
firewall_driver=nova.virt.firewall.NoopFirewallDriver

so that nova's security rules will not block the metadata server's traffic.

Can you help with this problem?

Provide an answer of your own, or ask vj for more information if necessary.

To post a message you must log in.