6장. Saving a configuration change to a working file

Procedure

1. Save the active CIB to a file. This example saves the CIB to a file named original.xml.

   # pcs cluster cib original.xml

2. Copy the saved file to the working file you will be using for the configuration updates.

   # cp original.xml updated.xml

3. Update your configuration as needed. The following command creates a resource in the file updated.xml but does not add that resource to the currently running cluster configuration.

   # pcs -f updated.xml resource create VirtualIP ocf:heartbeat:IPaddr2 ip=192.168.0.120 op monitor interval=30s

4. Push the updated file to the active CIB, specifying that you are pushing only the changes you have made to the original file.

   # pcs cluster cib-push updated.xml diff-against=original.xml

5. Alternately, you can push the entire current content of a CIB file with the following command.

   # pcs cluster cib-push filename

6. When pushing the entire CIB file, Pacemaker checks the version and does not allow you to push a CIB file which is older than the one already in a cluster. If you need to update the entire CIB file with a version that is older than the one currently in the cluster, you can use the --config option of the pcs cluster cib-push command.

   # pcs cluster cib-push --config filename