NAME

cstatus - program to status Cplant(tm) cluster


MODULE

base


DESCRIPTION

cstatus is a front end program used for status'ing nodes and optionally devices in the cluster.


USAGE

cstatus [OPTION]


OPTIONS

Where n is node-number

Where R is Rack-number

Where < text > is the specification required by the OPTION switch

Where [ text ] is the specification that is allowed but not required by the OPTION switch.

--teal, -t < R | R,R | R-R >
Specification of a single, multiple, or inclusive range of racks in the "teal" or "t" Series.

--red, -r < R | R,R | R-R >
Same but for "red" or "r" Series racks.

--yellow, -y < R | R,R | R-R >
Same but for "yellow" or "y" Series racks.

--green, -g < R | R,R | R-R >
Same but for "green" or "g" Series racks.

--blue, -b < R | R,R | R-R >
Same but for "blue" or "b" Series racks.

--node, --nodes, -n < n | n,n | n-n >
Same but for "nodes" .

--leader, --leaders
Providing this switch will have the effect of interpreting the rack specifications listed above to be leader designations. To illustrate by example providing --leader -t 0 will specify the required action to be executed on the leader(s) of the nodes in the collection t-0.

--vmname, --vm "virtual machine name"
Providing this switch will have the effect of selecting nodes that are members of the vm specified. This switch is dependent on the vmname attribute being set and being accurate for the desired outcome.

--man
displays this manual page

--usage
Displays short usage information about available options

--debug n Where n is a numeric level of debug information required, prints extra output for debugging purposes.
--libdebug class
Where class is the class from the base libs that you wish to output debug information from. Ex. cstatus -t 0 -n 0 --libdebug Device::Node::Alpha

Rack Designations:

Color Physical Label device specification

Red (R0-Tn) r-n

Teal (T0-Tn) t-n

Green (G0-Gn) g-n

Yellow (Y0-Yn) y-n

Blue (B0-Bn) b-n


CURRENT FUNCTIONALITY

cstatus can be used to status a "cluster" in many different ways, it is intended that cstatus allows the user great freedom in how it is used.

One common use for cstatus might be to just cut and past the arguments provided to cboot (less the --boot or --power options) to status the same nodes that were just powered or booted.

EXAMPLES

To status an entire rack of equipment. The following command will determine what the leader node is for the rack, status it first if successful status the nodes in the rack.

cstatus -r 0

The following command will do the same on a range of racks.

cstatus -r 0-5

To specify specific nodes on a rack to status The following will status nodes 4 6 and 7 on rack r-5

cstatus -r 5 -n 4,6,7

To specify the same nodes on multiple racks

cstatus -r 5,7 -n 4,6,7

Also works for a range of racks.

cstatus -r 5-7 -n 4,6,7

To status the leaders on a range of racks, useful if you don't know who the leaders are for particular racks.

cstatus -r 5-12 --leader

To status all of the nodes in a particular virtual machine.

cstatus --vm default

To status only the nodes that are in particular racks and also in a particular virtual machine.

cstatus --vm default -r 0,5

Cstatus can also be used with simple command line input. Just list the device or collection as it appears in the database on the command line.

cstatus node.n-0.t-0

cstatus t-0

To get extra debug information on any of the above commands add the --debug n switch.

To get library debug information on any of the above commands add the --libdebug <class> switch. Note this will probably not be very useful for anyone other than library developers.


FILES

/<install_dir>/bin/status

/<install_dir>/lib/Parse.pm

/<install_dir>/lib/Local.pm


SEE ALSO

The status document.

Questions, comments, bugs should be sent to jhlaros@sandia.gov


NAME

cstatus - program to status nodes in cluster


MODULE

base