openstack team mailing list archive

[Jean-Daniel BUSSY <silversurfer972@xxxxxxxxx>]

Hi stackers,

I have deployed a fully working multi-host cluster with 3 hosts featuring
quantum with gre network:

   1.  controller
   2.  network
   3.  compute

For various reasons I would like to achieve the ​ retrieval of the VM
metadata directly on the compute node.
For this I have nova-api-metadata installed in the compute node and I have
confirmed that the service is listening on port 8775.

# netstat -tulpen | grep 8775
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN
     108        51549236    3091/python

I can see the VM host request when tapping all the interfaces.
So by entering the following routing rule I should have request from
169.254.169.254:80 routed to localhost:8775

​iptables -t nat -A PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport
80 -j REDIRECT --to-port 8775​

​By doing so I don't see packets on port 8775 and ​nova-api-metadata log is
not outputting anything.

My nova.conf is : https://gist.github.com/bussyjd/5269214

My questions are:

   - Am I missing something simple here?
   - Is nova-api-metadata really functioning as metadata server on my
   compute host? (seems not to be the cause of the problem but just checking).
   - Is there any plan for Grizzly to have the routing of the metadata
   request on the localhost automatically set when nova-api-metadata is
   present ?
   - Why my routing rule doesn't apply here?

​Regards,​


*BUSSY Jean-Daniel*