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.
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.
Thank you.
Joe V.
On Tue, Jul 17, 2012 at 12:03 PM, jvlcek jvlcek@redhat.com 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.
Once I have this pushed upstream I plan to push it to Fedora and then out to RHEL targeting release 6.4
Do you mean in RHEL itself or in EPEL? If cloud-init is going to make it into a RHEL channel then it would be useful if we could plan for that in advance.
See: BZ 838659 - https://bugzilla.redhat.com/show_bug.cgi?id=838659
Are we supposed to be able to see that bug? :-)
On 07/17/2012 04:49 PM, Garrett Holmstrom wrote:
On Tue, Jul 17, 2012 at 12:03 PM, jvlcek jvlcek@redhat.com 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.
Once I have this pushed upstream I plan to push it to Fedora and then out to RHEL targeting release 6.4
Do you mean in RHEL itself or in EPEL? If cloud-init is going to make it into a RHEL channel then it would be useful if we could plan for that in advance.
Yes the plan is to make it into the RHEL channel. We are just starting the planning now. It would be helpful to me if you could please pass along any input for the planning phase that you have.
See: BZ 838659 - https://bugzilla.redhat.com/show_bug.cgi?id=838659
Are we supposed to be able to see that bug? :-)
Sorry I hadn't realized that is internal.
That BZ is for planning for getting this into RHEL.
I'll check into making it public.
Also I know you are the fedora maintainer. Do you have any plans yet for updating the Fedora bits to newer upstream? I'd be glad to help with that.
Thank you again! Joe
On 2012-07-18 6:27, jvlcek wrote:
On 07/17/2012 04:49 PM, Garrett Holmstrom wrote:
On Tue, Jul 17, 2012 at 12:03 PM, jvlcek jvlcek@redhat.com wrote:
Once I have this pushed upstream I plan to push it to Fedora and then out to RHEL targeting release 6.4
Do you mean in RHEL itself or in EPEL? If cloud-init is going to make it into a RHEL channel then it would be useful if we could plan for that in advance.
Yes the plan is to make it into the RHEL channel. We are just starting the planning now. It would be helpful to me if you could please pass along any input for the planning phase that you have.
When porting things to new guests and clouds and whatnot it might be worth taking a look at the new extensions that the EC2 people made to cloud-config files in case anything new that people have to write can employ the same methods of configuration.
I will ask around for other input. I sincerely appreciate your mentioning this beforehand so we all have a chance to help out. :-)
See: BZ 838659 - https://bugzilla.redhat.com/show_bug.cgi?id=838659
Are we supposed to be able to see that bug? :-)
Sorry I hadn't realized that is internal.
That BZ is for planning for getting this into RHEL.
I'll check into making it public.
Thanks!
Also I know you are the fedora maintainer. Do you have any plans yet for updating the Fedora bits to newer upstream? I'd be glad to help with that.
Absolutely! Now that boto works again I can work on the bugfixes I was putting off. 8^)
On 07/19/2012 09:54 AM, Garrett Holmstrom wrote:
When porting things to new guests and clouds and whatnot it might be worth taking a look at the new extensions that the EC2 people made to cloud-config files in case anything new that people have to write can employ the same methods of configuration.
can you please provide some link / examples on these extensions? are they all based on userdata, or something else?
thanks, Itamar
On 2012-07-22 3:31, Itamar Heim wrote:
On 07/19/2012 09:54 AM, Garrett Holmstrom wrote:
When porting things to new guests and clouds and whatnot it might be worth taking a look at the new extensions that the EC2 people made to cloud-config files in case anything new that people have to write can employ the same methods of configuration.
can you please provide some link / examples on these extensions? are they all based on userdata, or something else?
Most of them are, yes. Amazon's documentation for it is in the EC2 user guide [1]. Unfortunately, it isn't as thorough as I thought it would be, but Scott *did* manage to fetch their source package and attach it to a Launchpad bug about integrating changes from Amazon's fork [2]. Most of their customizations revolve around package and repo management. The last time I looked, their code didn't really take advantage of cloud-init's existing module mechanism and configuration file, but regardless, it could be useful as inspiration.
[1] http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/AmazonLinuxAMIBasi... [2] https://bugs.launchpad.net/cloud-init/+bug/655837
Hi Joe,
This seems to be very much the right track for us, and the getting cloud-init in RHEL-proper would be great.
We are working on making cloud-init work on RHEL5, and hope to have something later this week.
cheers, Jan
PS: naive question - could cloud-init be made to work on Azure? This
On 07/17/2012 09: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.
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.
Thank you.
Joe V.
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
Thank you Jan!
Joe
On 07/18/2012 06:00 AM, Jan van Eldik wrote:
Hi Joe,
This seems to be very much the right track for us, and the getting cloud-init in RHEL-proper would be great.
We are working on making cloud-init work on RHEL5, and hope to have something later this week.
cheers, JanPS: naive question - could cloud-init be made to work on Azure? This
On 07/17/2012 09: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.
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.
Thank you.
Joe V.
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
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.
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.
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.
Joe
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.
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?
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
On 07/18/2012 10:42 PM, jvlcek wrote:
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?
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
iirc, the vm payload would appear as a file on the iso attached to the vm. the filename is something you set as part of the api call.
the api is documented here: http://wiki.ovirt.org/wiki/Features/VMPayload
From: jvlcek jvlcek@redhat.com 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
On 07/18/2012 11:57 PM, jrd@redhat.com wrote:
From: jvlcek <jvlcek@redhat.com> 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.
I expect customers to not replace overnight the DC virtualization just because 3.1 is released, so 3.0 will remain in the field for a while even if 3.1 replaces it for rpms, etc.
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
cloud@lists.stg.fedoraproject.org
-
Garrett Holmstrom -
iheim＠redhat.com -
Jan van Eldik -
Joseph VLcek -
jrd＠redhat.com