-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ethernet VLAN's or Infiniband partitions not supported #166
Comments
Warewulf's initrd also doesn't have a concept of VLANs/IB partitions, eg: https://github.com/warewulf/warewulf3/blob/development/provision/initramfs/init#L73 |
Oh, right. Definitely not as easy to fix as just tweaking the regexp, it seems. |
Does your use case include booting from a VLAN or IB partition device, or do you need to use it in a template to create a ifcfg-ib0.80a1 or similar? |
For now at least, no need to boot from it. I just need to create the ifcfg files and bring up the interfaces at some point during boot, which would then allow me to mount Lustre. (I could of course duct tape something together with a shell script launched from /etc/rc.local, but it would of course be nice if the 'obvious' thing would work) |
Warewulf doesn't handle IB partitions (or Eth VLAN's), see warewulf/warewulf3#166 Instead create a script to generate the ifcfg- files for the IB partitions, bring them up, and mount Lustre.
A workaround for VLANs at least, assuming RHEL, is to use Alternatively you can name your VLAN interfaces anything at all if you specify
Logic for parsing ifcfg scripts is found in /etc/sysconfig/network-scripts/ifup, around line 77 for VLAN configs, at least in RHEL 7.6. Note, using Warewulf's file functionality the %{...} template will be replaced with whatever is configured for the host, eg. I started looking at allowing the traditional |
Trying to configure a device for for an IB partition fails with
The same error occurs if I try to setup a device for an eth VLAN, which are named similarly (e.g. 'eno1.100' for VLAN 100 on the device eno1).
The problem seems to be that the regexp check in common/lib/Warewulf/Module/Cli/Node.pm is a bit too strict.
The text was updated successfully, but these errors were encountered: