Resources for IT Professionals > 포럼 홈 > Windows HPC Server V2 Pre-RTM > HPC 2008 naming / renaming of nodes / reset naming series
질문하기질문하기
 

답변됨HPC 2008 naming / renaming of nodes / reset naming series

  • 2008년 4월 14일 월요일 오후 1:26Johannes_de 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     


    Hello there,

    is there any command to reset the naming series to zero or to give one node a defined name to fill gaps in the naming series?


    Thanks

    Johannes

    //edit
    seems that reconfiguring the naming series,  although with the same parameters, resets the naming series.

    However it would be nice to decide which name to give at the point where I am assigning the node templates

답변

모든 응답

  • 2008년 4월 16일 수요일 오후 6:08cmp2 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     

    You can create a node.xml file which allows you to set node properties such as node names, node templates, location identifiers such as rack and chassi and node groups for nodes in your cluster.  To see what a node.xml file looks like, on your existing cluster, go to the node management navigation pane, select a set of nodes and choose the "export node.xml" action.  A node.xml file will be created for those nodes.  You can edit the file.  You can provision nodes using the node.xml file.  Invoke the add node wizard from either the node management navigation pane or from the configuration navigation pane.  Choose the node.xml option. 

     

    In our next community pack (CTP) release coming soon, you will also be able to reset the naming series (from the configuration navigation pane ToDo list) or rename a node to fill gaps before the node is provisioned. 

     

    Cathy

     

  • 2008년 5월 14일 수요일 오후 2:19a_Brannon_1 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    As a follow-up, what mechanism keeps track of this naming series sequence?  Would be nice to be able to see prior to initiating/resuming a deployment, where your system is in the naming series.
  • 2008년 5월 21일 수요일 오전 8:56Brian BrokerMSFT사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     

    Hi Brannon,

     

    This is a feature that I've brought up in the past and I'll push to get this in for RC1.  In the mean time, a solution for this issue is to simply go back to the 'to do' page and reset your node naming series from there.  We should fill in the gaps if you just click 'OK' against your original naming series (this will effectively reset the naming series for you).

     

    Also, as an alternative solution, you can also "Edit" a node name prior to assigning a deployment template in beta 2.

     

    Thanks for your feedback!  It validates my argument. ;-)

    --Brian

  • 2008년 5월 28일 수요일 오후 3:24a_Brannon_1 사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     
    Thank you.

    Please continue to push for that feature to be included. It is invaluable to be able to know exactly where the system is going to be in its naming. It's especially crucial for large deployments (which I do mostly) to be on the proactive side, rather than re-act to an error in sequencing.

    BTW, the process of going back to the "To Do" page & resetting the naming series, failed for me in my experiences with this issue. The system would continue counting up with each node that came up. Even when the node names are deleted in the interface & in AD. Something was keeping track of the names & sequence & was not relinquishing. (note: this was in Beta1 product).

    Care to share where these naming values are stored?

     
    I will be testing the renaming functionality in the coming weeks with Beta2.


    KUDOS guys! 

  • 2008년 5월 30일 금요일 오전 5:32Brian BrokerMSFT사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     

    I believe that resetting and filling the gaps was still an issue in Beta 1.  Furthermore, there is no public API for retrieving the current naming counter value.  We are in the process of estimating dev cost for GUI and/or Powershell support for this feature.

     

    Regards,

    --Brian

  • 2009년 3월 25일 수요일 오후 11:55Don PatteeMSFT, 중재자사용자 메달사용자 메달사용자 메달사용자 메달사용자 메달
     답변됨
     

    HPC Server 2008 shipped in September 2008, so I'm going through and marking all questions in the beta forum as 'answered'.