Rocks Cluster Distribution: Users Guide: 
| ||
|---|---|---|
| Prev | Chapter 1. Installing a Rocks Cluster | Next |
Login to the frontend node as root.
Run a program which captures compute node DHCP requests and puts their information into the Rocks MySQL database:
# insert-ethers |
This presents a screen that looks like:
 | If your your frontend and compute nodes are connected via a managed ethernet switch, you'll want to select 'Ethernet Switches' from the list above. This is because the default behavior of many managed ethernet switches is to issue DHCP requests in order to receive an IP address that clients can use to configure and monitor the switch. When insert-ethers captures the DHCP request for the managed switch, it will configure it as an ethernet switch and store that information in the MySQL database on the frontend. As a side note, you may have to wait several minutes before the ethernet switch broadcasts its DHCP request. If after 10 minutes (or if insert-ethers has correctly detected and configured the ethernet switch), then you should quit insert-ethers by hitting the F10 key. Now, restart insert-ethers and continue reading for a procedure on how to configure your compute nodes. |
Take the default selection, Compute, hit 'Ok'.
Then you'll see:
This indicates that insert-ethers is waiting for new compute nodes.
Take the Kernel Roll CD and put it in your first compute node -- this is the bottom compute node in your first cabinet.
 | If you don't have a CD drive in your compute nodes, you can use PXE (Network Boot). |
| If you don't have a CD drive in your compute nodes and if the network adapters in your compute nodes don't support PXE, see Using a Floppy to PXE boot. |
Power up the first compute node.
When the frontend machine receives the DHCP request from the compute node, you will see something similar to:
This indicates that insert-ethers received the DHCP request from the compute node, inserted it into the database and updated all configuration files (e.g., /etc/hosts, /etc/dhcpd.conf, DNS and batch system files).
The above screen will be displayed for a few seconds and then you'll see the following:
Figure: insert-ethers has discovered a compute node. The "( )" next to compute-0-0 indicates the node has not yet requested a kickstart file.
You will see this type of output for each compute node that is successfully identified by insert-ethers.
| As a kickstart file contains 411 keys and other sensitive information in plaintext, it is sent encrypted over the network. In addition, only recognized nodes are allowed to request one. Since insert-ethers is the tool used to identify new nodes, it must be used with care. If security is a concern, be suspicious of unknown MAC addresses in the insert-ethers window. |
Figure: The compute node has successfully requested a kickstart file from the frontend. If there are no more compute nodes, you may now quit insert-ethers. Kickstart files are retrieved via https. If there was an error during the transmission, the error code will be visible instead of "*".
At this point, you can monitor the installation by using rocks-console. Just extract the name of the installing compute node from the insert-ethers output (in the example above, the compute node name is compute-0-0), and execute:
# rocks-console compute-0-0 |
| You must be running X on the frontend in order to use rocks-console. |
When the installation is complete, the CD will eject. Take the CD out of the tray and put it into the next compute node above the one you just installed and hit the power button.
After you've installed all the compute nodes in a cabinet, quit insert-ethers by hitting the 'F10' key.
After you've installed all the compute nodes in the first cabinet and you wish to install the compute nodes in the next cabinet, just start insert-ethers like:
# insert-ethers --cabinet=1 |
This will name all new compute nodes like compute-1-0, compute-1-1, ...