Thread: [SSI-users] [2.6] Booted a two node cluster!!
Brought to you by:
brucewalker,
rogertsang
From: Brian J. W. <Bri...@hp...> - 2005-01-12 00:07:59
|
Yesterday I successfully booted a two node cluster running the new 2.6 based OpenSSI kernel!! All the necessary kernel code is checked into the OPENSSI-FC, OPENSSI-DEBIAN, and OPENSSI-RH development branches of our CVS repository. There are several caveats: 1) I've only tested on Fedora Core 2 installed with OpenSSI 1.2.0. 2) I've only tested on uniprocessor systems. There may be SMP races that need to be resolved. 3) I had to disable all the gettys in /etc/inittab, except the one for the serial console. Otherwise, node 1 locks up when node 2 attempts to start its gettys. I plan to try to fix this issue soon. 4) Only the config files in openssi/kernel.configs can be used, because there are certain things that cannot be enabled, yet. If you're feeling bold, feel free to try building and testing it. Bug reports are welcome! For less adventurous users, we're hoping to roll a 1.9.0 testing release at the end of January or the beginning of February that will include the new 2.6 kernel. Regards, Brian |
From: SAMPATHKUMAR K. K. <sam...@in...> - 2005-01-12 09:11:22
|
Hi Brian, Great news! Thanks for listing down the restrictions under which one can succesfully get a 2-node OpenSSI cluster on 2.6 up. It helps quite a bit. Just now, I checked out from the OPENSSI-RH branch of CVS and built this on my test machine, successfully. I plan to test this starting next week. Thanks, - Kishore > Yesterday I successfully booted a two node cluster running the new 2.6 > based OpenSSI kernel!! > > All the necessary kernel code is checked into the OPENSSI-FC, > OPENSSI-DEBIAN, and OPENSSI-RH development branches of our CVS > repository. There are several caveats: > > 1) I've only tested on Fedora Core 2 installed with OpenSSI 1.2.0. > > 2) I've only tested on uniprocessor systems. There may be SMP races that > need to be resolved. > > 3) I had to disable all the gettys in /etc/inittab, except the one for > the serial console. Otherwise, node 1 locks up when node 2 attempts to > start its gettys. I plan to try to fix this issue soon. > > 4) Only the config files in openssi/kernel.configs can be used, because > there are certain things that cannot be enabled, yet. > > If you're feeling bold, feel free to try building and testing it. Bug > reports are welcome! > > For less adventurous users, we're hoping to roll a 1.9.0 testing release > at the end of January or the beginning of February that will include the > new 2.6 kernel. > > Regards, > > Brian > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users |
From: SAMPATHKUMAR K. K. <sam...@in...> - 2005-01-12 09:12:17
|
Hi Brian, Great news! Thanks for listing down the restrictions under which one can succesfully get a 2-node OpenSSI cluster on 2.6 up. It helps quite a bit. Just now, I checked out from the OPENSSI-RH branch of CVS and built this on my test machine, successfully. I plan to test this starting next week on my test machine, which is a multiprocessor system. Thanks, - Kishore > Yesterday I successfully booted a two node cluster running the new 2.6 > based OpenSSI kernel!! > > All the necessary kernel code is checked into the OPENSSI-FC, > OPENSSI-DEBIAN, and OPENSSI-RH development branches of our CVS > repository. There are several caveats: > > 1) I've only tested on Fedora Core 2 installed with OpenSSI 1.2.0. > > 2) I've only tested on uniprocessor systems. There may be SMP races that > need to be resolved. > > 3) I had to disable all the gettys in /etc/inittab, except the one for > the serial console. Otherwise, node 1 locks up when node 2 attempts to > start its gettys. I plan to try to fix this issue soon. > > 4) Only the config files in openssi/kernel.configs can be used, because > there are certain things that cannot be enabled, yet. > > If you're feeling bold, feel free to try building and testing it. Bug > reports are welcome! > > For less adventurous users, we're hoping to roll a 1.9.0 testing release > at the end of January or the beginning of February that will include the > new 2.6 kernel. > > Regards, > > Brian > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > ssic-linux-devel mailing list > ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel > |
From: Bharata B R. <bha...@hp...> - 2005-01-18 09:07:14
|
I could get a 2 node cluster up with this kernel on SuSE 9.2 to the point where init gets started for node 2. The root node was running cluster-tools, openssi-tools and aaa_base packages modified for SuSE. Regards, Bharata. On Wed, 2005-01-12 at 05:36, Brian J. Watson wrote: > Yesterday I successfully booted a two node cluster running the new 2.6 > based OpenSSI kernel!! > > All the necessary kernel code is checked into the OPENSSI-FC, > OPENSSI-DEBIAN, and OPENSSI-RH development branches of our CVS > repository. There are several caveats: > > 1) I've only tested on Fedora Core 2 installed with OpenSSI 1.2.0. > > 2) I've only tested on uniprocessor systems. There may be SMP races that > need to be resolved. > > 3) I had to disable all the gettys in /etc/inittab, except the one for > the serial console. Otherwise, node 1 locks up when node 2 attempts to > start its gettys. I plan to try to fix this issue soon. > > 4) Only the config files in openssi/kernel.configs can be used, because > there are certain things that cannot be enabled, yet. > > If you're feeling bold, feel free to try building and testing it. Bug > reports are welcome! > > For less adventurous users, we're hoping to roll a 1.9.0 testing release > at the end of January or the beginning of February that will include the > new 2.6 kernel. > > Regards, > > Brian > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > ssic-linux-devel mailing list > ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel > |
From: Brian J. W. <Bri...@hp...> - 2005-01-25 01:28:41
|
Bharata B Rao wrote: > I could get a 2 node cluster up with this kernel on SuSE 9.2 to the > point where init gets started for node 2. > > The root node was running cluster-tools, openssi-tools and aaa_base > packages modified for SuSE. > > Regards, > Bharata. Hi Bharata, Did you get a login prompt on node 2? Brian |
From: Bharata B R. <bha...@hp...> - 2005-01-25 04:33:57
|
On Tue, 2005-01-25 at 06:57, Brian J. Watson wrote: > Bharata B Rao wrote: > > I could get a 2 node cluster up with this kernel on SuSE 9.2 to the > > point where init gets started for node 2. > > > > The root node was running cluster-tools, openssi-tools and aaa_base > > packages modified for SuSE. > > > > Regards, > > Bharata. > > Hi Bharata, > > Did you get a login prompt on node 2? Not yet Brain, I don't have any other packages except cluster-tools, openssi-tools and aaa_base modified for ssi. I am trying out ssi versions sysvinit, util-linux and e2fsprogs now and hopefully would get a login prompt. Regards, Bharata. > > Brian > |
From: Brian J. W. <Bri...@hp...> - 2005-01-25 19:17:55
|
Bharata B Rao wrote: > On Tue, 2005-01-25 at 06:57, Brian J. Watson wrote: > >>Hi Bharata, >> >>Did you get a login prompt on node 2? > > > Not yet Brain, I don't have any other packages except cluster-tools, > openssi-tools and aaa_base modified for ssi. I am trying out ssi > versions sysvinit, util-linux and e2fsprogs now and hopefully would get > a login prompt. > > Regards, > Bharata. Did you try my trick of disabling every getty in /etc/inittab, except for the serial console agetty? This is the only way I've gotten a prompt on the second node, so far. Of course, this requires you to be using a serial console. Regards, Brian |
From: Brian J. W. <Bri...@hp...> - 2005-01-26 03:45:22
|
Brian J. Watson wrote: >> Not yet Brain, I don't have any other packages except cluster-tools, >> openssi-tools and aaa_base modified for ssi. I am trying out ssi >> versions sysvinit, util-linux and e2fsprogs now and hopefully would get >> a login prompt. >> >> Regards, >> Bharata. > > > Did you try my trick of disabling every getty in /etc/inittab, except > for the serial console agetty? This is the only way I've gotten a prompt > on the second node, so far. Of course, this requires you to be using a > serial console. > > Regards, > > Brian Doh! I guess you won't see a prompt on the second node, until you test a clusterized version of SysVinit. Forget I said anything. ;) Brian |