cmapplyconf
-C
${config}
Applies the configuration files checked above.
Appears to repeat the configuration file checks, so checking them first may
be redundant.
-P ${config}
-p ${file}
cmcheckconf -C ${config} Configuration file checker. The -C checks cluster configuration files; -Pchecks package configuration files, and the -p checks all the configuration files listed in ${file} -P ${config} -p ${file}
cmdeleteconf -p Removes cluster configuration information. Use the -p option to remove package definitions from the existing cluster. I imagine there's more options; however, that one would seem to be the most used.
cmgetconf -c ${cluster} Generates configuration files that generated the existing cluster or package. Useful for identifying current configurations and for replacing configuration files that have been wiped out. Probably a good idea to use this to generate a config file to edit vs trying to keep track of changes on all cluster nodes. -p ${pkg}
cmhaltcl [ -f ] Halts a cluster. If any pakcages are running and the -f option is not supplied, the command will fail and complain about the running packages. Using the -f option will force the packages to halt before killing the cluster
cmhaltnode -f Halts a running node. Using the -f flag will switch any packages running on that particular node to an adoptive node. This command does not disable the global switch for any affected packages.
cmmakepkg -p ${config} Generates package configuration an run/halt scripts. The files generated must be edited prior to use. -p = package configuration while -s = run/halt script. -s ${script}
cmquerycl -n ${node} Use this command to set up the initial cluster configuration. Add a -noption for each node in the nascent cluster. The -C option specifies the cluster configuration file and the -v option requests verbose output. -C ${config} -v
cmruncl Starts up the cluster software and any configured packages on their primary nodes. cmrunnode Activate a previously halted node. DO NOT use this command to start up a cluster as the cluster reform process will hang. See "Hung cluster reformation" for solution to this problem.
cmscancl -s More detailed display of cluster configuration and status. -o will output to a file; -n will display information on ${node} only, and -s will display to the screen. -o ${file} -n ${node}
cmviewcl -v, Primary method for checking on the health and status of a running cluster. With no command line arguments, the command will display the cluster status (up/down) and the nodes that are attached and their status. -v = verbose with fairly obvious results. Adding other modifiers, such as -p will limit the display to the specific subsystem requested (-p = packages>. use cmviewcl -vp ${pkg} to ID global and local switch settings. -p, -c (others?)
cmviewconf -o ${file} Displays cluster configuration information. If supplied with the -o ${file}option, will output the results to ${file}. It won't overwrite ${file} if it exists.
cmcheckconf -C ${config} Configuration file checker. The -C checks cluster configuration files; -Pchecks package configuration files, and the -p checks all the configuration files listed in ${file} -P ${config} -p ${file}
cmdeleteconf -p Removes cluster configuration information. Use the -p option to remove package definitions from the existing cluster. I imagine there's more options; however, that one would seem to be the most used.
cmgetconf -c ${cluster} Generates configuration files that generated the existing cluster or package. Useful for identifying current configurations and for replacing configuration files that have been wiped out. Probably a good idea to use this to generate a config file to edit vs trying to keep track of changes on all cluster nodes. -p ${pkg}
cmhaltcl [ -f ] Halts a cluster. If any pakcages are running and the -f option is not supplied, the command will fail and complain about the running packages. Using the -f option will force the packages to halt before killing the cluster
cmhaltnode -f Halts a running node. Using the -f flag will switch any packages running on that particular node to an adoptive node. This command does not disable the global switch for any affected packages.
cmmakepkg -p ${config} Generates package configuration an run/halt scripts. The files generated must be edited prior to use. -p = package configuration while -s = run/halt script. -s ${script}
cmquerycl -n ${node} Use this command to set up the initial cluster configuration. Add a -noption for each node in the nascent cluster. The -C option specifies the cluster configuration file and the -v option requests verbose output. -C ${config} -v
cmruncl Starts up the cluster software and any configured packages on their primary nodes. cmrunnode Activate a previously halted node. DO NOT use this command to start up a cluster as the cluster reform process will hang. See "Hung cluster reformation" for solution to this problem.
cmscancl -s More detailed display of cluster configuration and status. -o will output to a file; -n will display information on ${node} only, and -s will display to the screen. -o ${file} -n ${node}
cmviewcl -v, Primary method for checking on the health and status of a running cluster. With no command line arguments, the command will display the cluster status (up/down) and the nodes that are attached and their status. -v = verbose with fairly obvious results. Adding other modifiers, such as -p will limit the display to the specific subsystem requested (-p = packages>. use cmviewcl -vp ${pkg} to ID global and local switch settings. -p, -c (others?)
cmviewconf -o ${file} Displays cluster configuration information. If supplied with the -o ${file}option, will output the results to ${file}. It won't overwrite ${file} if it exists.
