metadata server and ip - relation?

asked 2013-06-27 04:49:37 -0500

digitaldolby2002 gravatar image


I have configured an multinode grizzly with controller, network and one compute node. I am not able to understand why my VM instance is trying to contact the IP May be i am missing somethinng obvious here. I am trying to find out the answer for the following.

I create a keypair and copy that to controller node. chmod the file to 600. Then i create the VM instance including this keypair and assiging an internal IP. Once the VM is up, i assign it a floating IP. At this stage i can ssh to the instance from my controller by injecting the key [ssh -i].

If this is the key which is used for accessing, what is the relevence of the VM trying to fetch from metadata server. My metadata host is given as my controller node itself. Then why its trying to connect to IP. What is my VM trying to fetch from the server with IP\

Can someone familiar with this try to help me understand this.

Regards, -Alex

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2013-06-28 01:36:23 -0500

fetahi gravatar image

Technically, I don't think there is any server listening on that IP address. In my setup, the IP address is forwarded by quantum to the quantum-metadata-proxy server which forwards the metadata queries to the nova-api server. Have a look at the iptables rules in the namespace of the tenant network. It should give you an idea of what is happening.

edit flag offensive delete link more


Ok.. I think i got more towards the actual stuff now: is kind of a magical IP of the metadataserver. In my case its the Controller node. At this IP a http server is provided to the instance from where the instance fetches the metadata. right?

digitaldolby2002 gravatar imagedigitaldolby2002 ( 2013-06-28 04:51:58 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-06-27 04:49:37 -0500

Seen: 2,496 times

Last updated: Jun 28 '13