As an alternative, you can configure nova to use "config drive". This will provide the metadata via disk as opposed to over your network.
On Wed, Jul 24, 2013 at 8:15 AM, Jacob Godin <[email protected]> wrote: > Hi Jake, > > You have to run the quantum-metadata-agent on your networking nodes (aka > where the l3-agent, l2-agent, and dhcp-agent run). > > > On Wed, Jul 24, 2013 at 7:21 AM, Jake G. <[email protected]>wrote: > >> This looks like it is for collection metadata for amazon ec2 instances. >> >> How does this relate to my instances on my Openstack environment? >> >> >> >> >> >> ------------------------------ >> *From:* Jake G. <[email protected]> >> *To:* Robert Collins <[email protected]> >> *Cc:* OpenStack Maillist <[email protected]> >> *Sent:* Wednesday, July 24, 2013 5:59 PM >> >> *Subject:* Re: [Openstack] Cloud-init Fails - No route to host. >> >> I can access the internet from my instance no problem. >> >> "- you might not have a neutron metadata-agent & proxy configured and >> running" >> This one might be the issue. Where should I look to configure this? >> >> >> ------------------------------ >> *From:* Robert Collins <[email protected]> >> *To:* Jake G. <[email protected]> >> *Cc:* OpenStack Maillist <[email protected]> >> *Sent:* Wednesday, July 24, 2013 5:55 PM >> *Subject:* Re: [Openstack] Cloud-init Fails - No route to host. >> >> On 24 July 2013 20:50, Jake G. <[email protected]> wrote: >> > I have an issue with the cloud-init process on boot of my instance. >> > >> > DataSourceEc2.py[WARNING]: >> > 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed >> [2/120s]: >> > url error [[Errno 113] No route to host] >> > >> > I am using this doc -> >> > >> http://docs.openstack.org/trunk/openstack-image/content/centos-image.html >> > >> > Why is this trying to contact a 3rd party server? Is this no longer a >> valid >> > IP address or URL? I cannot get a response from any machine I try. >> > Is the cloud-init actually necessary, if I am not using any aws >> services? >> >> The cloud-init address is used for dynamic configuration of your >> instances. >> >> Reasons it might fail: >> - you might not have a neutron metadata-agent & proxy configured and >> running >> - your networking might be misconfigured : if instance networking >> doesn't come up, you'll see that error. >> >> I suspect the latter issue is the problem. >> >> -- >> Robert Collins <[email protected]> >> Distinguished Technologist >> HP Cloud Services >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
