crm_diff(8) [suse man page]
CRM_DIFF(8) [FIXME: manual] CRM_DIFF(8) NAME
crm_diff - identify changes to the cluster configuration and apply patches to the configuration files SYNOPSIS
crm_diff [-?|-V] [-o filename] [-O string] [-p filename] [-n filename] [-N string] DESCRIPTION
The crm_diff command assists in creating and applying XML patches. This can be useful for visualizing the changes between two versions of the cluster configuration or saving changes so they can be applied at a later time using cibadmin. OPTIONS
--help, -? Print a help message. --original filename, -o filename Specify the original file against which to diff or apply patches. --new filename, -n filename Specify the name of the new file. --original-string string, -O string Specify the original string against which to diff or apply patches. --new-string string, -N string Specify the new string. --patch filename, -p filename Apply a patch to the original XML. Always use with -o. --cib, -c Compare or patch the inputs as a CIB. Always specify the base version with -o and provide either the patch file or the second version with -p or -n, respectively. --stdin, -s Read the inputs from stdin. EXAMPLES
Use crm_diff to determine the differences between various CIB configuration files and to create patches. By means of patches, easily reuse configuration parts without having to use the cibadmin command on every single one of them. 1. Obtain the two different configuration files by running cibadmin on the two cluster setups to compare: cibadmin -Q > cib1.xml cibadmin -Q > cib2.xml 2. Determine whether to diff the entire files against each other or compare just a subset of the configurations. 3. To print the difference between the files to stdout, use the following command: crm_diff -o cib1.xml -n cib2.xml 4. To print the difference between the files to a file and create a patch, use the following command: crm_diff -o cib1.xml -n cib2.xml > patch.xml 5. Apply the patch to the original file: crm_diff -o cib1.xml -p patch.xml FILES
/var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged. SEE ALSO
??? AUTHOR
crm_diff was written by Andrew Beekhof. [FIXME: source] 07/05/2010 CRM_DIFF(8)
Check Out this Related Man Page
PACEMAKER(8) System Administration Utilities PACEMAKER(8) NAME
Pacemaker - Part of the Pacemaker cluster resource manager SYNOPSIS
cibadmin command [options] [data] DESCRIPTION
cibadmin - Provides direct access to the cluster configuration. Allows the configuration, or sections of it, to be queried, modified, replaced and deleted. Where necessary, XML data will be obtained using the -X, -x, or -p options OPTIONS
-?, --help This text -$, --version Version information -V, --verbose Increase debug output Commands: -u, --upgrade Upgrade the configuration to the latest syntax -Q, --query Query the contents of the CIB -E, --erase Erase the contents of the whole CIB -B, --bump Increase the CIB's epoch value by 1 -C, --create Create an object in the CIB. Will fail if the object already exists. -M, --modify Find the object somewhere in the CIB's XML tree and update it. Fails if the object does not exist unless -c is specified -P, --patch Supply an update in the form of an xml diff (See also: crm_diff) -R, --replace Recursivly replace an object in the CIB -D, --delete Delete the first object matching the supplied criteria, Eg. <op id="rsc1_op1" name="monitor"/> The tagname and all attributes must match in order for the element to be deleted -d, --delete-all When used with --xpath, remove all matching objects in the configuration instead of just the first one -5, --md5-sum Calculate the on-disk CIB digest -6, --md5-sum-versioned Calculate an on-the-wire versioned CIB digest -S, --sync (Advanced) Force a refresh of the CIB to all nodes -a, --empty Output an empty CIB Additional options: -f, --force -t, --timeout=value Time (in seconds) to wait before declaring the operation failed -s, --sync-call Wait for call to complete before returning -l, --local Command takes effect locally. Should only be used for queries -c, --allow-create (Advanced) Allow the target of a -M operation to be created if they do not exist -n, --no-children (Advanced) When querying an object, do not return include its children in the result Data: -X, --xml-text=value Retrieve XML from the supplied string -x, --xml-file=value Retrieve XML from the named file -p, --xml-pipe Retrieve XML from stdin -A, --xpath=value A valid XPath to use instead of -o -o, --scope=value Limit the scope of the operation to a specific section of the CIB. Valid values are: nodes, resources, constraints, crm_config, rsc_defaults, op_defaults, status -N, --node=value (Advanced) Send command to the specified host EXAMPLES
Query the configuration from the local node: # cibadmin --query --local Query the just the cluster options configuration: # cibadmin --query --scope crm_config Query all 'target-role' settings: # cibadmin --query --xpath "//nvpair[@name='target-role']" Remove all 'is-managed' settings: # cibadmin --delete-all --xpath "//nvpair[@name='is-managed']" Remove the resource named 'old': # cibadmin --delete --xml-text '<primitive id="old"/>' Remove all resources from the configuration: # cibadmin --replace --scope resources --xml-text '<resources/>' Replace the complete configuration with the contents of $HOME/pacemaker.xml: # cibadmin --replace --xml-file $HOME/pacemaker.xml Replace the constraints section of the configuration with the contents of $HOME/constraints.xml: # cibadmin --replace --scope constraints --xml-file $HOME/constraints.xml Increase the configuration version to prevent old configurations from being loaded accidentally: # cibadmin --modify --xml-text '<cib admin_epoch="admin_epoch++"/>' Edit the configuration with your favorite $EDITOR: # cibadmin --query > $HOME/local.xml # $EDITOR $HOME/local.xml # cibadmin --replace --xml-file $HOME/local.xml SEE ALSO: CRM shell, crm(8), crm_shadow(8) AUTHOR
Written by Andrew Beekhof REPORTING BUGS
Report bugs to pacemaker@oss.clusterlabs.org Pacemaker 1.1.7 April 2012 PACEMAKER(8)