David,
Let me say thanks for your well thought out email. Also, do you know
Jan Lindheim and/or Mark Bartelt?
Comments below...
David Mathog wrote:
>Greetings,
>
>I use systemimager and boel to replicate nodes on our beowulf.
>In order to speed things up I first modified boel to include
>"dolly", which is a daisy chain copier,
>
Cool. I've heard of "dolly", but have never played with it.
>instead of rdist, which
>isn't.
>
I presume you mean rsync? But your point is a good one -- rsync does
not use a daisy chain.
>That helped considerably but dolly had a few problems
>which I've hopefully remedied in the much simplified "nettee",
>which is derived from dolly.
>
* Is nettee software that you wrote?
* Based on the code from dolly?
* Is it Open Source?
>Nettee on most nodes is
>invoked like this:
>
> nettee -next nextnode >/dev/hda0
>
>(read data from the preceding node, send it to both the next
>node and the device being replicated). So the shell on each
>node needs to know the value of the nextnode (the name of
>the next node(s) in the chain) and it needs to get that from
>dhcp. Or at least ideally dhcp should return this value.
>
>Following the instructions in your boel article at linuxdevices.com
>and the man pages this was added to dhcpd.conf on the dhcp server:
>
>option nextnode code 200 = text;
>
>
Hmmm. This will work if you're imaging all nodes at once, but what
happens if you're only imaging a portion of the nodes, and they don't
happen to be adjascent to each other according to their dhcp info?
(other than re-writing the dhcpd.conf file)
>(just after the "vendor-encapsulated-options" string).
>
>and dhcpd restarted. That wasn't enough to get the new value
>into the leases on a client after dhclient was restarted. So
>on a test client (a normally running mandrake 10.0 node) I
>added
>
>/etc/dhclient-eth0.conf
>
>consisting of:
>
>request log-servers,
> nextnode,
> fixed-address,
> server-name,
> dhcp-lease-time,
> dhcp-message-type,
> domain-name-servers,
> dhcp-server-identifier,
> subnet-mask,
> broadcast-address,
> routers,
> host-name,
> domain-name;
>
>and restarted dhclient again.
>
Sounds good.
>It is run this way on this platform:
>
>/sbin/dhclient -1 -q -lf /var/lib/dhcp/dhclient-eth0.leases -pf
>/var/run/dhclient-eth0.pid -cf /etc/dhclient-eth0.conf eth0
>
>Looking in dhclient-eth0.leases one now finds the extra values
>listed in dhclient.conf. Unfortunately "nextnode" shows up
>this way:
>
> option unknown-200 "monkey02";
>
>instead of the hoped for:
>
> option nextnode "monkey02";
>
>In other words, the nextnode line in the dhclient.conf is required
>to retrieve the 200 value, but it is stamped with "unknown-200"
>instead of "nextnode".
>
>
I think there is a way to handle this in dhcp3 by defining your own
option types. But option-200 works just fine too. ;-)
>I see that in the boel script (not .conf) you use this syntax:
> IMAGESERVER=$new_option_140
> echo "Using option-140 as IMAGESERVER: $IMAGESERVER"
>
>and in dhclient.conf
>request option-100,
> option-140,
>etc.
>
>and the script writes the results into a file other than
>the lease file.
>
>I'm a bit confused here. Where does "new_option_140" come
>from in the script? Why isn't it "new_option-140"???
>
>
I believe this comes from dhclient-script. If you look at the
systemimager source, you'll find the following two files in the
"initrd_source/skel/etc" directory:
dhclient-script.systemimager-prefix
dhclient-script.debian-dist
They are concatenated into dhclient-script as the boel system is booting.
>Why does the lease in my case end up with an "unknown-200"
>name instead of "nextnode"?
>
>
See dhcp3 bit above.
>Thanks,
>
>
I'd be interested in considering this for inclusion in the upstream
source, as an alternative transport. Especially if there is a good
solution to the "I have no adjascent neighbor" question.
Cheers!
-Brian
>David Mathog
>[EMAIL PROTECTED]
>Manager, Sequence Analysis Facility, Biology Division, Caltech
>
>
>
>
--
------------------------------------------------------
Brian Elliott Finley Mobile: 630.631.6621
gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52
------------------------------------------------------
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
