openstack team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

On Tue, 22 May 2012, Jason Ford wrote:

> Scott,
>
> If you need someone to test your changes, I would be happy to do it. Please just give me some basic instructions on how to put it in place and I will get it working.
>
> As for your request for comments/features, personally I would like to see the following parts done initially:

I'm not sure of whether or not these things work in the status of these
things in fedora/RHEL.  I suspect that all below is true other than
disk space resize.  However, the following is true for ubuntu:

> - hostname set to instance name

 - hostname is set to whatever is in local-hostname of the metadata
   service. I think that actually does correlate to 'name' in the nova
   launch api.

> - disk space resize to flavor size

 - cloud-init runs resize2fs on the root partition on start up.  However,
   if you have a partition table on the disk, right now, that relies upon
   initramfs code delivered in cloud-initramfs-growroot [1] to grow the
   partition , and tell the kernel to re-read the partition while the
   filesystem is not mounted (otherwise you have to reboot).

   [1] https://launchpad.net/ubuntu/+source/cloud-initramfs-tools

> - ssh-key pull

 - cloud-init does that by default to the default user and adds it to the
   root user's .ssh/authorized_keys, with a message that says "you need to
   login as <the-configured-user>"

> - report a random password for root user (or default user) if this is possible

 - by default, cloud-init does not set a password for a user.  However, it
   can be told to via configuration (cloud-config in the image or passed
   in via userdata).  That looks like:
     password: RANDOM
   or
     chpasswd:
      list: |
        user1:password1
        user2:RANDOM
      expire: True
   There is more info at [2].

   [2] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config.txt
>
> Thanks for looking at this.
>
> jason
>
> ----- Original Message -----
> From: "Scott Moser" <smoser@xxxxxxxxxx>
> To: "Pádraig Brady" <P@xxxxxxxxxxxxxx>
> Cc: "Fedora Cloud SIG" <cloud@xxxxxxxxxxxxxxxxxxxxxxx>, "Andy Grimm" <agrimm@xxxxxxxxx>, "openstack" <openstack@xxxxxxxxxxxxxxxxxxx>
> Sent: Tuesday, May 22, 2012 12:51:42 PM
> Subject: Re: [Openstack] centos 6 images
>
> On Tue, 22 May 2012, Pádraig Brady wrote:
>
> > On 05/22/2012 03:39 PM, Andy Grimm wrote:
> > > On Tue, May 22, 2012 at 9:38 AM, Pádraig Brady <P@xxxxxxxxxxxxxx> wrote:
> > >> On 05/22/2012 04:07 AM, Jason Ford wrote:
> > >>> I am trying to put together an image for centos 6 that works like cloud-init on ubuntu does. Currently I have ssh keys getting imported but having some problems getting the disk to dynamically resize to the flavor template as well as the hostname set in horizon to be pushed into the image. Does anyone have any howtos or suggestions on how to get this done? Is there cloud-init for centos just like ubuntu? I would also be interested in how to do this with debian as well.
> > >>
> > >> Well I notice there is no cloud-init package for EPEL.
> > >> I took a quick stab at it here:
> > >> http://pbrady.fedorapeople.org/cloud-init-el6/
> > >
> > > I've already responded in IRC, but it wouldn't hurt to have a response
> > > in the mail archive.  In short, the reason there isn't already a
> > > cloud-init for EL6 (or EL5, for that matter) is that upstream has been
> > > using python 2.7-only calls for a while now.  In particular, a couple
> > > of calls to subprocess.check_output need to be replaced, and I think
> > > there are a few other issues as well.  I don't think it's a huge
>
> It would help if you'd bring that up with upstream :)
> I'm interested in cloud-init working in the most places it can.  I'll try
> to pull in the sysvinit scripts that Pádraig added and grab other changes
> that are there.
>
> > > amount of work to make it functional, but it hasn't been high on
> > > anyone's list.  It would be cool if you have time to fix / test it,
> > > though.
> >
> > Ok I've fixed the check_output calls at the above URL.
>
> If anyone has features / issues they'd like addressed in cloud-init,
> please feel free to ping me (smoser).  I'll most likely ask you to open a
> bug at http://bugs.launchpad.net/cloud-init , and may even invite you to
> submit a patch.  One way or another, though, I'm interested in making
> cloud-init better, so comments/concerns/participation is welcome and
> encouraged.
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>