HP XC System Software Administration Guide Version 3.1

All the nodes to be overriden must be linked.
7. Use the text editor of your choice to edit the /etc/systemimager/flamethrower.conf file.
Add an entry at the end of the file for the directory you created in the first step. In this example, add
the entry shown in bold:
[base_image]
DIR = /var/lib/systemimager/images/base_image
[override_n8_override]
DIR = /var/lib/systemimager/overrides/n8_override
[override_base_image]
DIR = /var/lib/systemimager/overrides/base_image
Save the file and exit the text editor.
8. Reimage the nodes:
# setnode --resync --all
# stopsys
# startsys --image_and_boot
9. Verify that the propagation occurred as expected by examining the files on the node.
10.3.3 Using Per-Node Service Configuration
The HP XC system configuration process uses per-node configuration scripts to achieve personalized role
configurations as necessary on each node. The per-node configuration process occurs initially during HP
XC system configuration, at the time each client node is auto-installed. The HP XC configuration and
management database (CMDB) contains the per-node role and service configuration, and is queried on
each node's initial boot to identify which roles and services to configure. See “Adding a New Service”
(page 71) for more information.
A per-node configuration script is associated with each configurable service, and is executed on the client
node if the CMDB identifies this client as hosting this service.
The per-node configuration process actually occurs in two phases:
• Global Service Configuration
The global configuration phase is intended to set up the per-node configuration phase by globally
configuring the service for use within the HP XC system. The global configuration of a service occurs
when a global configuration script (a gconfig script) is executed during the running of the
cluster_config utility. It is here that you interact with the cluster_config utility as necessary
to configure the service. In order to configure a new service into the HP XC system using gconfig,
you must run the cluster_config utility again.
The global configuration script can store information in the following locations:
CMDB Use the database as the target for node-specific configuration data,
that is, services that are not ubiquitous in the HP XC system, but run
on only one or a handful of nodes.
Golden client file system By writing to the golden client file system, the script can add or
modify files that are propagated to all nodes of the HP XC system by
using the golden image. This is useful for configuring services that
are ubiquitous in the HP XC system.
Cluster common storage
(/hptc_cluster)
By writing to the cluster common storage, the script is able to add or
modify files that are visible to all the nodes of the HP XC system. Use
this method for either per-node or clusterwide services.
As mentioned previously, the database is the destination for node-specific data. However, some
existing services may already place configuration data used by the service in files in known locations.
The golden client file system and the cluster common storage are available to support such applications.
134 Distributing Software Throughout the System