Re: [Oscar-devel] RFC: UYOK option in "Setup Networking"?

Sat, 24 Jun 2006 19:30:41 -0700

Title: Re: [Oscar-devel] RFC: UYOK option in "Setup Networking"?
AutoInstall CD also works now - I changed the behaviour a bit so that it does not pop up an xterm and ask for which flavour of bootcd to create, instead, --flavor standard is hardcoded.
 
I will do a bit more testing and check it in once everybody had a chance to comment on it.
 
Cheers,
 
Bernard

From: [EMAIL PROTECTED] on behalf of Bernard Li
Sent: Sat 24/06/2006 17:46
To: [EMAIL PROTECTED]; [email protected]
Subject: Re: [Oscar-devel] RFC: UYOK option in "Setup Networking"?

Hi Erich, others:
 
I have just implemented my changes so that UYOK is integrated with OSCAR (at least with network boot, I still need to work on the AutoInstall CD...).  I haven't checked the changes in yet, but you can take a look at the screenshot :-)
 
I changed the behaviour so that instead of copying kernel and initrd.img, it symlinks them (/tftpboot/kernel and /tftpboot/initrd.img will be deleted first before symlinking...)
 
If the "Enable UYOK" radio button is pressed, then when you press "Setup Network Boot", si_prepareclient will run in the background to generate the kernel/ramdisk, and the UYOK files will be stored in /etc/systemimager/boot and they will be symlinked to /tftpboot (instead of /usr/share/systemimager/boot/$ARCH/standard).  /tftpboot/pxelinux.cfg/default will also be "fixed" so that ramdisk_size is 80000 (I don't know what this should be, but 80000 seems to work :P).
 
The UYOK setting is not saved, and needs to be enabled each time you run "Setup Network Boot".  And the kernel/initrd.img is re-generated each time, which doesn't take too much time...
 
I hope this works well with what Erich has in mind  - please let me know if you want anything changed.
 
Erich, do you plan to implement what you outlined (supporting multiple distro/arch netbooting) for 5.0 timeframe?  We need to decide soon what features to be included in 5.0 before the freeze.
 
Thanks,
 
Bernard

From: Erich Focht [mailto:[EMAIL PROTECTED]
Sent: Wed 21/06/2006 01:35
To: [email protected]
Cc: Bernard Li
Subject: Re: [Oscar-devel] RFC: UYOK option in "Setup Networking"?

Hi,

a related issue: since we now support multiple architectures and distros, we
actually can deploy any arch from the master node. SystemInstaller is halfways
prepared for that as it chooses what file to deliver first (pxelinux.0 or
elilo.efi) depending on the architecture. What we don't do yet is delivering
an arch dependent pxe-config file (called default right now), which selects
the kernel appropriate for the actual architecture.

My workaround was to use netbootmgr and create the appropriate links, having
  install-kernel-i386
  install-initrd-i386.img
  install-kernel-x86_64
  install-initrd-x86_64.img
  install-kernel-ia64
  install-initrd-ia64.img

With UYOK we get an additional variable into the game: the distribution from
which the own kernel emerged. So please consider some naming scheme for the
UYOK output which can coexist with other architectures/distros, and maybe
create a symlink to "kernel" and "initrd.img" for the master's arch.

Regards,
Erich


On Tuesday 20 June 2006 22:18, Bernard Li wrote:
> Mike:
>
> UYOK uses the kernel which the Linux distribution provides, so it's not
> really a "custom kernel".
>
> Basically instead of using the standard boot kernel/initrd.img which
> comes with SystemImager, it takes the running kernel of the image server
> and generate a initrd.img that works with SystemImager based on the
> intird_template for that architecture.
>
> Just thought I'd clarify this.
>
> Cheers,
>
> Bernard
>
> > -----Original Message-----
> > From: Michael Edwards [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, June 20, 2006 12:41
> > To: Bernard Li
> > Cc: [email protected]
> > Subject: Re: [Oscar-devel] RFC: UYOK option in "Setup Networking"?
> >
> > Yes, please, I think this is critically needed for many users.  Custom
> > kernels seem to be the norm in cluster computing, not the exception,
> > and making people drop out of oscar to deal with them seems silly.
> >
> > On 6/20/06, Bernard Li <[EMAIL PROTECTED]> wrote:
> > > I would like to add a new radio button in "Setup
> > Networking" to enable
> > > UYOK.
> > >
> > > For those of you who don't know what UYOK is, you can read about it
> > > here:
> > >
> > > http://svn.oscar.openclustergroup.org/trac/oscar/wiki/SystemImager
> > >
> > > Basically if that button is enabled, then a UYOK enabled
> > kernel/ramdisk
> > > will generated on the headnode and when the "setup network
> > boot" button
> > > is pressed, this kernel/ramdisk will be copied to /tftpboot
> > as opposed
> > > to the standard one which ships with SystemImager.
> > >
> > > This will also update /tftpboot/pxelinux.cfg/default's
> > append line with
> > > an appropriate ramdisk_size.
> > >
> > > Thoughts?  This won't be enabled by default, but would be
> > an easy point
> > > & click way for users to make use of UYOK.
> > >
> > > Cheers,
> > >
> > > Bernard

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to