integrate changes from amazon

Bug #655837 reported by Scott Moser on 2010-10-06
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloud-init
Low
Unassigned

Bug Description

Amazon's linux image uses cloud-init: http://aws.amazon.com/amazon-linux-ami/ .

Amazon made changes to cloud-init to support their Fedora/CentOS base.

the changes should be integrated into cloud-init upstream.

I'm attaching the cloud-init srpm obtained with: get_reference_source -p cloud-init
from ami-3ac33653 (137112412989/amzn-ami-0.9.8-beta.i386-ebs) on 2010-10-06.

Scott Moser (smoser) wrote :
Scott Moser (smoser) wrote :
Scott Moser (smoser) on 2011-12-20
Changed in cloud-init:
importance: Medium → Low
Joshua Harlow (harlowja) wrote :

Looking at this, it seems like the 0.7.0 release covers most of the amazon changes (they added some sysvinit stuff, some yum install 'abstraction' as well, they adjusted subprocess exception throwing). They also added in a somewhat abstraction of yum/apt... They write out yum repo config files (thats different), and handle yum upgrades a little differently.... The 0.7.0 are more extensive (and imho better) so this bug might not be needed anymore...

Noteable additions:

1. It seems like they also can take base64 encoded userdata (from a response header??)

decoded_user_data = base64.urlsafe_b64decode(user_data)
                for header in valid_headers:
                    if decoded_user_data.startswith(header):
                        returned_data = decoded_user_data
                        break

2. It seems like they have a generic package install mechanism we might want to take (a config module):
   a) Look for file (in that rpm), cc_package_setup.py

3. Similarly they generate repo configs, in cc_genrepo.py (might be useful again)

flaccid (chris-xhost) wrote :

Which source did Debian use for what is in the current experimental repos?
We need one upstream source for all distributions to remove the forking.
smoser your assistance with this appreciated.

On Mon, 9 Jul 2012, flaccid wrote:

> Which source did Debian use for what is in the current experimental repos?
> We need one upstream source for all distributions to remove the forking.
> smoser your assistance with this appreciated.

debian used cloud-init 0.6.3 from launchpad.

I participated in that, and will continue to help there. I'm interested
in debian support working.

launchpad.net/cloud-init is most definitely the one upstream source.

Joshua Harlow (harlowja) wrote :

I think we are getting close to that goal of one upstream, the 0.7.0 work should be making this possible, its not 100% perfect yet, but its getting closer to that :-) Sysvinit scripts might also just work on debian as they exist right now...

flaccid (chris-xhost) wrote :

Thank you smoser and harlowja. I am going to build Debian 6.0.5 AMIs for all regions that use cloud-init from experimental and then we can see how it goes on a practical level for Debian (sysvinit not upstart still).
Really happy that this was ported back, I was never able to find time to do it, but hopefully can help with any bugs I might find from here.

Joshua Harlow (harlowja) wrote :

Sweet, I'll be out shortly but I know the sysvinit stuff works on RHEL6.2 (places the right symlinks at the right time in /etc/rc.X) so if that works for you all the better! Also don't forget to update the cloud.cfg to remove stuff that might be ubuntu specific (landscape module) and change the distro to 'debian' (although this really doesn't matter right now). cc_package_setup might be useful to have here (and should now be really easy, ie like a 20 line config module), same with cc_gen_repo....

Scott Moser (smoser) wrote :

Marking this "wont fix" for now.
Last I looked at Amazon's changes they were not relevant to current trunk, which runs now on rhel or fedora also.

Changed in cloud-init:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers