HP XC System Software Administration Guide Version 3.0

# service nconfig nconfigure
# service nconfig restart
6. Run the following commands to run the per-node configuration service on all the client nodes:
# cexec -x `nodename` -a "service nconfig nconfigure"
# cexec -x `nodename` -a "service nconfig restart"
Using the cexec Command
You can use the cexec command to copy designated files to client nodes.
Its advantage is that it is performed immediately, and potentially with little effect on the HP XC system
configuration files, presuming the file list does not contain any configuration files that require the restarting
of services.
Its disadvantages are that you must copy the files or directories and that you must update the golden image
to sustain the change when the node is reimaged.
Note
The cexec command performs a maximum of 32 simultaneous commands by default. Use the -f option to
specify a different maximum.
Maintaining Service Configuration Globally
When the golden image is updated from the golden client, the list of system services that are started
automatically on each client is set based on a template file,
/opt/hptc/systemimager/etc/chkconfig.map. This template attempts to turn on only those services
that should be run on all nodes. This provides a common denominator for a golden image that must serve
all client nodes.
The global and node-specific configuration framework (gconfig and nconfig) configures additional
node-specific services, as the node is initially installed, based on how the HP XC system was defined during
configuration.
If you are adding software that contains services that should run on all nodes, see “Propagating the Golden
Image to All Nodes” (page 86) for the instructions on updating the golden image and propagating it to
client nodes if this software provides a system service that should be started automatically on all client nodes
on system reboot. If the service is not automatically turned on as a result of the software installation process,
use the chkconfig command to start the service on the head node before updating the golden image. For
example:
# chkconfig --level 2345 service on
Add an entry in the /opt/hptc/systemimager/etc/chkconfig.map file whenever you add a new
service, regardless of whether it applies globally to the HP XC system or is specific to one node or several
nodes. This entry ensures that the correct service orientation (ON or OFF) in the golden image is always
maintained.
To install software that contains services appropriate for only one or a handful of nodes, update the
chkconfig.map file to add the name of the service, so that the golden image will maintain the service in
the default OFF orientation, because few nodes run this service. Use the following procedure:
1. Log in as the superuser on the head node.
2. Use the squeue command to ensure that no current LSF-HPC jobs are running and that the SLURM
queues are idle.
3. Install the software on the golden client.
Note the names of the services that are created as a result.
4. Create global or node-specific configuration files (gconfig or nconfig) or both, if the services will
run only on some specialized nodes.
5. Place the gconfig files in /opt/hptc/etc/gconfig.d, the nconfig files in
/opt/hptc/etc/nconfig.d, and the configuration files in /opt/hptc/etc/cconfig.d, using
an appropriate priority ordering based on the prefix of the file name.
88 Distributing Software Throughout the System