[Rocks-Discuss] Safest way to rename compute nodes

1,606 views
Skip to first unread message

JP

unread,
Nov 7, 2011, 4:42:42 AM11/7/11
to Discussion of Rocks Clusters
Hi using the great Rocks Viper (5.4.3).

I had some teething problems with insert-ethers (I was getting roughly two
entries for each compute node - so somehow there must have been two dhcp
requests being issued. Could have been a switch issue).

Anyway I removed the ones which were not the actual compute nodes (the ones
which did not respond to "rocks run host hostname") and now I am left with
a non continuous list of compute nodes

[root@xxx ~]# rocks list host
HOST MEMBERSHIP CPUS RACK RANK RUNACTION INSTALLACTION
xxx: Frontend 8 0 0 os install
compute-0-1: Compute 4 0 1 os install
compute-0-0: Compute 4 0 0 os install
compute-0-3: Compute 4 0 3 os install
compute-0-7: Compute 4 0 7 os install
compute-0-9: Compute 4 0 9 os install
compute-0-11: Compute 4 0 11 os install
compute-0-12: Compute 4 0 12 os install
compute-0-15: Compute 4 0 15 os install

So my question and TL;DR is: Any idea how I can safely rename node
compute-0-15 to compute-0-2 ?

-
Jean-Paul Ebejer
Early Stage Researcher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20111107/549ba3a3/attachment.html

Philip Papadopoulos

unread,
Nov 7, 2011, 5:11:08 PM11/7/11
to Discussion of Rocks Clusters
The extra entries are almost certainly happening because your nodes have
IPMI enabled (and requesting DHCP).

For what you want to do:
Try this:

# rocks dump host > /tmp/myhosts
# rocks dump host interface >> /tmp/myhosts

Then edit the /tmp/myhosts with some global replaces e.g.
s/compute-0-3/compute-0-2/g
s/compute-0-7/compute-0-3/g

etc.
until you have renamed the nodes and their interfaces in this file.

Then,
1. remove all compute nodes
eg. rocks remove host compute-0-3 compute-0-7 ...
2. sync the config
# rocks sync config
3. re-add the nodes back into the DB.
# sh /tmp/myhosts
4. sync the config again
# rocks sync config
5. set the nodes to reinstall
# rocks set host boot action=install compute
6. reinstall the nodes
# rocks run host compute "shutdown -r now"

-P


--
Philip Papadopoulos, PhD
University of California, San Diego
858-822-3628 (Ofc)
619-331-2990 (Fax)


-------------- next part --------------
An HTML attachment was scrubbed...

URL: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20111107/44a517e2/attachment.html

JP

unread,
Nov 8, 2011, 6:14:30 AM11/8/11
to Discussion of Rocks Clusters
On 7 November 2011 22:11, Philip Papadopoulos <philip.pa...@gmail.com
> wrote:

>
> Then,
> 1. remove all compute nodes
> eg. rocks remove host compute-0-3 compute-0-7 ...
> 2. sync the config
> # rocks sync config
> 3. re-add the nodes back into the DB.
> # sh /tmp/myhosts
> 4. sync the config again
> # rocks sync config
> 5. set the nodes to reinstall
> # rocks set host boot action=install compute
> 6. reinstall the nodes
> # rocks run host compute "shutdown -r now"
>

I assume at point 6. insert-ethers is switched off on the front end (since
we added the nodes in 3.)

Correct?


-------------- next part --------------
An HTML attachment was scrubbed...

URL: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20111108/7e4c89a1/attachment.html

Philip Papadopoulos

unread,
Nov 8, 2011, 9:46:39 AM11/8/11
to Discussion of Rocks Clusters
correct.
insert-ethers is used for discovery and automatically assigning names/IP
addresses.

-P

--
Philip Papadopoulos, PhD
University of California, San Diego
858-822-3628 (Ofc)
619-331-2990 (Fax)

-------------- next part --------------
An HTML attachment was scrubbed...

URL: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20111108/48f8e61b/attachment.html

Reply all
Reply to author
Forward
0 new messages