mikem

Overview

The kitops tool is responsible for adding and removing kits to/from a Kusu cluster. A kit is additional software bundled in a specific way, making it easy to outfit your cluster according to your needs.
Some examples of kits are the Nagios or Cacti kits, providing monitoring to your cluster, or the [HPC kit], containing various MPI libraries and related tools. The kitops tool itself, along with the complete suite of Kusu tools, is bundled in our Base Kit.
Operating systems are also kits. Additional Linux distribution kits enable heterogeneous clusters, such as a mix of 32-bit Fedora and 64-bit CentOS nodes.

Kits

A kit consists of the kit package, component packages and optionally of additional software packages. The kit package can contain plugins for Kusu tools, kit documentation and kit meta information in the form of a kitinfo file.
Refer to Kusu Kits for more details about kits in Kusu.

Adding Kits

kitops handles adding the kit to the Kusu database. The kit can be added from a CD or DVD, an ISO image, a directory containing the kit or an HTTP URL to an ISO file. kitops expects the kit, component and software packages in a subdirectory. For example, the Cacti kit directory structure on a CD mounted at /mnt/cdrom would look as follows:

Code:

$ tree /mnt/cdrom/
/mnt/cdrom/
|-- TRANS.TBL
`-- cacti
    |-- TRANS.TBL
    |-- cacti-0.8.6j-1.noarch.rpm
    |-- cacti-cactid-0.8.6i-1.x86_64.rpm
    |-- cacti-node-1-1.noarch.rpm
    |-- component-cacti-0.1-0.noarch.rpm
    |-- component-cacti-monitored-node-0.1-0.noarch.rpm
    |-- kit-cacti-0.1-0.x86_64.rpm
    `-- rrdtool-1.2.23-3.el5.x86_64.rpm

Note the TRANS.TBL files are generated by mkisofs.
For RPM based Linux distributions he kit package follows the format kit-{kit_name}-{kit_version}-{kit_release}.{kit_arch}.rpm and component packages follow the format component-{component_name}-{component_version}-{component_release}.{component_arch}.rpm.

The kit is recorded into the [Kusu database]'s kits and components tables. Kit metadata is obtained from the kitinfo file generated by buildkit and bundled in the kit package. If a kitinfo file is not found, kitops will try to get what it needs from the package files it finds.

All the kit packages are copied into /depot/kits/{kit_name}/{kit_version}/{kit_arch}.

OS kits do not need to be prepared in any way. Simply directing kitops to the OS media obtained from the distribution when adding a kit will suffice. They also don't have kit or component packages or a kitinfo file.

See [Adding a Kit] for the complete process for installing software on your cluster.

Removing Kits

Once a kit's components are no longer associated with any nodegroups and the kit has been removed from all repositories, kitops will remove the kit information from the database and the relevant files in the /depot/kits/ directory tree.