HWADDR Based Interface Configuration
9 views
Skip to first unread message
Allen, Benjamin S.
Apr 10, 2016, 2:52:29 AM4/10/16
to warewul...@lbl.gov
Implementation of interface configuration in the provisioning environment by matching against the hwaddr instead of interface name.
Couple of notes:
1. WWPOSTNETDOWN used to disable creation of network interface configuration scripts, I've added a new variable, $WWNETCFGFILE, to control this separately. As now we want WWPOSTNETDOWN to default on, and the config files to be created as well.
2. I haven't looked at adding a new CLI option for WWNETCFGFILE, nor changed the default for WWPOSTNETDOWN.
3. WWNETDEV is used (i.e. wwnetdev from the kernel cmd line via pxelinux.cfg/...) without question when creating the network interface configuration scripts. If provisioning RHEL, this lets you name your provisioning interface whatever you want via Warewulf, as long as you have the correct MAC address. Not sure how udev rules are setup on other distros, but at minimum if you set --netdev to match the predictable interface name, it will now work.
4. Brute force fall-back interface configuration now iterates over all available interfaces. Presumably now that the network interface is picked based on hwaddr, the fall back won't actually ever be needed, unless perhaps someone incorrectly hand edits the wwhwaddr= argument in a pxelinux.cfg/ file.
5. I've not tested this with IB, but it should work. Everything is still based on the GUID not the full hardware address.
Let me know what you think,
Ben
Couple of notes:
1. WWPOSTNETDOWN used to disable creation of network interface configuration scripts, I've added a new variable, $WWNETCFGFILE, to control this separately. As now we want WWPOSTNETDOWN to default on, and the config files to be created as well.
2. I haven't looked at adding a new CLI option for WWNETCFGFILE, nor changed the default for WWPOSTNETDOWN.
3. WWNETDEV is used (i.e. wwnetdev from the kernel cmd line via pxelinux.cfg/...) without question when creating the network interface configuration scripts. If provisioning RHEL, this lets you name your provisioning interface whatever you want via Warewulf, as long as you have the correct MAC address. Not sure how udev rules are setup on other distros, but at minimum if you set --netdev to match the predictable interface name, it will now work.
4. Brute force fall-back interface configuration now iterates over all available interfaces. Presumably now that the network interface is picked based on hwaddr, the fall back won't actually ever be needed, unless perhaps someone incorrectly hand edits the wwhwaddr= argument in a pxelinux.cfg/ file.
5. I've not tested this with IB, but it should work. Everything is still based on the GUID not the full hardware address.
Let me know what you think,
Ben
Reply all
Reply to author
Forward
0 new messages