> Now that I type it out - and I read your answer to question 2, my presumption 
> is that it's the latter - since there is no way to remove the nic* attributes 
> in node01 without removing it from the group?

Unless, perhaps, there is a nics table definition for node01 that overrides the 
group entry you're talking about.

Regards,
Christian Caruthers
Lenovo Professional Services
Mobile: 757-289-9872

-----Original Message-----
From: Lachlan Simpson <lachlan.simp...@unsw.edu.au> 
Sent: Tuesday, March 3, 2020 4:34 PM
To: xcat-user@lists.sourceforge.net
Subject: Re: [xcat-user] [External] Networking: groups and nodes; nic* 
attributes

On Tue, 2020-03-03 at 15:27 +0000, Christian Caruthers wrote:
> If chdef is not working as you expect, you can always use tabedit nics 
> to open the table in an editor and manually edit it. Be careful in 
> there, though. It's easy to put info into the wrong field.
> 
> Not sure what you're asking in the first question. Can you send the 
> commands you ran along with the output of an lsdef for the node?
> 

Re question 1, imagine this:

lsdef node01
Object name: node01
    arch=x86_64
    bmc=10.197.32.01
    cons=ipmi
    ip=10.197.34.01
    mac=38:68:dd:13:f4:a0
    mgt=ipmi
    netboot=xnba
    os=centos7.7
    profile=compute
    status=booted

Then I add node01 to a group called "other_network", which now has definition 
lsdef -t group other_network Object name: mpi
    members=node01
    nicaliases.eno2=|node(\d+)|($1).mpi|
    nichostnamesuffixes.eno2=-mpi
    nicips.eno2=|node(\d+)|10.197.36.($1+0)|
    nicnetworks.eno2=mpi
    nictypes.eno2=ethernet

So. When I now do lsdef on node01, does it look like the above, or does it look 
like this:

lsdef node01
Object name: node01
    arch=x86_64
    bmc=10.197.32.01
    cons=ipmi
    ip=10.197.34.01
    mac=38:68:dd:13:f4:a0
    mgt=ipmi
    netboot=xnba
    os=centos7.7
    profile=compute
    status=booted
    nicaliases.eno2=node01.mpi
    nichostnamesuffixes.eno2=-mpi
    nicips.eno2=10.197.36.01
    nicnetworks.eno2=mpi
    nictypes.eno2=Ethernet


Now that I type it out - and I read your answer to question 2, my presumption 
is that it's the latter - since there is no way to remove the nic* attributes 
in node01 without removing it from the group?


Cheers
L.

> Regards,
> Christian Caruthers
> Lenovo Professional Services
> Mobile: 757-289-9872
> 
> -----Original Message-----
> From: Lachlan Simpson <lachlan.simp...@unsw.edu.au>
> Sent: Monday, March 2, 2020 9:29 PM
> To: xcat-user@lists.sourceforge.net
> Subject: [External] [xcat-user] Networking: groups and nodes; nic* 
> attributes
> 
> I have two questions:
> 
> 1. If a node belongs to a group with nic* defined are those additions added 
> to the node's def?
> 
> for eg, if I have an existing node  *without* those nics defined, does 
> the installation/config process add those values to the node? (lsdef 
> before gives nothing, lsdef after has nic* entries)
> 
> 2. How does one remove errant nicalias entries (for example, any nic* 
> key/value in reality) from a node's definition? Given that chdef -m/-p 
> doesn't work ( 
> https://xcat-docs.readthedocs.io/en/stable/advanced/domain_name_resolu
> tion/domain_name_resolution.html#setting-individual-nic-attribute-valu
> es
> )
> 
> I have tried re-defining the values I wanted to change and just ended 
> up with two entries for nicaliases.ib0= in the node def?
> 
> cheers
> L.
-- 
   
Lachlan Simpson

Research Technology Services

UNSW Research Technology Services
Level 3, Chemical Sciences Building F10
UNSW SYDNEY NSW 2052 AUSTRALIA
E: lachlan.simp...@unsw.edu.au
W: https://research.unsw.edu.au

_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user


_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to