#149 HWControlNodeId

2.8.4
pending
nobody
5
2013-12-12
2012-05-09
No

CSM has a "HWControlNodeId" field which corresponds to the lpar "name" in the HMC. To maintain consitancy with CSM, it would be beneifical if xCAT development could add a table entry for the HWControlNodeID which matches the LPAR "name" in the HMC. As a workaround, we put the lpar "name" in the "comments" field of the "nodelist" table. We chose the "comments" fields to avoid xCAT's control/use of other/similar fields. We had a prior meeting with IBM about this. We would hope that in the future xCAT table/fields would better match the CSM fields since CSM more closely aligns itself to the HMC environment. In particular we would like to see the field above added to xCAT tables.

Discussion

  • Guang Cheng Li

    Guang Cheng Li - 2013-12-11
    • status: open --> closed
    • Group: --> 2.8.4
     
  • Guang Cheng Li

    Guang Cheng Li - 2013-12-11

    A reasonable requirement, xCAT uses the lparid as the identification for the lpar however CSM uses the LPAR name as the identification. The problem with the CSM mechanism is that if there are duplicate lpar names between CECs, CSM will get confused. But xCAT can add a new node attribute lparname besides the lparid, the lparname is mainly for informational purpose.

    I have added this request into xCAT wishlist, see https://sourceforge.net/apps/mediawiki/xcat/index.php?title=Wish_List_for_xCAT_2. Closing this feature request and start using the wishlist to track this request.

     
  • Bruce

    Bruce - 2013-12-11

    How will the lparname attribute get populated? I would rather have lsvm return this value (and not add an attribute).

     
  • Guang Cheng Li

    Guang Cheng Li - 2013-12-12
    • status: closed --> pending
     
  • Guang Cheng Li

    Guang Cheng Li - 2013-12-12

    We already have the lparname returned from rscan, but for now we are using the lparname as the nodename by default, it is possible that the users will modify the hostname to be different with the lparname. If the hostname and lparname is different, it is a little bit confusing on which lpar the node is. But as you mentioned above, we do have lsvm command to list the lparname of the node, and we could use chvm <noderange> lparname=* to make the lparnames be the same as the nodenames(however it only works for DFM configuration for now). Maybe we want to add the support of chvm <noderange> lparname= with the HMC configuration.

    Austin Fowler,

    In your configuration, are the nodenames different with the lparnames? If we could use chvm <noderange> lparname=* to change the lparnames be the same as the hostnames, will this make the things easier for you?