Open Stack

Hello,

You need to configure the datasource for cloud-init to utilize EC2.

I've used the following in the past as part of our image build process to get around this:

echo "cloud-init cloud-init/datasources string NoCloud, OVF, Ec2" > /tmp/debconf-selections  
/usr/bin/debconf-set-selections /tmp/debconf-selections
rm -f /tmp/debconf-selections
apt-get -y install cloud-init

There may be more elegant ways to solve this problem but the above has worked for me.  YMMV.

---
Joseph Breu
Deployment Engineer
Rackspace Cloud Builders
210-312-3508

On Feb 29, 2012, at 12:47 AM, Lillie Ross-CDSR11 wrote:

> All,
> 
> I've built a custom image according to the various directions available in the nova docs.  The instance is loaded into glance and boots fine.  When building the image, openssh-server and cloud-init packages are installed.  So far so good.
> 
> However, when I start the image, cloud-init does not 'see' the EC2 datasource (i.e. the meta-data server), and reports back that it's only looking for the NoCloudNet and SourceOVFNet datasources when running in the 'cloud-init start' phase (versus start-local).  When I check the '/var/lib/cloud' directory, cloud-init is not setting up the instance link or populating the instance subdirectory under /var/lib/cloud/instances.
> 
> I'm able to connect to the meta-data service with no problem when logged into the running instance.  Obviously there's something I'm missing when configuring my custom image and installing the cloud-init package.  UEC images execute flawlessly (downloaded from Ubuntu).  
> 
> I feel like a broken record.  What am I missing?  Any pointers would be appreciated.
> 
> Regards,
> ross
> 
> 
> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp