FYI, one of the things I'm planning to do is having the network config model
better designed to tolerate this (e.g. you wouldn't specify the interface name,
unless you wanted to, and if you indicated a name and a mac address, then that
nic would be renamed according to your request).
I know this has been a personal annoyance of mine and so it was on my list. I
didn't know to what extent others experienced the same annoyance at the limited
nature and the ad-hoc nature of the postscripts.
From: Christian Caruthers [mailto:[email protected]]
Sent: Thursday, June 30, 2016 2:07 PM
To: xCAT Users Mailing list
Subject: Re: [xcat-user] discovering interface names dynamically
A few things to try:
First, you can boot to the genesis image (nodeset node shell), which is the
same thing that is running after discovery. From there, you can login and use
ethtool to identify your interfaces.
Second, RHEL 7 variants now use what they call consistent naming. If you can
wrap your head around the logic behind it, you can probably predict what the
interface names will be. I can't, so…
Third, if you don't like the consistent naming, you can add "biosdevname=0
net.ifnames=0" to addkcmdline for your osimage, and RHEL 7 will boot up with
good old eth(0, 1, 2…)..
Finally, with xCAT 2.12 came the command "getadapter" which will "Scan the
network adapters on the compute nodes to determine the predictable naming of
the network interfaces when the OS is installed.” I haven't messed with it yet.
https://github.com/xcat2/xcat-core/wiki/XCAT_2.12_Release_Notes
Regards,
Christian Caruthers
Lenovo xESS IT Consultant
Mobile: 757-289-9872
From: Andrew Loftus [mailto:[email protected]]
Sent: Thursday, June 30, 2016 1:18 PM
To: [email protected]<mailto:[email protected]>
Subject: [xcat-user] discovering interface names dynamically
Does anyone have any experience or ideas how to acquire (ethernet) interface
names dynamically?
For instance, in setting up secondary networks, entries in the "nics" table
require both the interface name and associated network information. However,
these interface names aren't known before the OS is installed (unless one node
has already been installed and the interface names checked manually).
Furthermore, the interface names change based on a combination of OS version,
hardware model, and install type combination. So it's not very robust.
My thought is to setup secondary networks using a postbootscript. I'm looking
for ideas to scan each ethernet interfaces and discover the network information
to setup the secondary networks using that information.
Cheers,
--Andy
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
