Kickstart a Fedora (Anaconda) Install on EC2
Raphaël De GIUSTI
raphael.degiusti at guardis.com
Tue Feb 8 14:07:56 UTC 2011
So if we put aside how the kickstart would be generated, what would be the
starting point in all of this ?
I was working with Centos55 when I made it to the partitioning phase (and I
don't really know why it went wrong), but I couldn't even get the F14 kernel
In other words :
- Which fedora kernel / initrd combination should I use in my grub.conf ?
- Should any of those two be altered in any way ?
I'm also willing to put some time in it if I may be useful... but like I
said I'm no expert.
On Wed, Feb 2, 2011 at 9:48 PM, Brian LaMere <brian at cukerinteractive.com>wrote:
> Maybe I'm missing something: why would you ever want an instance to
>> kickstart at boot time? You should create an image for every role you
>> care about and then boot the appropriate one for every instance you
> roles change, updates happen frequently, and I'd rather a machine spin up
> with the latest packages. I've always found that updating a pre-built
> machine is slower, sometimes substantially so, than just building a fresh
> image with the newest rpms.
> That said, some roles can (and often should) be fairly rigid and slow to be
> updated. But there's not much less of a need for flexible, dynamic builds
> in the cloud than there is in a local server room; do you build all new
> local servers based on a pre-built image that you just replicate? Would
> seem to negate the purpose of a kickstart server ;)
> cloud mailing list
> cloud at lists.fedoraproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cloud