Cronograma de Actividades Diagrama de Gantt:

The Configured Nodes list box provides a pop-up menu for performing many operations related to the configuration and maintenance of "configured" nodes. When you right-click anywhere in this window, you are presented with the pop-up menu shown below.

Figure B-18. Configured Nodes Pop-Up Menu

Depending on the node being selected, its current state, and your current privilege level, some of the items on the menu may be disabled. The following table details the availability of a menu item with respect to the selected node’s current state. Table B-1. Configured Node List Pop-Up Menu Item Availability

Menu Items Down Unavailable Error Up Boot

Insert ena ena ena ena ena

Edit ena dis dis dis dis

Delete ena dis dis dis dis

Move to Ignored ena dis dis dis dis

Move to Unknown ena dis dis dis dis

View Syslog ena ena ena ena ena

Menu Items Down Unavailable Error Up Boot

Wake Up ena dis dis dis dis

Reboot dis ena ena ena ena

Halt dis ena ena ena ena

Power Off dis ena ena ena ena

Kill dis ena ena ena ena

Mark Up dis ena dis dis dis

Mark Unavailable dis dis dis ena dis

Note that the View Syslog... and View Beoboot Log... menu items are available to all users, regardless of their current privilege level. Of the remaining menu items shown in the table above, those listed as enabled are actually available only to users running beosetup with full privileges. These menu items will be disabled for those running with limited privileges. Some of the functionality provided with the pop-up menu can be performed using drag-and-drop operations with your mouse. These operations are discussed where appropriate. You can also use drag-and-drop to reorder the numbering of the nodes in your cluster. Simply drag a node from one location to another to renumber the list. Note that you are only able to drag a node when its state is anything other than up, unavailable, error or boot. Also note that when dragging nodes around the list, the position of up nodes is automatically maintained by beosetup.

For any changes you make in this window to take effect, you must be sure to apply them. Edit Ownership

This menu item opens the Edit Node dialog box, where you can edit the user, group, and mode of a node. You can also specify execute rights for the node.

Figure B-19. Edit Node Ownership

Edit Identity

This menu item lets you modify the Ethernet hardware (MAC) address for the currently selected node in the Configured

Nodes list box.

When initially displayed, the MAC Address field in the dialog box contains the selected node’s current Ethernet hardware (MAC) address. Simply change the address to the desired value and select the OK button. If your changes contain any errors, an error message box will be displayed, and your changes will be ignored. Simply reselect the menu item and try again. Once your changes have been applied, the selected node’s entry in the cluster config file is replaced with the new address. If you decide you no longer wish to change the node’s hardware address, simply select the Cancel button.

Note that a node’s MAC address is determined by the network interface card plugged in to the node. It should not be arbitrarily changed to another value unless you really know what you’re doing. The capability to modify the address is primarily provided to change an off node to a real address and as a convenience when replacing network cards.

Edit Node Order

This group of menus allows you to move, delete, and insert nodes in the Configured Nodes list box.

Figure B-21. Edit Node Order

Move to Ignored

This menu item moves the selected node from the Configured Nodes list box to the Ignored addresses list box. Once this change has been applied, the selected node is re-tagged in/etc/beowulf/configfrom node to ignore. As described in the section on numbering your cluster’s nodes, when moving a node out of this list an off node may be automatically inserted by beosetup to maintain the current numbering of up nodes.

Another way to perform this operation is by dragging and dropping nodes using your mouse. Simply select and drag the highlighted node from the Configured Nodes list box and drop it onto the Ignored addresses list box. The drag-and-drop operation is functionally equivalent to selecting this menu item.

Move to Unknown

This menu item moves the selected node from the Configured Nodes list box to the Unknown addresses list box. Once this change has been applied, the selected node is removed from /etc/beowulf/config and added to

/var/beowulf/unknown_addresses. As described in the section on numbering your cluster’s nodes, when moving a node out of this list an off node may be automatically inserted by beosetup to maintain the current numbering of up nodes.

Another way to perform this operation is by dragging and dropping nodes using your mouse. Simply select and drag the highlighted node from the Configured Nodes list box and drop it onto the Unknown addresses list box. The drag- and-drop operation is functionally equivalent to selecting this menu item.

Delete

This menu item deletes the selected node from the Configured Nodes list box. Once this change has been applied, the selected node is removed from/etc/beowulf/config. As described in the section on numbering your cluster’s nodes, when moving a node out of this list an off node may be automatically inserted by beosetup to maintain the current numbering of up nodes.

Insert

This menu item allows you to insert a node into the Configured Nodes list box directly above the node you selected when clicking your right mouse button. (If you happened to right click in the white space at the bottom of the list box, the new node is simply added to the end of the list.) The new node is initially given an address of off , which can be changed using the Edit... menu item. Once changed and applied, the newly inserted node is written to/etc/beowulf/config

using the node tag. As described in the section numbering your cluster’s nodes, beosetup will automatically insert the new node where appropriate so as to maintain the current numbering of up nodes.

View Syslog...

This menu item lets you view the master’s/var/log/messagesfile, filtered for messages about the selected node. This menu item is available to users of all privilege levels, all the time.

When you select this menu item, the window shown below is opened, displaying beoserv messages from when the node was given its IP addresses and boot images, as well as all of the compute node’s kernel log messages. If new information is added to the log file while this window is open, the window will automatically update with the new information.

You can display messages for another node in the cluster by entering the node number in the Node list box at the top of the window; you can also use the increment/decrement arrows to select a different node number.

You can search for specific information by entering a search string in the Search field. To remove this window from the screen, select the Close button.

Figure B-22. View the Syslog for a Node

View Beoboot Log...

This menu item lets you view the boot/status log for the selected node. This menu item is available to users of all privilege levels, all the time.

When you select this option, the window shown below is opened, displaying the contents of the node’s activity log file. The name of the log file is shown in the window’s title bar,/var/log/beowulf/node.#where "#" is replaced with the selected node’s number. If new information should be added to the log file while this window is displayed, the window will automatically update with the new information.

Figure B-23. View the Beoboot Log for a Node

Change Node State

This group of menus will allow you to change the state of "configured" nodes.

Figure B-24. Change Node State

Wake Up...

This menu item can be used to send a Wake On LAN message to the selected node. Wake-On-LAN is the generic name for the AMD "Magic Packet" technology. It’s very similar to the PCMCIA modem "wake on ring" signal line. The basic idea is that the network adapter has a very-low-power mode to monitor the network for special packet data that will wake up the machine. When this menu item is selected, the script/usr/lib/beoboot/bin/node_wakeis executed, which uses the ether-wake utility to generate and send the special data packet to the node.

Indicator on Indicator off Reboot... Halt... Power Off... Kill...

These last four menu items all perform somewhat related functions. In each case, the master node sends commands to the selected compute node using the script/usr/lib/beoboot/bin/node_down. The selected operation is passed to the script as a parameter. Reboot will cycle power to the node off and then on again. Halt will suspend the node. Power Off will shut off a node completely. Finally, Kill will totally disavow the node by changing its state to down. After selecting any one of these items, the following alert will be displayed:

Figure B-25. Node Shutdown Alert

You have 3 options:

• Selecting the Cancel button closes the message box, and the node will be left .

• If you select Abrupt Shutdown, the new state is directly passed on to the BProc distributed process space software, and the node responds accordingly.

• If you select Clean Shutdown, the selected operation is performed by running thenode_downscript. The following progress dialog box will be displayed during the operation:

Figure B-26. Clean Shutdown Progress

Although this dialog box contains a Cancel button, it is not recommended that you select it during a clean shutdown, as it is very likely to leave the selected node in an ambiguous state. When the operation completes, the Cancel button is renamed to Close, which can then be selected to close the dialog box. At any time, you can click the Show Details... button to enlarge the dialog and view the output from the execution of thenode_downscript.

Mark Up

Mark Unavailable

These two menu items allow you to change the selected node’s state. When the node’s state is up, you can mark it as

unavailable; when the node’s state is unavailable, you can mark it as up. The up and unavailable states are analogous

to the familiar computer terms on-line and off-line.

You may want to temporarily mark a node as unavailable to take if off-line for performing some routine maintenance. While the node is off-line, it will not be automatically used by the scheduler for running any jobs. Once you’ve completed your maintenance activities, simply mark the node as up and it’s back on-line again.