On 2/13/19 6:41 PM, Kevin Keane wrote:
One of the drawbacks of using a formula
Sorry, I meant regexp : we successfully do something very similar (our compute nodes are in a /22 part of a /21 subnet) :
"tars","|\D+(\d+)$|192.168.(128+$1/255).($1%254+2)|",,,"192.168.128.0/22 (192.168.128.0 -> 192.168.131.255)",
It works (the +2 at the end is to skipt .0 and .1
And for your most recent question: I just checked - the NIC that is used for PXE booting continues to get its address from DHCP.
Hmm, that could be a problem since, though your isolation (1Gb/s nic for admin, 10Gb/s for data) is cleaner, I'm not sure I'd want it since it seems to imply some overhead (2x ip/names, ssh to the "correct" name depending of what you do, ...etc...).
If I choose not to do it, I'll end up just like today, i.e. with only one ip on each node (for the 10Gb/s nic).
As I said, even then your nicip attribute use is a very good idea since it frees us from worrying about what interface PXE uses.
So if it "happens" (bios setting) that the nic I use once netbooted is the nic that's used for PXE, you seem to say it won't be statically set.
And, though my nodes today use dhcp set interface, I'd like to change it to static since dhcpd on the MN is a SPOF (if dhcpd dies, nodes at the end of lease could lose connectivity, which wouldn't happen if set statically).
Maybe it's feasible with some postscript tuning. Thanks -- Thomas H. _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
