I woild assume that you would configure / build a new kernel for each hardware spec in your farm in your test environment, verify there are no glitches and then distibute the .config file to all servers and cron a kernel build / installation.
The reboot required for the servers would then be done during that server's maintenance window. On 2/11/08, Thilo Bangert <[EMAIL PROTECTED]> wrote: > Ramon van Alteren <[EMAIL PROTECTED]> said: > > Hi Thilo, > > > > Thilo Bangert wrote: > > | in the near future i am looking at installing gentoo onto a number of > > | hosts. i already have a buildhost preparing binary packages for the > > | clients - one of the missing pieces is the kernel install. > > | > > | i'd like to avoid having to compile a kernel on each and every host. > > | how do you install a prebuilt kernel onto the host, fx. after having > > | deployed a stage4 using quickstart? the best thing i can come up with > > | is writing my own custom script, which pulls a tarball via http. the > > | tarball has the modules, the initrd and the kernel... > > > > What's wrong with building your stage4 with catalyst and have it > > include a kernel ? > > and what do you do after a weekend like this one: kernel upgrade on 1300 > hosts? > > but you are right - i somehow missed that possibility. > > > > > We use catalyst to generate all our install images and catalyst uses > > genkernel internally to include it in the image. Just specify which > > kernel you'd like and provide a .config for it. > > > > We've installed 1300 servers that way, I'll personally guarantee you > > that it works :-D > > :) > thats more than good enough for me. > Thanks! > > > > > Regards, > > > > Ramon van Alteren > > kind regards > Thilo > -- [ Brandon Adams ] bmadams at gmail dot com -- [email protected] mailing list
