As I understand it, there's no grub in the ec2 instances because grub2 was not happy with the xen paravirtualized devices. And also it's not necessary.
Our instructions for OpenStack here https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova#Downloadi... have a little script for injecting syslinux as a bootloader so the images work with openstack.
A notable drawback is that kernel updates don't actually take effect without manual intervention. Plus, of course, if we don't start doing this ourselves, it means an extra annoying step for everyone.
It looks to me that more recent grub2 is patched to deal with the situation -- see https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/623609 and code in current grub-2.00/util/getroot.c.
Is there anything I'm missing here, and, what's the best way forward? (Grub in everything? Grub in images on mirrors, skip it in ec2?)
On Fri, Oct 12, 2012 at 3:47 PM, Matthew Miller mattdm@fedoraproject.org wrote:
Our instructions for OpenStack here https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova#Downloadi... have a little script for injecting syslinux as a bootloader so the images work with openstack.
We should probably rename and obsolete that page, it was for F16 when we didn't have publicly hosted Fedora image we could use with OpenStack. For F17 danpb created and provided Fedora image, updated instructions are here https://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17#R...
Is there anything I'm missing here, and, what's the best way forward? (Grub in everything? Grub in images on mirrors, skip it in ec2?)
I'd keep separate ec2 and non-ec2 Fedora cloud image, like http://cloud-images.ubuntu.com/precise/current/ kickstarts could have shared includes but leave them separate to allow small differences like this bootloader.
Cheers, Alan
On Fri, Oct 12, 2012 at 06:36:08PM +0200, Alan Pevec wrote:
We should probably rename and obsolete that page, it was for F16 when we didn't have publicly hosted Fedora image we could use with OpenStack. For F17 danpb created and provided Fedora image, updated instructions are here https://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17#R...
I think Daniel just basically did what the earlier instructions said and made it available. (Note that the F17 instructions point toward an F16 image.) That's a great start, but now we want to move to making it official.
Is there anything I'm missing here, and, what's the best way forward? (Grub in everything? Grub in images on mirrors, skip it in ec2?)
I'd keep separate ec2 and non-ec2 Fedora cloud image, like http://cloud-images.ubuntu.com/precise/current/ kickstarts could have shared includes but leave them separate to allow small differences like this bootloader.
Yeah, we want to do something like that anyway, at the very minimum because having a "launch" button is very slick.
Another consideration is that grub2 is not tiny. Doing something to automate syslinux installation (and figuring out updates with kernel updates?) is another path to think about.
On Fri, Oct 12, 2012 at 6:54 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Fri, Oct 12, 2012 at 06:36:08PM +0200, Alan Pevec wrote:
For F17 danpb created and provided Fedora image, updated instructions are here https://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17#R...
I think Daniel just basically did what the earlier instructions said and made it available. (Note that the F17 instructions point toward an F16 image.) That's a great start, but now we want to move to making it official.
Daniel built it from scratch with appliance-creator and patched F16 ec2 kickstart: http://berrange.fedorapeople.org/images/2012-02-29/f16-x86_64-openstack.ks Diff it aginst http://git.fedorahosted.org/cgit/cloud-kickstarts.git/plain/ec2/fedora-16-x8... to see the changes.
Cheers, Alan
On Fri, Oct 12, 2012 at 07:08:19PM +0200, Alan Pevec wrote:
Daniel built it from scratch with appliance-creator and patched F16 ec2 kickstart: http://berrange.fedorapeople.org/images/2012-02-29/f16-x86_64-openstack.ks Diff it aginst http://git.fedorahosted.org/cgit/cloud-kickstarts.git/plain/ec2/fedora-16-x8... to see the changes.
Thanks for that. Daniel, any comments on merging that in to the ec2 kickstart? It'd be nice if we could just have one. How much of the stuff removed will _hurt_ if left in for openstack et al?
On Fri, Oct 12, 2012 at 01:16:23PM -0400, Matthew Miller wrote:
On Fri, Oct 12, 2012 at 07:08:19PM +0200, Alan Pevec wrote:
Daniel built it from scratch with appliance-creator and patched F16 ec2 kickstart: http://berrange.fedorapeople.org/images/2012-02-29/f16-x86_64-openstack.ks Diff it aginst http://git.fedorahosted.org/cgit/cloud-kickstarts.git/plain/ec2/fedora-16-x8... to see the changes.
Thanks for that. Daniel, any comments on merging that in to the ec2 kickstart? It'd be nice if we could just have one. How much of the stuff removed will _hurt_ if left in for openstack et al?
I don't know really. I didn't try todo anything special with this image. I merely built it, booted it and verified I could ssh into it.
Regards, Daniel
On Fri, Oct 12, 2012 at 07:24:26PM +0100, Daniel P. Berrange wrote:
Thanks for that. Daniel, any comments on merging that in to the ec2 kickstart? It'd be nice if we could just have one. How much of the stuff removed will _hurt_ if left in for openstack et al?
I don't know really. I didn't try todo anything special with this image. I merely built it, booted it and verified I could ssh into it.
In that case, I'll try things and find out. Thanks.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El Fri, 12 Oct 2012 09:47:09 -0400 Matthew Miller mattdm@fedoraproject.org escribió:
As I understand it, there's no grub in the ec2 instances because grub2 was not happy with the xen paravirtualized devices. And also it's not necessary.
Our instructions for OpenStack here https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova#Downloadi... have a little script for injecting syslinux as a bootloader so the images work with openstack.
A notable drawback is that kernel updates don't actually take effect without manual intervention. Plus, of course, if we don't start doing this ourselves, it means an extra annoying step for everyone.
It looks to me that more recent grub2 is patched to deal with the situation -- see https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/623609 and code in current grub-2.00/util/getroot.c.
Is there anything I'm missing here, and, what's the best way forward? (Grub in everything? Grub in images on mirrors, skip it in ec2?)
I was planning to look at hvm images for f18 which would require grub2 be installed.
Dennis
-
Alan Pevec -
Daniel P. Berrange -
Dennis Gilmore -
Matthew Miller