<br><font size=2 face="sans-serif">There are scripts within the OSCAR release to do this for you. You can start the scripts, power on the nodes in the order you wish, and then assign them to auto generated hostnames. The scripts output the dhcp.conf file.</font>
<br>
<br><font size=2 face="sans-serif">I would think you could pull them out of oscar pretty easily.</font>
<br>
<br><font size=2 face="sans-serif">Jason</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Chris Dagdigian <dag@sonsorol.org></b></font>
<br><font size=1 face="sans-serif">Sent by: bioclusters-bounces+jason.calvert=pharma.novartis.com@bioinformatics.org</font>
<p><font size=1 face="sans-serif">03/29/2005 02:27 PM</font>
<br><font size=1 face="sans-serif">Please respond to "Clustering, compute farming & distributed computing in life science informatics"</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: adamm@menlo.com, "Clustering, compute farming & distributed computing in life science informatics" <bioclusters@bioinformatics.org></font>
<br><font size=1 face="sans-serif"> cc: (bcc: Jason Calvert/PH/Novartis)</font>
<br><font size=1 face="sans-serif"> Subject: Re: [Bioclusters] alternative DHCP implementations?</font></table>
<br>
<br>
<br><font size=2 face="Courier New"><br>
<br>
Agreed. It was just a shortcut. We already do allocation of IP based on <br>
MAC address but that only works when you know the MAC address <br>
information ahead of time. This is rare especially on whitebox cluster <br>
projects where people don't put the MAC on the product packaging or on <br>
the chassis itself. Some vendors do a good job of making the data easy <br>
to find and others simply don't bother.<br>
<br>
A dhcp server handing out dynamic-range leases in a predictable manner <br>
is what allowed us to easily map MAC address to node position and <br>
nodename simply by powering on the nodes for PXE boot in the order in <br>
which they are racked and stacked. Once this was done we had the <br>
MAC->Node mapping data we needed to generate the static allocation entries.<br>
<br>
A workaround for non-predictable allocation is to simply power on the <br>
cluster in the order in which you want things named, then parse the <br>
dhcpd leases file for both the MAC address *and* the timestamp <br>
representing the lease handout. That would allow you to map MAC -> Node <br>
without having to care about hostnames for the first pass MAC collection <br>
phase. Then you build the static-by-mac entries into the conf file and <br>
problem solved. If we stick with ISC DHCP this is a possibility...<br>
<br>
c<br>
<br>
Adam S. Moskowitz wrote:<br>
> Chris,<br>
> <br>
> <br>
>>We are thinking about trying to find a replacement DHCP server that has <br>
>>a predictable method of allocating dynamic IP addresses (even if only <br>
>>for the initial cluster deployment)<br>
> <br>
> <br>
> I think it's a bad idea to rely on such behavior. I don't remember what<br>
> the RFC says, but in general, unless the RFC guarantees an<br>
> implementation should behave a particular way, you are asking for<br>
> trouble to rely on specific behavior.<br>
> <br>
> A great example of this is how round-robin DNS used to work and then how<br>
> it changed and lots of things broke.<br>
> <br>
> DHCP isn't meant to do what you're asking it to do, so I strongly<br>
> suggest you not use it to solve that particular problem.<br>
> <br>
> That said, DHCP supports a mechanism for binding specific IP addresses<br>
> to specific MAC addresses, even though the assignment is still done<br>
> dynamically. Yes, this is a bit more work, but at least it's guaranteed<br>
> behavior.<br>
_______________________________________________<br>
Bioclusters maillist - Bioclusters@bioinformatics.org<br>
https://bioinformatics.org/mailman/listinfo/bioclusters<br>
</font>
<br>
<br>
<BR>
______________________________________________________________________<BR>
The Novartis email address format has changed to <BR>
firstname.lastname@novartis.com. Please update your address book <BR>
accordingly.<BR>
______________________________________________________________________<BR>