[prev in list] [next in list] [prev in thread] [next in thread]
List: npaci-rocks-discussion
Subject: [Rocks-Discuss] Re: proper way to rename a Rocks 6.1.1 compute node
From: Robert Kudyba <rkudyba () fordham ! edu>
Date: 2020-10-28 19:09:18
Message-ID: CAFHi+KSpMMuusHR1eswrHzni9PXA111C0ieSR3dYO4Oo7hEtXA () mail ! gmail ! com
[Download RAW message or body]
Just wanted to share with the list that Prof. Papadopoulos tips below was
the correct way to rename. So simple just use the command "rocks set host"
and do a sync and reboot when done.
rocks list host interface | grep -e HOST -e compute-0-0
*HOST *SUBNET IFACE MAC IP NETMASK
MODULE *NAME *VLAN OPTIONS CHANNEL
compute-0-0: private eth1 00:24:81:e9:5f:80 10.1.1.254 255.255.255.0
------ compute-0-0 ---- ------- -------
What I had to also fix was that the "HOST" column and the "NAME" column
values needed changing. Now we're good!
rocks list host | grep -e HOST -e compute
HOST MEMBERSHIP CPUS RACK RANK RUNACTION INSTALLACTION
compute-0-0: Compute 8 0 0 os install
compute-0-11: Compute 24 0 11 os install
compute-0-2: Compute 8 0 2 os install
compute-0-3: Compute 8 0 3 os install
compute-0-4: Compute 8 0 4 os install
compute-0-5: Compute 8 0 5 os install
compute-0-6: Compute 8 0 6 os install
compute-0-7: Compute 8 0 7 os install
compute-0-8: Compute 8 0 8 os install
compute-0-9: Compute 8 0 9 os install
compute-0-10: Compute 8 0 10 os install
compute-0-1: Compute 8 0 1 os install
compute-0-12: Compute 8 0 12 os install
compute-0-13: Compute 8 0 13 os install
compute-0-14: Compute 8 0 14 os install
Thanks again!
On Thu, Oct 22, 2020 at 1:43 PM Philip Michael Papadopoulos <
ppapadop@uci.edu> wrote:
> HI Robert,
> Trying to remember 6.1.1 -- it's quite a while ago (don't have any 6.x
> systems up any longer)
> if you do "rocks set host" you can see the various items that can set for
> a host.
> Please note: this changes the database, you will need to sync the config
> and then reinstall the host
> First things do a
> # rocks list host | grep -e MEMBERSHIP -e compute-0-0
> HOST MEMBERSHIP CPUS RACK RANK RUNACTION INSTALLACTION
> compute-0-0: Compute 6 0 0 os install headless
>
> and
> # rocks list host interface | grep -e HOST -e compute-0-0
> HOST SUBNET IFACE MAC IP
> NETMASK MODULE NAME VLAN OPTIONS CHANNEL
> compute-0-0: private eno1 00:d8:61:78:13:2d 10.1.147.251
> 255.255.255.0 ------ compute-0-0 ---- ------- -------
> compute-0-0: ------- enp3s0f0 00:15:17:71:44:d6 ---------------
> --------------- ------ ---------------- ---- ------- -------
> compute-0-0: ------- enp3s0f1 00:15:17:71:44:d7 ---------------
> --------------- ------ ---------------- ---- ------- -------
>
> Nearly all the fields are changeable with rocks commands.
>
> You can find out about available commands
>
> The following is for rocks 7, I've highlighted the key ones
> # rocks set host
> attr {host} {attr} {value} [attr=string] [value=string]
> boot {host}... [action=string]
> bootflags {host}... [flags=string]
> cdrom {host} [cdrom=string] [key=string]
> comment {host}... {comment} [comment=string]
> cpus {host}... {cpus} [cpus=string]
> installaction {host}... {action} [action=string]
> interface channel {host}... {iface} {channel} [channel=string]
> [iface=string]
> interface disablekvm {host} {iface} [disablekvm=bool] [disablekvm=bool]
> [iface=string]
> interface iface {host}... {mac} {iface} [iface=string] [mac=string]
> interface ip {host} {iface} {ip} [iface=string] [ip=string]
> interface mac {host} {iface} {mac} [iface=string] [mac=string]
> interface module {host}... {iface} {module} [iface=string] [module=string]
> *interface name {host} {iface} {name} [iface=string] [name=string] *
> interface options {host}... {iface} [iface=string] [options=string]
> interface subnet {host}... {iface} {subnet} [iface=string] [subnet=string]
> interface vlan {host}... {iface} {vlan} [iface=string] [vlan=string]
> membership {host}... {membership} [membership=string]
> *name {host} {name} [name=string] *
> power {host}... [action=string] [key=string]
> *rack {host}... {rack} [rack=string] *
> *rank {host}... {rank} [rank=string] *
> roll {host} {name} {version} {arch} [arch=string] [name=string]
> [os=string]
> [version=string]
> runaction {host}... {action} [action=string]
> sec_attr {host} [attr=string] [crypted=boolean] [enc=string]
> [value=string]
> vm {host} [disk=string] [disksize=string] [mem=string] [physnode=string]
> [slice=string] [virt-type=string]
> vm cdrom {host} [cdrom=string]
>
> So for the existing host I would do
> rocks set host rack <host> rack#
> rocks set host rank <host> "desired rank"
> rocks set host interface name <host> <iface> "new name of host"
> rocks set host name <host> "new name of host"
>
> Here's an example from the output above changing compute-0-0 to robert-1-5
>
>
> rocks set host rack compute-0-0 1
> rocks set host rank compute-0-0 5
> rocks set host interface name compute-0-0 eno1 robert-1-5
> rocks set host name compute-0-0 robert-1-5
>
> ## Now check the results
> rocks list host | grep -e HOST -e robert
> HOST MEMBERSHIP CPUS RACK RANK RUNACTION INSTALLACTION
> robert-1-5: Compute 6 1 5 os install headless
> rocks list host interface | grep -e HOST -e robert
> HOST SUBNET IFACE MAC IP
> NETMASK MODULE NAME VLAN OPTIONS CHANNEL
> robert-1-5: private eno1 00:d8:61:78:13:2d 10.1.147.251
> 255.255.255.0 ------ robert-1-5 ---- ------- -------
> robert-1-5: ------- enp3s0f0 00:15:17:71:44:d6 ---------------
> --------------- ------ ---------------- ---- ------- -------
> robert-1-5: ------- enp3s0f1 00:15:17:71:44:d7 ---------------
> --------------- ------ ---------------- ---- ------- -------
>
> All that looks right to me.
> So, sync the config and check that you can get to the node
> rocks sync config
> ssh robert-1-5
> Warning: untrusted X11 forwarding setup failed: xauth key data not
> generated
> Last login: Wed Jun 3 17:17:24 2020 from mass.local
> Rocks Compute Node
> Rocks 7.0 (Manzanita)
> Profile built 16:22 19-Oct-2019
>
> Kickstarted 16:28 19-Oct-2019
> *[root@compute-0-0 ~]# <--- still the old node name, this is correct*
>
> FINAL STEP
> # rocks set host boot action=install robert-1-5
> then reboot the node.
>
> HOpe that helps,
> Phil
>
>
>
>
>
> On Thu, Oct 22, 2020 at 9:46 AM Robert Kudyba <rkudyba@fordham.edu> wrote:
>
> > Hello Prof. Papadopoulos,
> >
> > Would you be willing to reply via the list (or personally) on how to
> > properly rename both the compute node and the rank? We're still on 6.1.1
> >
> > ---------- Forwarded message ---------
> > From: Sarlo, Jeffrey S <JSarlo@central.uh.edu>
> > Date: Sat, Oct 10, 2020 at 8:53 AM
> > Subject: Re: [Rocks-Discuss] proper way to rename a Rocks 6.1.1 compute
> > node
> > To: Robert Kudyba <rkudyba@fordham.edu>
> >
> >
> > I think you would need to do the removal of compute-0-20, but you would
> > change the insert-ethers line in the steps.
> >
> > Not sure how rank is figured out. Maybe there is a counter that it keeps
> > track of for the last rank used and just increments from there and doesn't
> > keep track if any were removed. I thought rank and name matched also, but
> > it looks like they are different entries. If you want the rank to match,
> > you might have to do insert-ethers --cabinet 0 --rank 14 --hostname
> > compute-0-14 or it might give you rank of 21, even after 20 is removed.
> > Another possibility is if you had been using the version 1 directions and
> > maybe --replace only changes the name and doesn't do anything with the
> > existing rank for the node.
> >
> > Jeff
> >
> > ------------------------------
> > *From:* Robert Kudyba <rkudyba@fordham.edu>
> > *Sent:* Friday, October 9, 2020 11:24 PM
> > *To:* Sarlo, Jeffrey S <JSarlo@Central.UH.EDU>
> > *Subject:* Re: [Rocks-Discuss] proper way to rename a Rocks 6.1.1
> > compute node
> >
> > On Fri, Oct 9, 2020 at 6:40 PM Sarlo, Jeffrey S <JSarlo@central.uh.edu>
> > wrote:
> >
> > You might specifically tell it you want 14 in the version 2 insert-ethers
> > --hostname compute-0-14.
> >
> >
> > So you mean to change line #3? 3. Run "insert-ethers --cabinet 0 --rank
> > 0"? But don't I have to remove 20 first?
> >
> >
> > It looks like you do have a 15-19 for rank from the list you sent.
> >
> >
> > I missed that originally, nice catch, how does rank fit into the picture?
> > I guess rank in my mind should ideally match the compute-0-xx but clearly
> > things have happened in the past that incremented the rank value.
> >
> >
> > Rocks might not just look for open spaces and might just go for the next
> > largest and that is why it picked 20.
> >
> >
> > https://urldefense.com/v3/__http://central-7-0-x86-64.rocksclusters.org/roll-docum \
> > entation/base/7.0/insert-ethers.html__;!!Mih3wA!SjAChNdMiuqaFuFRdwHpsWVxXUiKDqI3MNeprL_6kAwTeEx-eUJtSFObxFecqiueD87d7qRAe3g$ \
> > <https://urldefense.proofpoint.com/v2/url?u=http-3A__central-2D7-2D0-2Dx86-2D64.r \
> > ocksclusters.org_roll-2Ddocumentation_base_7.0_insert-2Dethers.html&d=DwMFAw&c=aqM \
> > fXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3 \
> > GejY&m=rcy7EbMVQKWJ06G99ELLw_LRIUz8kEz-fFpiTsJvKxk&s=878cEiOPpSAy22hoTrjTRZJO-KsbTZNfixyBHyCwjQU&e=>
> >
> > The option might be --host also. The page is a little confusing if it is
> > host or hostname.
> >
> >
> > Thanks I just want to make sure I get it right as I won't be on site for
> > a few days.
> >
> > Also, you didn't CC the main mailing list was that intentional? I don't
> > mind sharing in case someone in the future runs into this.
> >
> > Thanks for the reply.
> >
> >
> >
> > ------------------------------
> > *From:* npaci-rocks-discussion-bounces@sdsc.edu <
> > npaci-rocks-discussion-bounces@sdsc.edu> on behalf of Robert Kudyba <
> > rkudyba@fordham.edu>
> > *Sent:* Friday, October 9, 2020 3:29 PM
> > *To:* Discussion of Rocks Clusters <npaci-rocks-discussion@sdsc.edu>
> > *Subject:* [Rocks-Discuss] proper way to rename a Rocks 6.1.1 compute
> > node
> >
> > I've seen the past thread here
> >
> > https://urldefense.com/v3/__https://lists.sdsc.edu/pipermail/npaci-rocks-discussio \
> > n/2012-January/056284.html__;!!LkSTlj0I!Se6HmnCqUl71K3kDghB--pi4tjf4px2iiIY-HLNp-1IJsWAGK56Ra17E_5xPFHM35eU$
> > ==========================
> > Version one:
> >
> > 1. Run "insert-ethers --replace compute-0-4"
> > 2. Pick "compute" from list.
> > 3. Make that node PXE boot.
> > 4. When the "( )" turns into a "(*)", indicating that the node has
> > received
> > a kickstart file, exit.
> >
> > Version two:
> >
> > 1. Run "rocks remove host compute-0-4"
> > 2. Run "rocks sync config; rocks sync users"
> > 3. Run "insert-ethers --cabinet 0 --rank 0"
> > 4. Pick "compute" from list.
> > 5. Make that node PXE boot.
> > 6. When the "( )" turns into a "(*)", indicating that the node has
> > received
> > a kickstart file, exit.
> >
> > To re-install a node that already has an entry in the rocks database (i.e.
> > a "known" node):
> >
> > 1. Run "rocks set host boot compute-0-0 action=install
> > 2. Make that node PXE boot.
> > ===================
> > I posted a thread
> > <
> > https://urldefense.com/v3/__https://lists.sdsc.edu/pipermail/npaci-rocks-discussio \
> > n/2020-October/073641.html__;!!LkSTlj0I!Se6HmnCqUl71K3kDghB--pi4tjf4px2iiIY-HLNp-1IJsWAGK56Ra17E_5xPg1PGLGA$
> >
> > >
> > earlier this week and I simply forced a reinstall. The node boots up with
> > hostname compute-0-20 but we'd like to keep it sequential so compute-0-14
> > is next. Right now we have this:
> > rocks list host
> > HOST MEMBERSHIP CPUS RACK RANK RUNACTION
> > INSTALLACTION
> > puppet: Frontend 32 0 0 os install
> > compute-0-0: Compute 8 0 16 os install
> > compute-0-11: Compute 24 0 18 os install
> > compute-0-2: Compute 8 0 2 os install
> > compute-0-3: Compute 8 0 3 os install
> > compute-0-4: Compute 8 0 4 os install
> > compute-0-5: Compute 8 0 5 os install
> > compute-0-6: Compute 8 0 6 os install
> > compute-0-7: Compute 8 0 7 os install
> > compute-0-8: Compute 8 0 8 os install
> > compute-0-9: Compute 8 0 9 os install
> > compute-0-10: Compute 8 0 17 os install
> > compute-0-1: Compute 8 0 15 os install
> > power-0-0: Power Distribution Unit 1 0 0 os install
> > network-0-0: Ethernet Switch 1 0 0 os install
> > compute-0-12: Compute 8 0 12 os install
> > network-0-1: Ethernet Switch 1 0 1 os install
> > compute-0-13: Compute 8 0 19 os install
> > compute-0-20: Compute 8 0 20 os install
> >
> > I'm pretty sure I already tried the suggestion from above, in our case to
> > run:
> > insert-ethers --replace compute-0-20. I see it in my history command. That
> > appeared to cause all the errors I mentioned in
> >
> > https://urldefense.com/v3/__https://lists.sdsc.edu/pipermail/npaci-rocks-discussio \
> > n/2020-October/073641.html__;!!LkSTlj0I!Se6HmnCqUl71K3kDghB--pi4tjf4px2iiIY-HLNp-1IJsWAGK56Ra17E_5xPg1PGLGA$
> >
> >
> > Why would it just to compute-0-20 when there's no 14-19 in the Rocks
> > database?
> >
> > Hoping for some sage advice to do it correctly this time...
> >
> > Thanks,
> >
> > Rob
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL:
> > https://urldefense.com/v3/__http://lists.sdsc.edu/pipermail/npaci-rocks-discussion \
> > /attachments/20201009/bc35e0ca/attachment.html__;!!LkSTlj0I!Se6HmnCqUl71K3kDghB--pi4tjf4px2iiIY-HLNp-1IJsWAGK56Ra17E_5xPgsvkATo$
> >
> >
> >
> >
>
> --
> Philip Papadopoulos, Ph.D
> Director, Research Cyber Infrastructure Center
> University of California, Irvine
> E-mail: ppapadop@uci.edu
> Phone: (949) 824-5343
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20201028/ef6d3f6e/attachment.html \
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic