RE: [Oscar-devel] Re: [Sisuite-devel] Troubles with /dev/shm

Mon, 16 Jan 2006 11:30:10 -0800

Title: RE: [Oscar-devel] Re: [Sisuite-devel] Troubles with /dev/shm

My thoughts on this:

 

I’m sure others may have pre- and post-install scripts that are useful for cluster installation. Including them with OSCAR is a great idea, but I’d leave installation to manual efforts. I don’t like requiring installation of something I may not need.

 

As a future feature, you could add and remove these with a check-box in the OSCAR interface. We would just need to include standard line comments in each script for Display Name and Description. I have others I haven’t distributed, but I don’t believe are ready yet for public distribution, such Activate RSH, Swap MAC Addresses, and Cross-Mount Intel Cluster Tools.

 

Personally, I find these small, modular scripts the best method for cluster customization.

 

J-

 

From: Bernard Li [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 15, 2006 2:18 PM
To: Siadal, Jeremy C; [EMAIL PROTECTED]
Cc: Paul Greidanus; [email protected]; [EMAIL PROTECTED]
Subject: RE: [Oscar-devel] Re: [Sisuite-devel] Troubles with /dev/shm

 

What do you guys think?  Perhaps we should include these in our image's post-install script directory.

 

One question though, does /dev/shm exist on ALL distros?  For instance, does this exist on Mandriva systems?  Fernando?

 

I proposes that we create a directory under packages/sis called "sis-post-install" (or "package/sis/scripts/post-install" but I did not really want to mix these in with the SIS package scripts...).

 

In there, we put our (OSCAR) custom post-install scripts for SystemImager and we'll modify the post-server-install script to copy all the scripts in that directory to /var/lib/systemimager/scripts/post-install (we should probably do the same for pre-install).

 

This provides a nice mechanism for us to perform any out-of-systemimager customizations to the installation.

 

The e1000 script may potentially be useful too as it does provide better latency for HPC systems.

 

Comments?

 

Cheers,

 

Bernard

 

From: [EMAIL PROTECTED] on behalf of Siadal, Jeremy C
Sent: Fri 13/01/2006 18:10
To: [EMAIL PROTECTED]
Cc: Paul Greidanus; [email protected]
Subject: RE: [Oscar-devel] Re: [Sisuite-devel] Troubles with /dev/shm

Here are my two stock post-install scripts that I drop into the
/var/lib/systemimager/scripts/post-install subdirectory. One updates the
e1000 driver options (it can reduce latency by up to 70% on HPC
systems), and the other adds the /dev/shm entry to
modules/modprobe.conf.

For me, this works well enough for now.

> -----Original Message-----
> From: Erich Focht [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 13, 2006 6:46 AM
> To: Siadal, Jeremy C
> Cc: [email protected]; Paul Greidanus; oscar-
> [EMAIL PROTECTED]
> Subject: Re: [Oscar-devel] Re: [Sisuite-devel] Troubles with /dev/shm
>
> Hi Jeremy,
>
> On Thursday 12 January 2006 20:00, Siadal, Jeremy C wrote:
> > I've added the option (just like you have it below) as the last line
in
> > the file, OSCAR nodes couldn't image any more. Checking the
oscarmaster
> > script shows that when the /dev/shm option is added to the .disk
file,
> > SIS tries to install to the second physical hard drive. I think that
is
> > the same problem Paul had.
> >
> > To me, that is a real bug. If I need to add devices to the .disk
file,
> > OSCAR needs to interpret them in the correct order.
>
> that is a bug, indeed. I found that systeminstaller creates an entry
like
>
>         <disk dev="/dev/none" label_type="msdos"
unit_of_measurement="MB">
>         </disk>
>
> in the etc/systemimager/autoinstallscript.conf file inside the image.
>
> As a workaround: delete that <disk ..> </disk> block and regenerate
the
> autoinstallscript with si_mkautoinstallscript.
>
> I'll have a look at systeminstaller, and will also consider adding
> /dev/shm
> by default.
>
> Regards,
> Erich

Reply via email to