beosi collects configuration information from either the head node or compute nodes on a BProc cluster into an archive file. beosi can also be used to extract information from a previously-assembled archive.
The file produced when using the -m or -n options is of the form conf-date.encoded where date indicates the current year, month, and day. This file is a gzipped tar file that has been encoded using uuencode to enable portability.
This utility can be used to capture configuration information for later retrieval or comparison. For example, if the current configuration is working, you can store a copy of it using beosi. If a configuration change causes your cluster to stop working, you can create another archive, extract it, and examine the differences between the two configurations (e.g. using diff) to determine which change caused the problem.
The following options are available to the beosi program.
Collect information about the head (master) node. Produces a uuencoded, gzipped tar file in the current directory called conf-date.encoded
Collect information about individual (compute) nodes. Produces a uuencoded, gzipped tar file in the current directory called conf-date.encoded
Decodes information from a configuration archive created previously by beosi. The result is a gzipped tar file with the same root filename.
To inspect the configuration information on the head node, first run:
[user@cluster user]$ beosi -m [user@cluster user]$ ls conf-05-11-31.encoded
Then examine the information, like so:
[user@cluster user]$ beosi -d conf-05-11-31.encoded [user@cluster user]$ tar zxvf conf-05-11-31.tar.gz conf-05-11-31/ conf-05-11-31/master/ conf-05-11-31/master/dmesg conf-05-11-31/master/lsmod conf-05-11-31/master/syslog ...
Use a prior configuration to compare individual files:
[user@cluster user]$ diff -u conf-05-11-3?/master/uname --- conf-05-11-30/master/uname 2005-11-22 15:43:28.000000000 -0800 +++ conf-05-11-31/master/uname 2005-11-22 15:43:58.000000000 -0800 @@ -1 +1 @@ ...