Open Stack

Putting the ML back on the thread...

On 01/12/2014 07:20 AM, Rafael Gomes wrote:
> Hum ok. I understand. 
> 
> So it's normally that when I run a curl 169.254.169.254 or 169.254.169.254:8775
> from my VM I won't obtain answer? I ask this because right now when I execute
> the curl I don't have a answer from curl.

My typical test from a VM to see if metadata is working is to try and get this:

http://169.254.169.254/2009-04-04/meta-data/

That should always succeed, and will download an index.html file with all the
possible metadata pieces listed.

-Brian


>> Date: Thu, 9 Jan 2014 15:13:17 -0500
>> From: brian.haley at hp.com
>> To: rggg88 at hotmail.com
>> CC: openstack at lists.openstack.org
>> Subject: Re: [Openstack] Unable curl 169.254.169.254 from my VM (using neutron)
>>
>> On 01/09/2014 12:41 PM, Rafael Gomes wrote:
>> > Hi everyone, Sorry for bother you again. But now I have a question about
>> > metadata service when I launch a VM.
>> >
>> > The openstack instalation use a neutron to network and metadata service. I can
>> > launch a VM (image cirros), ping and access via ssh to VM. But when I try, from
>> > my VM, this curl 169.254.169.254:8775 I received this answer: couldn't connect
>> > to host
>>
>> Metadata requests from VMs should be sent on the "regular" http port, 80.
>>
>> Neutron uses a proxy process inside the router namespace that intercepts these
>> requests, sends them to an agent, who finally contacts the Nova api server on
>> port 8775. VMs don't have direct access to that.
>>
>> -Brian