ssic-linux-users Mailing List for OpenSSI Clusters for Linux (Page 9)
Brought to you by:
brucewalker,
rogertsang
You can subscribe to this list here.
| 2003 |
Jan
(17) |
Feb
(23) |
Mar
(32) |
Apr
(48) |
May
(51) |
Jun
(23) |
Jul
(39) |
Aug
(47) |
Sep
(107) |
Oct
(112) |
Nov
(112) |
Dec
(70) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(155) |
Feb
(283) |
Mar
(200) |
Apr
(107) |
May
(73) |
Jun
(171) |
Jul
(127) |
Aug
(119) |
Sep
(91) |
Oct
(116) |
Nov
(175) |
Dec
(143) |
| 2005 |
Jan
(168) |
Feb
(237) |
Mar
(222) |
Apr
(183) |
May
(111) |
Jun
(153) |
Jul
(123) |
Aug
(43) |
Sep
(95) |
Oct
(179) |
Nov
(95) |
Dec
(119) |
| 2006 |
Jan
(39) |
Feb
(33) |
Mar
(133) |
Apr
(69) |
May
(22) |
Jun
(40) |
Jul
(33) |
Aug
(32) |
Sep
(34) |
Oct
(10) |
Nov
(8) |
Dec
(18) |
| 2007 |
Jan
(14) |
Feb
(3) |
Mar
(13) |
Apr
(16) |
May
(15) |
Jun
(8) |
Jul
(20) |
Aug
(25) |
Sep
(17) |
Oct
(10) |
Nov
(8) |
Dec
(13) |
| 2008 |
Jan
(7) |
Feb
|
Mar
(1) |
Apr
(6) |
May
(15) |
Jun
(22) |
Jul
(22) |
Aug
(5) |
Sep
(5) |
Oct
(17) |
Nov
(3) |
Dec
(1) |
| 2009 |
Jan
(2) |
Feb
|
Mar
(29) |
Apr
(78) |
May
(17) |
Jun
(3) |
Jul
|
Aug
|
Sep
(1) |
Oct
(21) |
Nov
(1) |
Dec
(4) |
| 2010 |
Jan
(1) |
Feb
(5) |
Mar
|
Apr
(5) |
May
(7) |
Jun
(14) |
Jul
(5) |
Aug
(72) |
Sep
(25) |
Oct
(5) |
Nov
(14) |
Dec
(12) |
| 2011 |
Jan
(9) |
Feb
|
Mar
|
Apr
(3) |
May
(3) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(10) |
Aug
(18) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
| 2013 |
Jan
(1) |
Feb
(3) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Scott W. <sc...@sl...> - 2010-06-25 18:09:45
|
On 6/25/10, Cumberland, Lonnie <lon...@ni...> wrote: > Hello All, > > In step 10 of the > > http://openssi.org/cgi-bin/view?page=openssi.html > > It says to: > > "Add the module for your cluster-interconnect nic to /etc/mkinitrd/modules > (You can find out what it is by doing: > ls -ld /sys/class/net/ethX/device/driver/module > where "ethX" is the nic you want to use). " > > How do I do this? > > I found out that the module is "e1000" Add the line to /etc/mkinitrd/modules. Mine has these in it: 3c59x 8139too 3c509 I also kept the comment at the top reminding me to run mkinitrd after changing the file. Machines on the cluster net-boot and mount the cluster filesystem as their root filesystem, and this file tells the initnode which network modules it needs to include in for the netbooting hosts so that they can get the network up and mount the cluster filesystem. The modules listed in there get built into the /boot/initrd-* (for your kernel version) file. After editing that file and doing mkinitrd, I also like to do ssi-ksync to make sure all of the netbooting apparatus is updated and in order. Thanks, -scott |
|
From: Cumberland, L. <lon...@ni...> - 2010-06-25 18:02:35
|
Hello Scott, In my last attempt (a few moments ago) I simply added the e1000 to the modules file but forgot to run mkinitrd. Once rebooted, the system does not boot up and falls out with an error message. Looks like I will have to restart the whole process again and see. Thanks and have a great day, Lonnie Cumberland, Prof. Physicist National Institute of Standards and Technology Ionizing Radiation Division (846) Radiation Physics Group (245), Room C106 ADDRESS: 100 Bureau Drive, Stop 8462 Gaithersburg, MD 20899-8462 EMAIL: lon...@ni... http://physics.nist.gov/Divisions/Div846/div846.html -----Original Message----- From: Scott Walters [mailto:sc...@sl...] Sent: Friday, June 25, 2010 1:47 PM To: Cumberland, Lonnie Cc: Roger Tsang; ssi...@li... Subject: Re: [SSI-users] LinuxSSI x86_64 bit On 6/25/10, Cumberland, Lonnie <lon...@ni...> wrote: > Hello All, > > In step 10 of the > > http://openssi.org/cgi-bin/view?page=openssi.html > > It says to: > > "Add the module for your cluster-interconnect nic to /etc/mkinitrd/modules > (You can find out what it is by doing: > ls -ld /sys/class/net/ethX/device/driver/module > where "ethX" is the nic you want to use). " > > How do I do this? > > I found out that the module is "e1000" Add the line to /etc/mkinitrd/modules. Mine has these in it: 3c59x 8139too 3c509 I also kept the comment at the top reminding me to run mkinitrd after changing the file. Machines on the cluster net-boot and mount the cluster filesystem as their root filesystem, and this file tells the initnode which network modules it needs to include in for the netbooting hosts so that they can get the network up and mount the cluster filesystem. The modules listed in there get built into the /boot/initrd-* (for your kernel version) file. After editing that file and doing mkinitrd, I also like to do ssi-ksync to make sure all of the netbooting apparatus is updated and in order. Thanks, -scott |
|
From: Cumberland, L. <lon...@ni...> - 2010-06-25 17:38:10
|
Hello All, In step 10 of the http://openssi.org/cgi-bin/view?page=openssi.html It says to: "Add the module for your cluster-interconnect nic to /etc/mkinitrd/modules (You can find out what it is by doing: ls -ld /sys/class/net/ethX/device/driver/module where "ethX" is the nic you want to use). " How do I do this? I found out that the module is "e1000" Thanks and have a great day, Lonnie Cumberland, Prof. Physicist National Institute of Standards and Technology Ionizing Radiation Division (846) Radiation Physics Group (245), Room C106 ADDRESS: 100 Bureau Drive, Stop 8462 Gaithersburg, MD 20899-8462 EMAIL: lon...@ni...<mailto:lon...@ni...> http://physics.nist.gov/Divisions/Div846/div846.html ________________________________ From: Roger Tsang [mailto:rog...@gm...] Sent: Thursday, June 24, 2010 8:32 PM To: Cumberland, Lonnie Cc: ssi...@li... Subject: Re: [SSI-users] LinuxSSI x86_64 bit Hi, http://openssi.org/cgi-bin/view?page=openssi.html Recent News OpenSSI 1.9.6 x86_64 Preview Released<http://deb.openssi.org/openssi/dists/1.9.6-lenny-preview/> OpenSSI is quite transparent to user space; we don't modify existing ABI's. So this practically means you can install any software in your OpenSSI cluster as if you were installing on a "single system" - you only need to perform the software install once. The OpenSSI cluster will immediately see the install. -Roger On Thu, Jun 24, 2010 at 8:57 AM, Cumberland, Lonnie <lon...@ni...<mailto:lon...@ni...>> wrote: Hello All, I am new to LinuxSSI and have been investigating XtreemOS and OpenSSI as possible options for a 30-node cluster (4Ghz Xeons) that we have just physically put together. I came across the OpenSSI site and have downloaded the "OpenSSI 1.2.0+ for KNOPPIX 3.6" but did not see a 64-bit version and also was not sure how to easily add additional packages and tools to the OS. Any information that could be provided would be greatly appreciated. Thanks and have a great day, Lonnie Cumberland, Prof. Physicist National Institute of Standards and Technology Ionizing Radiation Division (846) Radiation Physics Group (245), Room C106 ADDRESS: 100 Bureau Drive, Stop 8462 Gaithersburg, MD 20899-8462 EMAIL: lon...@ni...<mailto:lon...@ni...> http://physics.nist.gov/Divisions/Div846/div846.html ________________________________ ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Ssic-linux-users mailing list Ssi...@li...<mailto:Ssi...@li...> https://lists.sourceforge.net/lists/listinfo/ssic-linux-users |
|
From: Cumberland, L. <lon...@ni...> - 2010-06-25 14:48:45
|
Greetings Scott and Roger, I thank you for responding to my post and have been working my way through the documentation for the installation but just ran into a small problem while setting up the head node. Everything ran fine up until the point when it asked me to reboot the system in step number 18. I am getting the message: " ERROR: could not find NIC with a static node configured. Dynamically allocating an IP and node number. Could not find the NIC used to add this node to the cluster. Unable to continue. Halting. " On this node which will be the head node, I have network cards (one for the static public IP "eth0" and one for the interconnect NIC which I assigned a static IP of 192.168.0.1 "eth1") Since the system is not booting and I cannot seem to get to a command prompt, does this mean that I will have to re-install everything from scratch and try again? Thanks and have a great day, Lonnie Cumberland, Prof. Physicist National Institute of Standards and Technology Ionizing Radiation Division (846) Radiation Physics Group (245), Room C106 ADDRESS: 100 Bureau Drive, Stop 8462 Gaithersburg, MD 20899-8462 EMAIL: lon...@ni... http://physics.nist.gov/Divisions/Div846/div846.html -----Original Message----- From: Scott Walters [mailto:sc...@sl...] Sent: Thursday, June 24, 2010 11:14 AM To: Cumberland, Lonnie Cc: ssi...@li... Subject: Re: [SSI-users] LinuxSSI x86_64 bit Hi Lonnie, At http://openssi.org/cgi-bin/view?page=openssi.html, there is an x86_64 preview release for Debian at the top of the list of releases. I personally haven't used it; I'm running the 32 bit version at the moment. The install process is a bit involved and, in my experience, likely to go wrong due to changes in Debian that have happened since the OpenSSI release was prepared. Knowing your way around Linux is essential. I'm in Ohio at YAPC, the Perl conference right now. I gave a talk on scaling Plack (a Perl version of the Rack Web interface/toolkit idea) applications using OpenSSI. Perl's thread interface is also implemented by a module that's implemented in terms of forked processes using IPC. This is one option for writing a distributed cache without the programming overhead of memcached. I wrote Plack middleware for doing session affinity (keeping user's sessions on the same host) which is necessary for frameworks based on coroutines (keeping execution contexts around for users). Plack worker-processes can be automatically or manually migrated. One of these, I need to go do some editing in the Wiki, but one tip: don't count on the network hardware in your machines being supported. I bought a pile of older 3COM 3c509 style cards off of eBay, but my machines are mostly non-uniform so far. Good luck and let the list know if you get stuck. Cheers, -scott On 0, "Cumberland, Lonnie" <lon...@ni...> wrote: > > Hello All, > > > I am new to LinuxSSI and have been investigating XtreemOS and OpenSSI > as possible options for a 30-node cluster (4Ghz Xeons) that we have > just physically put together. > > > I came across the OpenSSI site and have downloaded the "OpenSSI 1.2.0+ > for KNOPPIX 3.6" but did not see a 64-bit version and also was not > sure how to easily add additional packages and tools to the OS. > > > Any information that could be provided would be greatly appreciated. > > > Thanks and have a great day, > > Lonnie Cumberland, Prof. > > Physicist > > > National Institute of Standards and Technology > > Ionizing Radiation Division (846) > Radiation Physics Group (245), Room C106 > > ADDRESS: > > 100 Bureau Drive, Stop 8462 > Gaithersburg, MD 20899-8462 > > > EMAIL: [1]lon...@ni... > [2]http://physics.nist.gov/Divisions/Div846/div846.html > ______________________________________________________________________ > > References > > 1. mailto:lon...@ni... > 2. http://physics.nist.gov/Divisions/Div846/div846.html > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users |
|
From: Roger T. <rog...@gm...> - 2010-06-25 00:31:45
|
Hi, http://openssi.org/cgi-bin/view?page=openssi.html Recent News OpenSSI 1.9.6 x86_64 Preview Released<http://deb.openssi.org/openssi/dists/1.9.6-lenny-preview/> OpenSSI is quite transparent to user space; we don't modify existing ABI's. So this practically means you can install any software in your OpenSSI cluster as if you were installing on a "single system" - you only need to perform the software install once. The OpenSSI cluster will immediately see the install. -Roger On Thu, Jun 24, 2010 at 8:57 AM, Cumberland, Lonnie < lon...@ni...> wrote: > Hello All, > > > > I am new to LinuxSSI and have been investigating XtreemOS and OpenSSI as > possible options for a 30-node cluster (4Ghz Xeons) that we have just > physically put together. > > > > I came across the OpenSSI site and have downloaded the “*OpenSSI 1.2.0+ > for KNOPPIX 3.6*” but did not see a 64-bit version and also was not sure > how to easily add additional packages and tools to the OS. > > > > Any information that could be provided would be greatly appreciated. > > > > Thanks and have a great day, > > Lonnie Cumberland, Prof. > > Physicist > > > > National Institute of Standards and Technology > > Ionizing Radiation Division (846) > Radiation Physics Group (245), Room C106 > > ADDRESS: > > 100 Bureau Drive, Stop 8462 > Gaithersburg, MD 20899-8462 > > > > EMAIL: lon...@ni... > http://physics.nist.gov/Divisions/Div846/div846.html > ------------------------------ > > > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > |
|
From: Cumberland, L. <lon...@ni...> - 2010-06-24 12:57:21
|
Hello All,
I am new to LinuxSSI and have been investigating XtreemOS and OpenSSI as possible options for a 30-node cluster (4Ghz Xeons) that we have just physically put together.
I came across the OpenSSI site and have downloaded the "OpenSSI 1.2.0+ for KNOPPIX 3.6" but did not see a 64-bit version and also was not sure how to easily add additional packages and tools to the OS.
Any information that could be provided would be greatly appreciated.
Thanks and have a great day,
Lonnie Cumberland, Prof.
Physicist
National Institute of Standards and Technology
Ionizing Radiation Division (846)
Radiation Physics Group (245), Room C106
ADDRESS:
100 Bureau Drive, Stop 8462
Gaithersburg, MD 20899-8462
EMAIL: lon...@ni...<mailto:lon...@ni...>
http://physics.nist.gov/Divisions/Div846/div846.html
________________________________
|
|
From: John H. <jo...@Ca...> - 2010-05-14 08:48:42
|
Scott Walters wrote: > Was there a fork at some point with development happening > concurrently on the 1.9.x branch and the 2.0.x branch? Or is > the Debian work just lagging in cluster software version? > The "cluster software" (libcluster and so on) hasn't needed any major changes for quite some time. Most of the interesting work has been in ther kernel. > http://wiki.openssi.org/go/Roadmap partially answers that question > (2.0.0preX reserved for kernel 2.6.18 or higher). > In fact 2.0 is going to be 2.6.11 based. We'll move to more recent kernels after 2.0. > I'm pretty sure I installed 1.9.6 for Debian Lenny (x86), but > `cluster -r` reports: "This is cluster software release 1.9.3". > That's kind of tangential, but I can't help wondering if that can > easily be accounted for. > It's really just the version of the "cluster" command. > `cluster -m` reports 15, and I'm approaching that number of machines > here. Also, one of the photos at http://wiki.openssi.org/go/Showcase > kind of suggests that clusters with more nodes exist. Can this limit > be easily increased in config? I thought I read somewhere that > the 1.2 stable branch had a similarly low limit but newer 1.9 versions > allowed for hundreds of machines in the cluster. > > Do I (currently) need to run the Fedora Core version to throw nodes at this? > The cluster tools are (distribution differences aside) identical between the Debian and FC versions. > I'm continuously in awe of OpenSSI. Thank you for your work and > for your attention. > Aw, shucks. |
|
From: John H. <jo...@Ca...> - 2010-05-14 08:44:44
|
Roger Tsang wrote: > Hi Scott, > > 2.0.0pre2 is an older release - aka 1.9.5 - where as 2.0.0pre1 is > equivalent to 1.9.4. 2.0.0pre1 was released after 1.9.3. > > Our development mailing list mentioned that there were many changes > since 2.0.0pre2 (1.9.5). For this reason the latest work today is > called 1.9.6 "preview" instead of 2.0.0pre3. > > 1.9.6 "preview" is just that - not really a release. After some final > touches 1.9.6 "preview" (or actually the latest in CVS) will become > 2.0.0rc1. > > There will no longer be any confusion since 2.0.0rc1 naturally follows > after 2.0.0pre2. I'm really bad at version numbers and releases. And there are a lot of different version numbers. There is the version of the kernel, the version of the OpenSSI modifications to the kernel, the version of libcluster and the cluster tools, the versions of the patches to the base utilities. My "1.9.6 preview" stuff is based on whatever Roger checks in to CVS - as he says he's working towards a nice stable "2.0". Roger, please correct me if I'm wrong, but my understanding is: The 2.0 kernel will be based on what Roger is putting in to CVS, on base kernel 2.6.11 The Debian version will be based on Sarge. The "Redhat/Fedora" version will be based on CentOS 4.8 When 2.0 is wrapped up we'll start work on a 2.1. The main aim of 2.1 will be to move to newer kernels and distributions. |
|
From: Roger T. <rog...@gm...> - 2010-05-14 05:13:53
|
Hi Scott, 2.0.0pre2 is an older release - aka 1.9.5 - where as 2.0.0pre1 is equivalent to 1.9.4. 2.0.0pre1 was released after 1.9.3. Our development mailing list mentioned that there were many changes since 2.0.0pre2 (1.9.5). For this reason the latest work today is called 1.9.6 "preview" instead of 2.0.0pre3. 1.9.6 "preview" is just that - not really a release. After some final touches 1.9.6 "preview" (or actually the latest in CVS) will become 2.0.0rc1. There will no longer be any confusion since 2.0.0rc1 naturally follows after 2.0.0pre2. If I'm not mistaken existing releases (other than 1.9.6 "preview") have a limit of 126 nodes. This limit was optimized to 15 nodes in 1.9.6 "preview" for mid-size clusters. A patch is required to revert that. Bruce and Jaideep (from HP Labs) talked about scaling out to hundreds or thousands of nodes - PetaScale OpenSSI. -Roger On Thu, May 13, 2010 at 2:57 PM, Scott Walters <sc...@sl...> wrote: > Hi all, > > (Trying again with a subject line... third time's the charm they say...) > > >From http://openssi.org/cgi-bin/view?page=openssi.html : > > # OpenSSI 1.9.6 Preview Updated > * version for Debian Lenny i386 updated 2010/02/18 > * version for Debian Lenny updated 2010/01/07 > * version for Debian Etch updated 2010/01/07 > > ... > > # OpenSSI 2.0.0pre2 Now Available > * version for Fedora Core 3 released 2008/01/03 > > Roughly, what are the differences between 1.9.6 and 2.0.0pre2? > > Was there a fork at some point with development happening > concurrently on the 1.9.x branch and the 2.0.x branch? Or is > the Debian work just lagging in cluster software version? > > http://wiki.openssi.org/go/Roadmap partially answers that question > (2.0.0preX reserved for kernel 2.6.18 or higher). > > I'm pretty sure I installed 1.9.6 for Debian Lenny (x86), but > `cluster -r` reports: "This is cluster software release 1.9.3". > That's kind of tangential, but I can't help wondering if that can > easily be accounted for. > > `cluster -m` reports 15, and I'm approaching that number of machines > here. Also, one of the photos at http://wiki.openssi.org/go/Showcase > kind of suggests that clusters with more nodes exist. Can this limit > be easily increased in config? I thought I read somewhere that > the 1.2 stable branch had a similarly low limit but newer 1.9 versions > allowed for hundreds of machines in the cluster. > > Do I (currently) need to run the Fedora Core version to throw nodes at > this? > > I'm continuously in awe of OpenSSI. Thank you for your work and > for your attention. > > Regards, > -scott > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > |
|
From: Scott W. <sc...@sl...> - 2010-05-13 18:57:40
|
Hi all, (Trying again with a subject line... third time's the charm they say...) >From http://openssi.org/cgi-bin/view?page=openssi.html : # OpenSSI 1.9.6 Preview Updated * version for Debian Lenny i386 updated 2010/02/18 * version for Debian Lenny updated 2010/01/07 * version for Debian Etch updated 2010/01/07 ... # OpenSSI 2.0.0pre2 Now Available * version for Fedora Core 3 released 2008/01/03 Roughly, what are the differences between 1.9.6 and 2.0.0pre2? Was there a fork at some point with development happening concurrently on the 1.9.x branch and the 2.0.x branch? Or is the Debian work just lagging in cluster software version? http://wiki.openssi.org/go/Roadmap partially answers that question (2.0.0preX reserved for kernel 2.6.18 or higher). I'm pretty sure I installed 1.9.6 for Debian Lenny (x86), but `cluster -r` reports: "This is cluster software release 1.9.3". That's kind of tangential, but I can't help wondering if that can easily be accounted for. `cluster -m` reports 15, and I'm approaching that number of machines here. Also, one of the photos at http://wiki.openssi.org/go/Showcase kind of suggests that clusters with more nodes exist. Can this limit be easily increased in config? I thought I read somewhere that the 1.2 stable branch had a similarly low limit but newer 1.9 versions allowed for hundreds of machines in the cluster. Do I (currently) need to run the Fedora Core version to throw nodes at this? I'm continuously in awe of OpenSSI. Thank you for your work and for your attention. Regards, -scott |
|
From: Scott W. <sc...@sl...> - 2010-05-13 18:12:12
|
Hi all, >From http://openssi.org/cgi-bin/view?page=openssi.html : # OpenSSI 1.9.6 Preview Updated * version for Debian Lenny i386 updated 2010/02/18 * version for Debian Lenny updated 2010/01/07 * version for Debian Etch updated 2010/01/07 ... # OpenSSI 2.0.0pre2 Now Available * version for Fedora Core 3 released 2008/01/03 Roughly, what are the differences between 1.9.6 and 2.0.0pre2? Was there a fork at some point with development happening concurrently on the 1.9.x branch and the 2.0.x branch? Or is the Debian work just lagging in cluster software version? http://wiki.openssi.org/go/Roadmap partially answers that question (2.0.0preX reserved for kernel 2.6.18 or higher). I'm pretty sure I installed 1.9.6 for Debian Lenny (x86), but `cluster -r` reports: "This is cluster software release 1.9.3". That's kind of tangential, but I can't help wondering if that can easily be accounted for. `cluster -m` reports 15, and I'm approaching that number of machines here. Also, one of the photos at http://wiki.openssi.org/go/Showcase kind of suggests that clusters with more nodes exist. Can this limit be easily increased in config? I thought I read somewhere that the 1.2 stable branch had a similarly low limit but newer 1.9 versions allowed for hundreds of machines in the cluster. Do I (currently) need to run the Fedora Core version to throw nodes at this? I'm continuously in awe of OpenSSI. Thank you for your work and for your attention. Regards, -scott |
|
From: John H. <jo...@Ca...> - 2010-05-07 08:50:33
|
Scott Walters wrote: > Hi John, > > Mis-type. /etc/dhcpd3/dhcpd.proto, on my recent install, specifies > log-facility: local7. Yup, it's an actual bug. We'll have to check what the log-facility is set to on OpenSSI install, and maybe re-check on ssi-addnode. (I just couldn't understand what on earth your initial bug report was going on about). |
|
From: John H. <jo...@Ca...> - 2010-05-06 21:10:49
|
A little more detail please. What are you trying to do? Install OpenSSI preview on Debian Lenny? How far have you got, what exactly is not working? I don't see any /etc/dhcpd3/dhcpd.info under Lenny. If you want help could you please write to the mailing list. |
|
From: John H. <jo...@Ca...> - 2010-04-24 12:40:19
|
By the way (and as an aide-memoire for me) one of the more irritating
results of the failure of migration on the x86_64 port is that ssi-ksync
doesn't work.
The workaround is to do:
onall ssi-ksync -l
|
|
From: John H. <jo...@Ca...> - 2010-04-10 09:07:14
|
Arthur Turrini wrote: > What's actual project status? > Missing developers? We don't have many developers at the the moment (Roger Tsang is the main kernel developer, I take care of the Debian port). |
|
From: Arthur T. <at...@gm...> - 2010-04-10 00:57:23
|
What's actual project status? Missing developers? On Thu, Apr 8, 2010 at 5:57 AM, John Hughes <jo...@ca...> wrote: > Shane wrote: > > I was reading in the notes on the 'downloads' section of the website > that OpenSSI is only good for Fedora, Debian, and Red Hat 9. Are those > set in stone or would it run on other linux flavors as well? I have 3 > small clusters that I've been using for a while for my software and > none of them are of the supported flavors listed by OpenSSI. (I have > OSX, RHE, and Gentoo). > > > OpenSSI uses some modified versions of the base packages of the OS (for > example, I've attached the list for Debian Sarge). > > If you want to install OpenSSI on some other OS you have to port the > OpenSSI changes to the other OS. > > The hard part is dealing with the cascading dependencies - The "official" > OpenSSI kernel is based on 2.6.11, and so can't use a udev newer than 0.056 > or so. I've ported the OpenSSI patches to 2.6.14 (with some known bugs), so > we can use up to udev 0.80. The version of udev in Debian Lenny requires > at least kernel 2.6.18. > > Many packages require a more modern udev - as I downgrade the Debian Lenny > version from 0.125 to 0.80 I have to provide a few out of date packages to > make Lenny work - see > http://deb.openssi.org/openssi/dists/1.9.6-lenny-preview/extras > > If you want to try OpenSSI I seriously recommend using one of the supported > distributions. Personally I think that the Debian version is the easiest to > install, and the Debian Lenny based distribution is the most "up to date". > > If you want to get an idea what OpenSSI is like without messing up one of > your working clusters try installing OpenSSI under a virtual monitor: KVM, > QEMU, Xen (HVM only at the moment). > > (I'm writing this message from an OpenSSI cluster where some of the nodes > are running in Xen HVM virtual machines. I do most of my testing in > clusters built from QEMU virtual machines). > > OpenSSI packages for Debian Sarge: > > am-utils_6.0.9-3.2.ssi1.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/am-utils_6.0.9-3.2.ssi1.tar.gz> 12-Oct-2008 > 09:24 1.4M cluster-tools_1.9.3-0.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/cluster-tools_1.9.3-0.tar.gz> 12-Oct-2008 > 08:38 278K devfsd_1.3.25-19.ssi2.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/devfsd_1.3.25-19.ssi2.tar.gz> 12-Oct-2008 > 09:17 65K dpkg_1.10.28.ssi1.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/dpkg_1.10.28.ssi1.tar.gz> 12-Oct-2008 > 09:21 2.1M drbd0.7.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/drbd0.7.tar.gz> 12-Oct-2008 > 09:23 126K drbd_0.7.24-1.ssi2.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/drbd_0.7.24-1.ssi2.tar.gz> 12-Oct-2008 > 09:23 287K e2fsprogs_1.37-2sarge1.ssi2.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/e2fsprogs_1.37-2sarge1.ssi2.tar.gz> 12-Oct-2008 > 09:17 3.4M initrd-tools_0.1.81.1.ssi2.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/initrd-tools_0.1.81.1.ssi2.tar.gz> 12-Oct-2008 > 09:21 33K kernel-ssi-latest-2.6-i386_102.ssi2.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/kernel-ssi-latest-2.6-i386_102.ssi2.tar.gz> 12-Oct-2008 > 09:27 3.6K logrotate_3.7-5.ssi1.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/logrotate_3.7-5.ssi1.tar.gz> 12-Oct-2008 > 09:21 50K netdump_0.6.11-1.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/netdump_0.6.11-1.tar.gz> 12-Oct-2008 > 09:23 40K nfs-utils_1.0.6-3.1.ssi1.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/nfs-utils_1.0.6-3.1.ssi1.tar.gz> 12-Oct-2008 > 09:23 263K openssi-tools_1.9.3-3.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/openssi-tools_1.9.3-3.tar.gz> 12-Oct-2008 > 09:17 541K portmap_5-9.ssi2.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/portmap_5-9.ssi2.tar.gz> 12-Oct-2008 > 09:23 27K procps_3.2.1-2.ssi3.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/procps_3.2.1-2.ssi3.tar.gz> 12-Oct-2008 > 09:22 289K strace_4.5.8-1.2.ssi2.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/strace_4.5.8-1.2.ssi2.tar.gz> 12-Oct-2008 > 09:22 631K sysvinit_2.86.ds1-1.ssi3.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/sysvinit_2.86.ds1-1.ssi3.tar.gz> 12-Oct-2008 > 09:20 176K udev_0.056-3.ssi1.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/udev_0.056-3.ssi1.tar.gz> 12-Oct-2008 > 09:27 500K util-linux_2.12p-4sarge1.ssi3.tar.gz<http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/util-linux_2.12p-4sarge1.ssi3.tar.gz> 12-Oct-2008 > 10:48 2.0M > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > |
|
From: John H. <jo...@Ca...> - 2010-04-08 08:59:57
|
Shane wrote: > I was reading in the notes on the 'downloads' section of the website > that OpenSSI is only good for Fedora, Debian, and Red Hat 9. Are those > set in stone or would it run on other linux flavors as well? I have 3 > small clusters that I've been using for a while for my software and > none of them are of the supported flavors listed by OpenSSI. (I have > OSX, RHE, and Gentoo). > OpenSSI uses some modified versions of the base packages of the OS (for example, I've attached the list for Debian Sarge). If you want to install OpenSSI on some other OS you have to port the OpenSSI changes to the other OS. The hard part is dealing with the cascading dependencies - The "official" OpenSSI kernel is based on 2.6.11, and so can't use a udev newer than 0.056 or so. I've ported the OpenSSI patches to 2.6.14 (with some known bugs), so we can use up to udev 0.80. The version of udev in Debian Lenny requires at least kernel 2.6.18. Many packages require a more modern udev - as I downgrade the Debian Lenny version from 0.125 to 0.80 I have to provide a few out of date packages to make Lenny work - see http://deb.openssi.org/openssi/dists/1.9.6-lenny-preview/extras If you want to try OpenSSI I seriously recommend using one of the supported distributions. Personally I think that the Debian version is the easiest to install, and the Debian Lenny based distribution is the most "up to date". If you want to get an idea what OpenSSI is like without messing up one of your working clusters try installing OpenSSI under a virtual monitor: KVM, QEMU, Xen (HVM only at the moment). (I'm writing this message from an OpenSSI cluster where some of the nodes are running in Xen HVM virtual machines. I do most of my testing in clusters built from QEMU virtual machines). OpenSSI packages for Debian Sarge: am-utils_6.0.9-3.2.ssi1.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/am-utils_6.0.9-3.2.ssi1.tar.gz> 12-Oct-2008 09:24 1.4M cluster-tools_1.9.3-0.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/cluster-tools_1.9.3-0.tar.gz> 12-Oct-2008 08:38 278K devfsd_1.3.25-19.ssi2.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/devfsd_1.3.25-19.ssi2.tar.gz> 12-Oct-2008 09:17 65K dpkg_1.10.28.ssi1.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/dpkg_1.10.28.ssi1.tar.gz> 12-Oct-2008 09:21 2.1M drbd0.7.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/drbd0.7.tar.gz> 12-Oct-2008 09:23 126K drbd_0.7.24-1.ssi2.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/drbd_0.7.24-1.ssi2.tar.gz> 12-Oct-2008 09:23 287K e2fsprogs_1.37-2sarge1.ssi2.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/e2fsprogs_1.37-2sarge1.ssi2.tar.gz> 12-Oct-2008 09:17 3.4M initrd-tools_0.1.81.1.ssi2.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/initrd-tools_0.1.81.1.ssi2.tar.gz> 12-Oct-2008 09:21 33K kernel-ssi-latest-2.6-i386_102.ssi2.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/kernel-ssi-latest-2.6-i386_102.ssi2.tar.gz> 12-Oct-2008 09:27 3.6K logrotate_3.7-5.ssi1.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/logrotate_3.7-5.ssi1.tar.gz> 12-Oct-2008 09:21 50K netdump_0.6.11-1.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/netdump_0.6.11-1.tar.gz> 12-Oct-2008 09:23 40K nfs-utils_1.0.6-3.1.ssi1.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/nfs-utils_1.0.6-3.1.ssi1.tar.gz> 12-Oct-2008 09:23 263K openssi-tools_1.9.3-3.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/openssi-tools_1.9.3-3.tar.gz> 12-Oct-2008 09:17 541K portmap_5-9.ssi2.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/portmap_5-9.ssi2.tar.gz> 12-Oct-2008 09:23 27K procps_3.2.1-2.ssi3.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/procps_3.2.1-2.ssi3.tar.gz> 12-Oct-2008 09:22 289K strace_4.5.8-1.2.ssi2.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/strace_4.5.8-1.2.ssi2.tar.gz> 12-Oct-2008 09:22 631K sysvinit_2.86.ds1-1.ssi3.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/sysvinit_2.86.ds1-1.ssi3.tar.gz> 12-Oct-2008 09:20 176K udev_0.056-3.ssi1.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/udev_0.056-3.ssi1.tar.gz> 12-Oct-2008 09:27 500K util-linux_2.12p-4sarge1.ssi3.tar.gz <http://deb.openssi.org/openssi/dists/1.9.6-sarge/openssi/source/util-linux_2.12p-4sarge1.ssi3.tar.gz> 12-Oct-2008 10:48 2.0M |
|
From: Shane <sof...@gm...> - 2010-04-08 02:57:05
|
I was reading in the notes on the 'downloads' section of the website that OpenSSI is only good for Fedora, Debian, and Red Hat 9. Are those set in stone or would it run on other linux flavors as well? I have 3 small clusters that I've been using for a while for my software and none of them are of the supported flavors listed by OpenSSI. (I have OSX, RHE, and Gentoo). |
|
From: Benjamin V. <ben...@wi...> - 2010-02-09 14:47:14
|
It would be nice to target RHEL/CentOS 6 release as a base in the future. I initially intended to port the userland stuff to CentOS 5, however a lot has changed in the Linux world since it was originally released and I prefer saving my energy for a more current release. Fedora, IMO, is not a viable solution as a long-term platform, since they spit out at least 2 releases every year. It would be impossible to keep up without the manpower. I also wondered if you guys have any intention of submitting the SSI stuff for inclusion with the kernel? Also, one might consider updating openssi.org. It is quite a dissuasive to see the most recent news to be from 2006. Nobody really knows if the project is still alive, unless you sign up to the mailing list. Just my 2 cents.. ;) Regards, - Ben On Tue, 2010-02-09 at 12:20 +0100, John Hughes wrote: > Mulyadi Santosa wrote: > > AFAIK, OpenSSI development is a little bit "stalled" right now. > > Probably this is due to lack of time in the OpenSSI team itself. > Well, also due to the size of the "team". > > The problem with openSSI porting toward newer distro is not just about > > kernel issue, it also touches userland tools too. > The userland side isn't too hard, it's just a lot of fiddly work. > > Thus, it demands > > larger effort than porting something like openMosix (now RIP). Not to > > mention the QA effort > > > > Thus, as conclusion, I think you are tied with rather old distro if > > you want to implement OpenSSI. > Debian Lenny isn't that old. > > You could also consider Kerrighed, but > > last time I visit its website, it's still based on 2.6.20. > > > > Hopefully you can draw your own decision after looking at the facts above. > > > > > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users |
|
From: John H. <jo...@Ca...> - 2010-02-09 11:18:11
|
Mulyadi Santosa wrote: > AFAIK, OpenSSI development is a little bit "stalled" right now. > Probably this is due to lack of time in the OpenSSI team itself. Well, also due to the size of the "team". > The problem with openSSI porting toward newer distro is not just about > kernel issue, it also touches userland tools too. The userland side isn't too hard, it's just a lot of fiddly work. > Thus, it demands > larger effort than porting something like openMosix (now RIP). Not to > mention the QA effort > > Thus, as conclusion, I think you are tied with rather old distro if > you want to implement OpenSSI. Debian Lenny isn't that old. > You could also consider Kerrighed, but > last time I visit its website, it's still based on 2.6.20. > > Hopefully you can draw your own decision after looking at the facts above. > > |
|
From: John H. <jo...@Ca...> - 2010-02-09 11:15:29
|
Charles Def wrote: > I would like to run Openssi on PC with the newest Nvidia GPU installed. > But I only succeeded to install from Fedora 10 and later. > Will you able to deliver a version of openssi for Fedora kernel 2.6.30 > x86_64 in a few months ? > At the moment we have a 2.6.12 on x86_64 which works somewhat, with some known bugs. We've also gone some way towards 2.6.15, but it doesn't really work enough to be useful. The current plan is to put more effort in to porting to newer kernel versions after 2.0 is released. See Rogers message "Promoting 1.9.6 to 2.0.0rc1". I don't know how much effort it is to port the userland to Fedora 10, but Debian Lenny is currently working pretty well. Squeeze will have to wait until we have a newer kernel, and the init changes (async boot scripts) and replacing our ancient initrd with initramfs may be "interesting". To summarise - "in a few months" - I doubt it. |
|
From: Mulyadi S. <mul...@gm...> - 2010-02-09 02:59:44
|
Hi.... I am not one of OpenSSI developers, but hopefully I can give a thought here... On Tue, Feb 9, 2010 at 2:07 AM, Charles Def <cha...@or...> wrote: > > I would like to run Openssi on PC with the newest Nvidia GPU installed. > But I only succeeded to install from Fedora 10 and later. > Will you able to deliver a version of openssi for Fedora kernel 2.6.30 > x86_64 in a few months ? AFAIK, OpenSSI development is a little bit "stalled" right now. Probably this is due to lack of time in the OpenSSI team itself. But personally I'd like to see it growing. Unfortunately, I still can not contribute anything than a piece of HOWTO I wrote years ago. The problem with openSSI porting toward newer distro is not just about kernel issue, it also touches userland tools too. Thus, it demands larger effort than porting something like openMosix (now RIP). Not to mention the QA effort Thus, as conclusion, I think you are tied with rather old distro if you want to implement OpenSSI. You could also consider Kerrighed, but last time I visit its website, it's still based on 2.6.20. Hopefully you can draw your own decision after looking at the facts above. -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com |
|
From: Charles D. <cha...@or...> - 2010-02-08 19:07:44
|
I would like to run Openssi on PC with the newest Nvidia GPU installed. But I only succeeded to install from Fedora 10 and later. Will you able to deliver a version of openssi for Fedora kernel 2.6.30 x86_64 in a few months ? -- View this message in context: http://old.nabble.com/openssi-on-fedora-latest-version-tp27504690p27504690.html Sent from the ssic-linux-users mailing list archive at Nabble.com. |
|
From: John H. <jo...@Ca...> - 2010-01-18 17:00:24
|
I'm in the process of re-arranging the OpenSSI on Debian repository that
Ivan Krstić hosts for us.
So far only the preview install on Lenny is in the new format.
Old /etc/apt/sources.list:
deb http://deb.openssi.org/alpha/openssi-lenny ./
deb-src http://deb.openssi.org/alpha/openssi-lenny ./
deb http://deb.openssi.org/alpha/openssi-lenny-extras ./
New format:
deb http://deb.openssi.org/openssi 1,9.6-lenny-preview openssi extras
deb-src http://deb.openssi.org/openssi 1,9.6-lenny-preview openssi extras
I.E. the "base URL" is now "http://deb.openssi.org/openssi", the
"distribution" selects which version you get, (currently only
"1.9.6-lenny-preview" is available) and the "components" selects which
components you get - every "distribution" will have an "openssi"
component, the Lenny based distributions have an "extras" component.
Why? For as yet undisclosed reasons.
(All the old sources.lists incantations still work).
(Ivan - don't worry about exploding disk space, everything is linked to
the old versions for now.)
|
|
From: Roger T. <rog...@gm...> - 2009-12-22 18:12:30
|
I think the answer depends on the technology. One thing that hasn't been explored yet is integrating OpenVZ into OpenSSI so that each instance can form their own virtual OpenSSI cluster. -Roger On Tue, Dec 22, 2009 at 1:09 PM, Christopher G. Stach II <cg...@ld...> wrote: > ----- "James T Studebaker" <jts...@ji...> wrote: > >> Has anyone been able to set up VM software to run on an openssi >> cluster to make all the resources of the cluster available to the VM >> software? > > Treating an OpenSSI cluster as a big NUMA machine shouldn't be _that_ difficult, but certainly not a walk in the park. Getting OpenSSI smooshed into any modern kernel would still be necessary, though. A stable target like RHEL/CentOS 5 is a good idea, but who has the time these days? :P > > -- > Christopher G. Stach II > http://ldsys.net/~cgs/ > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > |