openstack team mailing list archive

[jrd@xxxxxxxxxx]

>    From: jvlcek <jvlcek@xxxxxxxxxx>
>    Date: Wed, 18 Jul 2012 15:42:33 -0400
>    
>    On 07/18/2012 03:00 PM, Itamar Heim wrote:
>    > On 07/18/2012 09:47 PM, jvlcek wrote:
>    >> On 07/18/2012 01:47 PM, Itamar Heim wrote:
>    >>> On 07/17/2012 10:03 PM, jvlcek wrote:
>    >>>>
>    >>>> I just wanted to let folks know what is happening regarding cloud-init
>    >>>> support for RHEVm and vSphere and what OSs.
>    >>>>
>    >>>> Currently cloud-init only supports Ec2. A version is available
>    >>>> for Fedora and EPEL.
>    >>>>
>    >>>> I am working on updating upstream to also support sourcing
>    >>>> user data for RHEVm and vSphere, using the same technique we do
>    >>>> with Audrey from a Delta-Cloud launch.
>    >>>
>    >>> Can you please provide some more background on this?
>    >>> which feature set of cloud-init do you see this covering and how would
>    >>> the information will be passed (I assume some would be via the vm
>    >>> payload).
>    >>> but going forward, i was envisioning for ovirt/rhev to better
>    >>> integrate with cloud-init via something like the meta data service (vm
>    >>> payload of type network).
>    >>>
>    >>> so there is custom vm payload, which integration via the current
>    >>> payload mechanism would be great (since it will be the userdata for
>    >>> network payload as well).
>    >>> but for some things, iiuc cloud-init correctly, they are not supposed
>    >>> to be via userdata, rather via specific named fields.
>    >>>
>    >>> Thanks,
>    >>>     Itamar
>    >>>
>    >>>>
>    >>>> Once I have this pushed upstream I plan to push it to Fedora and then
>    >>>> out to RHEL targeting release 6.4
>    >>>>
>    >>>> See: BZ 838659 - https://bugzilla.redhat.com/show_bug.cgi?id=838659
>    >>>>
>    >>>> Please let me know if this plan conflicts with any known needs or
>    >>>> if I am on the right track.
>    >>>
>    >>
>    >>
>    >> I am adding a new data source to cloud-init allowing user data to be
>    >> picked up by
>    >> cloud-init running on a launching RHEVm and vSphere instance the same
>    >> way we
>    >> currently do for Audrey as launched from DeltaCloud.
>    >
>    > why are you using the floppy method for rhev and not the iso one?
>    > (I hope you are using 3.1 vm payload feature rather than the custom
>    > hook approach)?
>    >
>    >>
>    >> That being: on RHEVm the user data is made available via floppy  and on
>    >> vSphere
>    >> via a cdrom.
>    >>
>    >> I am not familiar with what you are envisioning for ovirt/rhev. How soon
>    >> would that
>    >> ovirt/rhev pieces be available? Perhaps we should discuss enhancing what
>    >> I am doing
>    >> and when that could happen.
>    >
>    > this will take at least a few months.
>    
>    MFojtik and/or Lutter;
>      see below question regarding Delta-Cloud support for RHEVm3.1
>    
>    Itamar,
>    
>    I have been using the floppy method as the 3.1 iso method was not available
>    when I started working on this.
>    
>    A RHEVm3.1 test system was set up just a few days ago in Westford
>    which I could start to use for testing the iso method.
>    
>    Do you think it makes sense to support both or just move to supporting only
>    3.1 iso method for Cloud-Init?

My 2 kopeks is that we should go with what we got now (3.0 support)
then treat 3.1 as an enhancement, possibly fairly soon.  Unless
somebody (Itamar?) thinks that 3.0 will dissapear entirely once 3.1 is
available, we're going to want it to work with both anyhow.  This way,
you can get the support for RHEV and Vsphere in, and stabilized, then
deal with the enhancement later.

>    
>    Is support for the RHEVm3.1 iso method available in Delta-Cloud?
>    (cc-ing Delta-Cloud)
>    
>    Can you point me at examples of how  the instance will access the data
>    from the 3.1 iso method?
>    
>    Thank you for the help and input!
>        Joe
>    
>    
>    
>