Based on the LOCK_GULM locking protocol, the following list defines what can or cannot be changed in a CCS archive while a cluster is running. There are no restrictions to making changes to configuration files when the cluster is offline.
New nodes can be defined in the nodes.ccs file.
Unused node definitions can be removed from the nodes.ccs file.
New fencing devices can be defined in the fence.ccs file.
The locking servers array (servers =) in cluster.ccs:cluster/lock_gulm cannot be changed.
The fencing parameters for an existing node definition in nodes.ccs can be changed.
The IP address of an existing node definition in the nodes.ccs file can only be changed if the node does not have any GFS file systems mounted and is not running a LOCK_GULM server.
This example procedure shows how to change configuration files in a CCS archive.
Extract configuration files from the CCA device into temporary directory /root/alpha-new/.
ccs_tool extract /dev/pool/alpha_cca /root/alpha-new/ |
Make changes to the configuration files in /root/alpha-new/.
Create a new CCS archive on the CCA device by using the -O (override) flag to forcibly overwrite the existing CCS archive.
ccs_tool -O create /root/alpha-new/ /dev/pool/alpha_cca |