[MIR] cloud-init (grub-legacy-ec2)

Bug #605013 reported by Scott Moser
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: cloud-init

the grub-legacy-ec2 package is part of 'cloud-init'. It was developed (copied from grub with minimal changes) to write/maintain a /boot/grub/menu.lst on ec2 instances without conflicting with grub2. This work is done for the server-maverick-cloud-kernel-upgrades spec [2]. There is more information on how/why at the wiki document [3].

In brief, the UEC images are used as both a UEC guest and an EC2 guest. UEC uses kvm, and is able to use grub2 as a bootloader. On EC2, we are only able to use grub-legacy. The grub-0.97 package is unsuitable because:
a.) it conflicts with grub2
b.) some changes would be needed to deal with ec2/xen specific issues

bug 605001 is opened to add grub-legacy-ec2 to the UEC seed.

--
[1] http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.maverick/annotate/head:/uec
[2] https://blueprints.launchpad.net/ubuntu/+spec/server-maverick-cloud-kernel-upgrades
[3] https://wiki.ubuntu.com/ServerMaverickCloudKernelUpgrades

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: cloud-init 0.5.12-0ubuntu4
ProcVersionSignature: User Name 2.6.32-305.9-ec2 2.6.32.11+drm33.2
Uname: Linux 2.6.32-305-ec2 i686
Architecture: i386
Date: Tue Jul 13 13:07:41 2010
Ec2AMI: ami-82b65deb
Ec2AMIManifest: ubuntu-images-testing-us/ubuntu-maverick-daily-i386-server-20100710.manifest.xml
Ec2AvailabilityZone: us-east-1b
Ec2InstanceType: m1.small
Ec2Kernel: aki-078e676e
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cloud-init

Revision history for this message
Scott Moser (smoser) wrote :
description: updated
Scott Moser (smoser)
summary: - [MIR] cloud-init (legacy-grub-ec2)
+ [MIR] cloud-init (grub-legacy-ec2)
description: updated
Revision history for this message
Alexander Sack (asac) wrote :

moving to mterry who loves the cloud.

Changed in cloud-init (Ubuntu):
assignee: nobody → Michael Terry (mterry)
Revision history for this message
Michael Terry (mterry) wrote :

Scott, can you please provide the info from https://wiki.ubuntu.com/UbuntuMainInclusionRequirements?

I'll look at it a bit now, but that legwork would help.

Changed in cloud-init (Ubuntu):
assignee: Michael Terry (mterry) → Scott Moser (smoser)
status: New → Incomplete
Revision history for this message
Michael Terry (mterry) wrote :

Scratch that. Most of those requirements deal with ferreting out details about upstreams (true-upstream and Debian), which don't really apply here.

The package is relatively complicated, but seems necessarily so since it is a wedge into early boot and takes over from grub2. And it is needed and well maintained in Ubuntu. No important bugs (besides bug 565018 -- any update on that Scott?).

Oh, and debian/po/POTFILES.in refers to grub.templates, but should probably refer to grub-legacy-ec2.templates, right?

Approved, but please fix the POTFILES.in thing at least.

Changed in cloud-init (Ubuntu):
assignee: Scott Moser (smoser) → nobody
status: Incomplete → Fix Committed
Revision history for this message
Scott Moser (smoser) wrote :

cloud-init the binary package is already in main. The "complicated" bit of this source package is in the binary cloud-init package.
This main inclusion request is for "grub-legacy-ec2", which is a binary package put here for lack of any better place to put it.

The code in grub-legacy-ec2 is copied from the grub source package. I chose to copy the existing "update-grub" grub rather than write new code to do something that was already being done elsewhere. The copy was needed (rather than just installation of 'grub') because:
a.) i needed some ec2 specific changes
b.) 'grub' conflicts with grub-pc (grub 2) which is needed in the uec images for other reasons.

as far as modifying the strings "grub" to "grub-legacy-ec2", I just left that as it was in most places figuring it there was no benefit to changing it and would simply be changes I'd have to re-apply if I wanted to re-sync with the code from grub that was copied.

Revision history for this message
Scott Moser (smoser) wrote :

So, it appears that I dont need a main inclusion report for this after all. I had mis-read https://wiki.ubuntu.com/MainInclusionProcess to believe that i did.

Revision history for this message
Scott Moser (smoser) wrote :

Marking this invalid. I believe I just read the documentation wrong. Sorry for the confusion, no MIR of this new binary package should be needed.

Changed in cloud-init (Ubuntu):
status: Fix Committed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.