Re: [SSI-users] State of OpenSSI on 2.6 / Debian Etch

[John H. <john@Calva.COM>]

skn...@we... wrote:
> Greetings, I admin a mid-sized Debian Sarge based OpenMOSIX cluster
>   
"Mid sized" means what?  I'm currently running a ~10 node cluster.
> and am investigating transitioning to an OpenSSI system since it is
> becoming difficult to add newer hardware with only a 2.4 kernel. OpenSSI
> stable also has this restraint, though I see a lot of work being done to get
> support for newer kernels. Specifically the packages for Etch here:
> http://www.atlantech.com/~john/openssi-etch/
>   
My real aim was to get the non-kernel stuff up to date (Etch & Lenny), 
the kernel is just Rogers work ported to 2.6.12 as Etch needs a udev 
that won't work on 2.6.11.
> I was wondering how far along OpenSSI actually is. For example, could
> OpenSSI on Debian Etch be used for a production cluster right now?
"production"?  I don't know.  I wouldn't bet my life or livelihood on it.
> Or would the resulting cluster be too crash happy?
I'd guess it depends on your applications.  See the sourceforge tracker 
for known bugs.
> If so, is there a timeline for when things might be suitable?
Uh, no.
> I don't need a lot of the higher-end features of OpenSSI, mainly just basic process migration
> as essentially it just has to do what OpenMOSIX does. I want to run this on Core Quad
> systems, so I need kernel 2.6.18 at the very least to support the
> hardware. 64-bit support would be very nice, but not necessary.
>   
Currently nothing newer than 2.6.12.

Why would you need 2.6.18 for the Core Quad?
> If I don't get a response I'll just have to try ;), but I thought I'd ask
> as well.
>   
Please feel free to try, more users generally means more bugs found, 
which should eventually lead to more bugs fixed.
> Possibly I could also get some time-saving tips, like the
> packages aren't good, but using the code from svn should be, etc. Our
> other main option is something like Platform LAVA, but I'd really prefer
> migration as opposed to a queue.
>   
For Etch, and kernel 2.6.12 you'll have to go with my packages for the 
moment.  (Source is, of course, available).