Re: [SSI-devel] Re: Knoppix OpenSSI cluster
Brought to you by:
brucewalker,
rogertsang
From: En C. L. <en...@in...> - 2005-02-03 11:58:32
|
> Forget about the part where I asked you to restrict the dynamic range to > just MAC addresses configured with <DHCP>. After talking with Bruce, > there doesn't seem to be much point in doing this. An ICS interface will > only use DHCP for one of two strategies: > > - the "quickup" strategy, where any node that boots gets an IP address, > kernel, etc., parses its node number from the low order bits of the IP > address, and joins without any manual configuration, or In this case, a `ssi-addiprange` command will create the clustertab line with `IPRANGE <start> <end>` and create the /cluster/node{start..end} directories. mkdhcpd.conf will add the range to dhcpd.conf and generate a boottab with a line to indicate that linuxrc should use dhclient to get ips if there is no matching MAC in the boottab. linuxrc will loop through the NICs on the machine and use the first one which gets an IP from the dhcp server. It will then use the least significant part of the IP as the node number. > - the "corporate network", where all nodes boot from a local boot device > (hard disk partition, Live CD, etc.), and get an IP address for their > ICS interfaces from a DHCP server outside of the cluster admin's control. ssi-addnode will create the /cluster/node{num} directory and the other stuff as it does right now, except that it will accept <DHCP> as a valid ip address and so there will be no change in the dhcpd.conf. What's in the boottab for this node? If there isn't a MAC address, how does the linuxrc associate a booting node with a valid node number? If there is a MAC address, where does it come from? I'm not very clear about what the setup procedure for this `corporate network` will be. Regards, En Chiang > > Only the quickup strategy will depend on mkdhcpd.conf to generate a > dhcpd.conf with a dynamic range of addresses, and we definitely don't > want to restrict who can get an address for this approach. > > Sorry for the confusion, > > Brian > > |