nodes.yaml does not accept iDRAC Service Tag

[sujit-jadhav]

nodes.yaml is tuned to accept HPE specifc value.
nodes:

• name: node01
  nid: 1
  xname: x1000c1s7b0n0
  bmc_mac: ec:2a:72:f8:77:bc
  bmc_ip: 100.96.58.175
  group: compute
  interfaces:
  • mac_addr: c4:cb:e1:bf:24:8e
    ip_addrs:
    • name: internal
      ip_addr: 172.16.0.1

xname format is more specific to HPE. On Dell server, we have Service Tag and following are the format for the same:
1736R14
2B4M8F3
J636R14

[alexlovelltroy]

I recommend adding comments around unique ids to the relevant discussions in the roadmap repository. At the moment, I think this one is the most fleshed out: #10

[erl-hpe]

There is a discussion going on right now in the Magellan project relating to this. The intention being both to give Magellan the ability to produce meaningful xnames (it currently produces xnames that have no external meaning, which does not work well with SMD) and to remove xnames and all other vendor specific embedded knowledge from Magellan.

My question about this specific item is: is the iDRAC Service Tag something that can be pulled directly from, say, the RedFish Managers structure that would represent a BMC or is it external data (like xnames are) that needs to be mapped from some other external identification for Magellan to learn it? The answer to that question could influence some part of the direction taken to resolve the other discussion.