Open whowutwut opened 6 years ago
hi, @whowutwut , for the 1st requirement that is it possible to also update some of the fields in dodiscovery to be executed on the compute node
, the PR https://github.com/xcat2/xcat-core/pull/5371/files made by @xuweibj can update some of the attributes with updatenode <CN> -P getinv
, but no MTM, serial number.
For normal discovery process, the node hardware information can be updated correctly.
But failed for the case that update host MAC manually, right?
Maybe we can have rinv to update and check the host mtms attribute with the destination node. What is your idea?
@zet809 Sorry for the very late response here. I thought about this again and came to the issue to see if any status has changed.
Not just for MTM and Serial, but for other attributes that the user may find interesting...
I am thinking about building upon xml packet this to extract more information off of the server but it doesn't work today so trying to see if we can allow it to run..
The real advantage here is when adapters or drives are replaced and machine put back, it might be valuable to xdsh to the node and run the findme and allow xCAT to update the node definition with data that is captured by the discovery code.
@zet809 I think you have implemented some changes to allow
bmcsetup
to be run outside of the genesis kernel and on the host.. . is it possible to also update some of the fields in dodiscovery to be executed on the compute node as well that would update attributes of xCAT via SN/MNI'm not 100% sure we want to update everything, would something overwrite some user defined fields? There's currently no way to tell which fields have been generated from findme in discovery and which field have been modified by the user after the nodes are discovered and in production.
I have see the case where there may be a need to update serial number/mtm if we replace a node at a certain switch/switchport ...when new machines are added into the cluster and powered on, discovery should handle this though... so this use case is not quite right.
In our dev environmnt there are times when I manually set up the IP for the BMC and obtain the MAC from the bootloader instead of using discovery, but sometimes would like the node definition to be updated or "refreshed" based on the actual running node, this would allow that...