Re: [K12OSN] LTSP+OpenMosix

["James Jensen" <jmsjnsn linuxfreemail com>]

Richard:

Yeah, looking at my little LTSP+OpenMosix How-To (which someone has kindly
posted at http://k12ltsp.org/ltsp-om5.html) I've been thinking that
virtually all of the installation could be automated with a little shell
scripting or an RPM/tarball package as you suggested.  At the very least a
script could:

1. Automate the installation of the 2.4.16 kernel source
2. Patch it with OpenMosix
3. Copy the K12LTSP config file(s) to the kernel source
4. Compile the client kernel (using the "make oldconfig" option)
5. Copy the new kernel modules from /lib/modules to their equivalent in
/opt/ltsp/i386/lib/modules/
6. Copy the userland tools from their original location to their proper
home(s) in /opt/ltsp/i386...
7. Create the mosix.map files
8. Add the necessary lines to the dhcpd.conf file
9. Did I miss anything?

Well, basically a script that would do everything that I outlined only
automatically.  Should be a snap for an experienced shell programmer (not
me, sorry.  I could give it a go but who knows how long it would take me to
work it out properly with error trapping, etc.)

Anyway, I think that would bring things one step closer to the ideal.  Of
course the *most* ideal solution would be, again as you suggested, an RPM
that could be included in the K12LTSP ftp updates folder and/or as an option
in the next distribution release ;-)

On a side note, I have been running some stress testing on my little set up.
Failover looks like it will be an issue.  I started a stress test from the
P100 client and I knew that it had migrated to the PII client so I powered
off that box to see what would happen.  The stress test hung on the P100.
Maybe there is a way to incorporate failover that I am not aware of?  At any
rate it would probably be very problematic (and slightly traumatic) for a
user to lose his or her masterpiece Gimp project because the process was
running on another client and it got powered off.

However I don't think that should deter anyone from further investigation
into OpenMosix for two reasons:

1. There may be a way to implement failover so the process doesn't just hang
as in the experiment above and,

2. You could definitely employ a second (non-client) machine as an OpenMosix
server to take load off of the LTSP server.  Maybe you don't run an
OpenMosix kernel on the client terminals just on the two (three or four)
server boxes.  The 2nd+ OpenMosix "server" machines could be much less
expensive then the main LTSP server as they would not need HDD.  Set them to
Runlevel 3 and away they go, helping the rest of the systems to fly right
along.  If someone is going around punching the power button on your
servers, well, boot 'em out of the class or something!!!

Just some thoughts for your (and anyone else who is interested) review.

James

----- Original Message -----
From: "Richard Camp" <rcamp campworld net>
To: "James Jensen" <jmsjnsn linuxfreemail com>
Cc: <K12OSN redhat com>
Sent: Wednesday, March 27, 2002 10:02 PM
Subject: Re: [K12OSN] LTSP+OpenMosix


> James,
>
> Good to have some feedback.  SiS chipset/ide/video/sound failed to
> compile for me.  After removing them from my kernel build the auto
> installer worked fine.  Doesn't matter at this point.
>
> I found out the issues with the MOSIX project.  Needless to say I'm not
> pleased.  Hence,  the HOWTO as it pertains specifically to MOSIX will
> remain in its current state.  It will be left on my website for those
> who still wish to install MOSIX.
>
> Enter OpenMosix: (well at least K12ltsp has made installing the server
> easier)
>
> This weekend I will start working on version 2 of the howto featuring
> OpenMosix.  It looks like the install will be easier for people.  I hope
> to produce a ltsp kernel tarball and/or rpm package.
>
> The HOWTO and up and comming file are available on my website at
> http://www.campworld.net under the linux section.
>
> Thanks
> Richard Camp