HP XC System Software Administration Guide Version 3.2

4.6.2 Service Configuration Sequence of Operation
To understand the relationship between the cluster_config utility and the service
configuration scripts, it is important to know the sequence of events that occur during
cluster_config processing:
1. Service-specific attributes are made available to the cluster_config utility in
service-specific *.ini files.
2. As the superuser (root), you run the cluster_config utility on the head node to configure
the HP XC system.
3. You assign roles to nodes (and thus, services) through the cluster_config text-based
user interface menu options.
4. During cluster_config processing, sconfigure scripts (system configuration) are
invoked to perform systemwide configuration of policies and other non-service-related
configuration.
5. During cluster_config processing, gconfigure scripts (global configuration) are
invoked to configure services, clients, and server-to-client assignments.
6. The golden image is created.
7. The node-specific nconfigure scripts run during cluster_config processing on the
head node to configure services specific to the head node.
The nconfigure scripts are invoked after imaging or reboot on the other nodes. These
scripts configure services appropriate to the specific nodes.
8. The cconfigure (client configuration) scripts run during cluster_config processing
on the head node to configure client services specific to the head node.
The cconfigure scripts are invoked after imaging or reboot on the other nodes. These
scripts configure client services appropriate to the specific nodes.
4.6.3 Assigning Roles with the cluster_config Utility
The cluster_config utility invokes a text-based user interface for assigning roles (and thus
services) to nodes. This interface accounts for scalability both in its initial default configuration
(server placement) and how it assists you to configure your system.
After you use the cluster_config utility to assign roles and to configure external Ethernet
connections, you are prompted for the optional expert services configuration portion of the
cluster_config processing, which is delivered in the configuration scripts.
The output of the role assignment process is a list of servers assigned per service. The list of
servers assigned per service is made available to the gconfigure scripts. Each gconfigure
script assigns clients across all the servers passed to it, if possible, as a means of achieving
scalability.
4.6.4 The *config.d Directories
As part of the system configuration process, the cluster_config utility searches the
configuration script directories listed in Table 4-4 and runs the configuration scripts found in
those directories. Table 4-4 lists the directories in the order in which they are accessed and
provides the argument used to run the script.
Table 4-4 Location of Configuration Script Directories
Invoked by This cluster_config
Unconfiguration Argument
Invoked by This cluster_config
Configuration ArgumentScript Directory
sunconfiguresconfigure/opt/hptc/etc/sconfig.d/
gunconfiguregconfigure/opt/hptc/etc/gconfig.d/
66 Managing and Customizing System Services