Gentoo Archives: gentoo-cluster

From: Donnie Berkholz <spyderous@g.o>
To: gentoo-cluster@l.g.o
Subject: Re: [gentoo-cluster] Gentoo clustering "à la" www.clustermatic.org (PXE booted nodes)
Date: Thu, 17 Nov 2005 14:31:30
Message-Id: 437C9402.8020800@gentoo.org
In Reply to: Re: [gentoo-cluster] Gentoo clustering "à la" www.clustermatic.org (PXE booted nodes) by Mathias Weigt
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 Mathias Weigt wrote:
5 | I have to setup such a (little) cluster as well and I am very interested
6 | in a good documented Gentoo-based procedure.
7
8 I set up an NFS-root, PXE-boot cluster about a year ago. I can try to
9 put my notes together into something usable as a doc, if you'd like.
10
11 The basic idea I used was to maintain a couple of ROOT=/foo environments
12 on the master server: one for the NFS root, and one smaller one with
13 just busybox and a kernel to create an initrd for each node.
14
15 The ROOT approach is far superior to what's promoted in the NFS root
16 Gentoo doc, because it allows for a maintainable and differentiated node
17 system rather than just copying straight from the master's root fs.
18
19 I then booted to the kernel+initrd with an interesting setup:
20 PXE-capable Etherboot on a floppy in each node (required a development
21 version of Etherboot at the time), because I didn't have PXE-capable
22 Ethernet cards, launched pxelinux on the server (part of isolinux),
23 which served as a HW-address-specific bootloader so it was possible to
24 have different roles for nodes. With a little symlinking I was able to
25 just have one pxelinux config file per role.
26
27 Thanks,
28 Donnie
29 -----BEGIN PGP SIGNATURE-----
30 Version: GnuPG v1.4.2 (GNU/Linux)
31
32 iD8DBQFDfJQCXVaO67S1rtsRAnmYAJ0VagjI2ZmZaIjIpGYkKo0pd5ZUngCfSEH6
33 QFOqXkNw/NLAPmJBEAg7m7w=
34 =mHEj
35 -----END PGP SIGNATURE-----
36 --
37 gentoo-cluster@g.o mailing list

Replies

Subject Author
Re: [gentoo-cluster] Gentoo clustering "à la" www.clustermatic.org (PXE booted nodes) Eric Thibodeau <kyron@××××××××.com>