Thread: Kusu Base Kit and Bootable ISO

Kit, Component and Node Group

Kits are pre-packaged applications or services that once added to a KUSU/OCS cluster can be automatically installed and configured onto cluster nodes.



As shown in the above figure, kits collect components into a simple package and components add an extra layer of dependency abstraction necessary for installing and configuring services in a cluster. The following queries indicate the association between a kit and its components:



A node group is a template that defines the properties of cluster nodes. The following queries indicate the association between node group, kits and components:




Base Kit

The Base Kit is made up of 2 components:

• component-base-installer
  • This component provides the primary install node with various Kusu management tools.
  • By default, this component is enabled on the Kusu primary install node.
• component-base-node
  • This component provides nodes in the Kusu cluster with the Kusus runtime for non-install-type nodes.
  • By default, this component is associated with compute, compute-imaged, and compute-diskless nodegroups.

Bootable ISO

The following figure lists the contents of the bootable ISO for setting up KUSU master.

• base directory includes all the RPM packages that are required for installing Base Kit, such as kit-base-1.1-1.i386.rpm.
• images directory includes two .img files.
  • The system anaconda is the major component of stage2.img which is used for installing the actual OS. stage2.img is coming from standard OS (Centos, RedHat, Fedora) iso.
  • updates.img mainly contains the Kusu faux anaconda loader which triggers the Kusu installer and finally triggers the system anaconda; opt directory contains the codes of Kusu installer including Kusu installation screens and the backend functions; thttpd-run.sh script starts HTTPD service for kickstart installation.
• isolinux directory has all the files for system initial bootup. isolinux.bin firstly boots up based on isolinux.cfg where passes the first kickstart file -- the ks.cfg shown in the above figure.
• splash.lss is the background picture of the Kusu boot loader.
• During the initial bootup, initrd.img and vmlinuz will be loaded, where initrd.img and vmlinuz are directly from standard OS iso, however Kusu custom kickstart script is packed into the initrd.img.

Kusu Master Installation

The following diagram shows the process of the installation of KUSU master.



Please refer to Kusu Installation Overview for the detailed description of the process.