openstack team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

On Wed, 24 Jul 2013, Jake G. wrote:

> Thanks Scott!
>
> I have removed cloud-init from my instance and enabled config-drive in the nova.conf file.

I don't think I suggested you remove cloud-init.
Just enable config drive and cloud-init will use that instead of the ec2
metadata service.  You really do not want to remove cloud-init.


>
> Anything else I should take notice of?

As others have pointed out, the fact that your instances can't reach the
metadata service shows that at least *something* is not functioning
correctly on your installation.
>
>
> ________________________________
>  From: Scott Moser <smoser@xxxxxxxxxx>
> To: Jake G. <dj_dark_junglist@xxxxxxxxx>
> Cc: Dean Troyer <dtroyer@xxxxxxxxx>; "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, July 25, 2013 10:58 AM
> Subject: Re: [Openstack] Image prep. cloud-init user configuration help.
>
>
> On Wed, 24 Jul 2013, Jake G. wrote:
>
> > I got the user correct now I am wondering why this is nessasary for my environment.
> > I am not using Amazon EC2 services so why would I need to get metadata from there API?
> >
> > Can someone explain?
>
> Cloud-init uses the "datasource" of the EC2 Metadata service, that
> Openstack provides a workalike for.
> That metadata service has things like "instance-id" and "hostname" that
> are useful.  cloud-init uses instance-id for "run-once-per-instance"
> functionality.
>
> cloud-init also gets user-data from the datasource, and that is very
> useful for initializing images with information provided at launch time by
> the user.
>
> If you enable config-drive in openstack, then cloud-init will find the
> same data above from the config-drive, and wont bother looking for the ec2
> metadata service.
>
> Scott