Adding kit components to nodes in a node group is very similar to adding additional RPM packages.

Each Red Hat HPC kit installs an application or a set of applications. The kit also contains components which are meta-RPM packages designed for installing and configuring applications within the cluster. By enabling the appropriate components, it is easy to configure all nodes in a node group.

For example, the Cacti kit contains two components, component-cacti and component-cacti-monitored-node. component-cacti installs and configures Cacti, sets up the web pages and connection to the database. This component is normally installed on the cluster installer node or any other node (or set of nodes) designated as the management node.

The other component in the Cacti kit, component-cacti-monitored-node contains the Cacti agent code that runs on compute nodes in the cluster.

Most Red Hat HPC Kits come configured with automatic node group association and component selection. In the case of the Cacti kit, all nodes within the compute-rhel node group have the component-cacti-monitored-node component enabled. This means these nodes are monitored by Cacti by default. The component does not need to be explicitly enabled as the Cacti kit does this automatically.

As another example, the Platform Lava kit automatically associates the Lava master with the installer node group and the Lava compute nodes with the compute-rhel node group. Installing the Lava kit automatically sets up and creates a usable Lava cluster without needing any additional configuration.