crm(8)

crm - Pacemaker command line interface for configuration and management

crm [OPTIONS] [SUBCOMMAND ARGS…]

The crm shell is a command-line based cluster configuration and management tool. Its goal is to assist as much as possible with the configuration and maintenance of Pacemaker-based High Availability clusters.

For more information on Pacemaker clusters, see http://clusterlabs.org/.

crm works both as a command-line tool to be called directly from the system shell, and as an interactive shell with extensive tab completion and help.

The primary focus of the crm shell is to provide a simplified and consistent interface to Pacemaker, but it also provides tools for managing the creation and configuration of High Availability clusters from scratch. To learn more about this aspect of crm, see the cluster section below.

The Pacemaker configuration is stored in something called a CIB file, where CIB stands for Cluster Information Base. The CIB is a set of instructions coded in XML which is synchronized across the cluster.

Editing the CIB is a challenge, not only due to its complexity and wide variety of options, but also because XML is more computer than user friendly. To help with this task, the crm shell provides a small and simple line-oriented configuration language consistent with the other commands available in the shell. For more information about this language and how to use it, see the configure section below.

crm provides a consistent and well-documented interface to most of the management tools included in Pacemaker, for example crm_resource(8) or crm_attribute(8). Instead of having to remember the various flags and options available for each tool, crm hides all of the arcane detail.

crm can also function as a cluster scripting tool, and can be fed multi-line sets of commands either directly from standard input or via a file. Templates with ready made configurations may help newbies learn about the cluster configuration or facilitate testing procedures.

The crm shell is line oriented: every command must start and finish on the same line. It is possible to use a continuation character (\) to write one command in two or more lines. The continuation character is commonly used when displaying configurations.

This section of the user guide covers general topics about the user interface and describes some of the features of crmsh in detail.

The main purpose of crmsh is to provide a simple yet powerful interface to the cluster stack. There are two main modes of operation with the user interface of crmsh:

Here are a few examples of using crm both as a command-line tool and as an interactive shell:

The crm interface is hierarchical, with commands organized into separate levels by functionality. To list the available levels and commands, either execute help <level>, or, if at the top level of the shell, simply typing help will provide an overview of all available levels and commands.

The (live) string in the crm prompt signifies that the current CIB in use is the cluster live configuration. It is also possible to work with so-called shadow CIBs. These are separate, inactive configurations stored in files, that can be applied and thereby replace the live configuration at any time.

The crm makes extensive use of tab completion. The completion is both static (i.e. for crm commands) and dynamic. The latter takes into account the current status of the cluster or information from installed resource agents. Sometimes, completion may also be used to get short help on resource parameters. Here are a few examples:

crmsh also comes with bash completion usable directly from the system shell. This should be installed automatically with the command itself.

The feature set of crmsh covers a wide range of functionality, and understanding how and when to use the various features of the shell can be difficult. This section of the guide describes some of the features and use cases of crmsh in more depth. The intention is to provide a deeper understanding of these features, but also to serve as a guide to using them.

A Shadow CIB is a normal cluster configuration stored in a file. They may be manipulated in much the same way as the live CIB, with the key difference that changes to a shadow CIB have no effect on the actual cluster resources. An administrator may choose to apply any of them to the cluster, thus replacing the running configuration with the one found in the shadow CIB.

The crm prompt always contains the name of the configuration which is currently in use, or the string live if using the live cluster configuration.

When editing the configuration in the configure level, no changes are actually applied until the commit command is executed. It is possible to start editing a configuration as usual, but instead of committing the changes to the active CIB, save them to a shadow CIB.

The following example configure session demonstrates how this can be done:

Resource definitions may be checked against the meta-data provided with the resource agents. These checks are currently carried out:

The parameter checks are obvious and need no further explanation. Failures in these checks are treated as configuration errors.

The timeouts for operations should be at least as long as those recommended in the meta-data. Too short timeout values are a common mistake in cluster configurations and, even worse, they often slip through if cluster testing was not thorough. Though operation timeouts issues are treated as warnings, make sure that the timeouts are usable in your environment. Note also that the values given are just advisory minimum---your resources may require longer timeouts.

User may tune the frequency of checks and the treatment of errors by the check-frequency and check-mode preferences.

Note that if the check-frequency is set to always and the check-mode to strict, errors are not tolerated and such configuration cannot be saved.

Configuration templates are ready made configurations created by cluster experts. They are designed in such a way so that users may generate valid cluster configurations with minimum effort. If you are new to Pacemaker, templates may be the best way to start.

We will show here how to create a simple yet functional Apache configuration:

We enter the template level from configure. Use the list command to show templates available on the system. The new command creates a configuration from the apache template. You can use tab completion to pick templates. Note that the apache template depends on a virtual IP address which is automatically pulled along. The list command shows the just created web configuration, among other configurations (I hope that you, unlike me, will use more sensible and descriptive names).

The show command, which displays the resulting configuration, may be used to get an idea about the minimum required changes which have to be done. All ERROR messages show the line numbers in which the respective parameters are to be defined:

The edit command invokes the preferred text editor with the web configuration. At the top of the file, the user is advised how to make changes. A good template should require from the user to specify only parameters. For example, the web configuration we created above has the following required and optional parameters (all parameter lines start with %%):

These lines are the only ones that should be modified. Simply append the parameter value at the end of the line. For instance, after editing this template, the result could look like this (we used tabs instead of spaces to make the values stand out):

As you can see, the parameter line format is very simple:

After editing the file, use show again to display the configuration:

The target resource of the apache template is a group which we named websvc in this sample session.

This configuration looks exactly as you could type it at the configure level. The point of templates is to save you some typing. It is important, however, to understand the configuration produced.

Finally, the configuration may be applied to the current crm configuration (note how the configuration changed slightly, though it is still equivalent, after being digested at the configure level):

Note that this still does not commit the configuration to the CIB which is used in the shell, either the running one (live) or some shadow CIB. For that you still need to execute the commit command.

To complete our example, we should also define the preferred node to run the service:

If you are not happy with some resource names which are provided by default, you can rename them now:

To summarize, working with templates typically consists of the following steps:

The amount of detail in a cluster makes all configurations prone to errors. By far the largest number of issues in a cluster is due to bad resource configuration. The shell can help quickly diagnose such problems. And considerably reduce your keyboard wear.

Let’s say that we entered the following configuration:

Before typing commit to submit the configuration to the cib we can make sure that all resources are usable on all nodes:

It is important that resources being tested are not running on any nodes. Otherwise, the rsctest command will refuse to do anything. Of course, if the current configuration resides in a CIB shadow, then a commit is irrelevant. The point being that resources are not running on any node.

Order of resources is significant insofar that a resource depends on all resources to its left. In most configurations, it’s probably practical to test resources in several runs, based on their dependencies.

Apart from groups, crm does not interpret constraints and therefore knows nothing about resource dependencies. It also doesn’t know if a resource can run on a node at all in case of an asymmetric cluster. It is up to the user to specify a list of eligible nodes if a resource is not meant to run on every node.

By default, the users from the haclient group have full access to the cluster (or, more precisely, to the CIB). Access control lists allow for finer access control to the cluster.

Access control lists consist of an ordered set of access rules. Each rule allows read or write access or denies access completely. Rules are typically combined to produce a specific role. Then, users may be assigned a role.

For instance, this is a role which defines a set of rules allowing management of a single resource:

The first two rules allow modifying the target-role and is-managed meta attributes which effectively enables users in this role to stop/start and manage/unmanage the resource. The constraints write access rule allows moving the resource around. Finally, the user is granted read access to the resource definition.

For proper operation of all Pacemaker programs, it is advisable to add the following role to all users:

For finer grained read access try with the rules listed in the following role:

It is however possible that some Pacemaker programs (e.g. ptest) may not function correctly if the whole CIB is not readable.

Some of the ACL rules in the examples above are expanded by the shell to XPath specifications. For instance, meta:bigdb:target-role expands to:

You can see the expansion by showing XML:

Many different XPath expressions can have equal meaning. For instance, the following two are equal, but only the first one is going to be recognized as shortcut:

XPath is a powerful language, but you should try to keep your ACL xpaths simple and the builtin shortcuts should be used whenever possible.

Using resource sets can be a bit confusing unless one knows the details of the implementation in Pacemaker as well as how to interpret the syntax provided by crmsh.

Three different types of resource sets are provided by crmsh, and each one implies different values for the two resource set attributes, sequential and require-all.

The three types of resource sets modify the attributes in the following way:

To create a set with the properties sequential=true and require-all=false, explicitly set sequential in a bracketed set, [ A B C sequential=true ].

To create multiple sets with both sequential and require-all set to true, explicitly set sequential in a parenthesis set: A B ( C D sequential=true ).

Attribute lists are used to set attributes and parameters for resources, constraints and property definitions. For example, to set the virtual IP used by an IPAddr2 resource the attribute ip can be set in an attribute list for that resource.

Attribute lists can have identifiers that name them, and other resources can reuse the same attribute list by referring to that name using an $id-ref. For example, the following statement defines a simple dummy resource with an attribute list which sets the parameter state to the value 1 and sets the identifier for the attribute list to on-state:

To refer to this attribute list from a different resource, refer to the on-state name using an id-ref:

The resource dummy-2 will now also have the parameter state set to the value 1.

In some cases, referencing complete attribute lists is too coarse-grained, for example if two different parameters with different names should have the same value set. Instead of having to copy the value in multiple places, it is possible to create references to individual attributes in attribute lists.

To name an attribute in order to be able to refer to it later, prefix the attribute name with a $ character (as seen above with the special names $id and $id-ref:

The identifier state can now be used to refer to this attribute from other primitives, using the @<id> syntax:

In some cases, using the attribute name as the identifier doesn’t work due to name clashes. In this case, the syntax $<id>:<name>=<value> can be used to give the attribute a different identifier:

There is also the possibility that two resources both use the same attribute value but with different names. For example, a web server may have a parameter server_ip for setting the IP address where it listens for incoming requests, and a virtual IP resource may have a parameter called ip which sets the IP address it creates. To configure these two resources with an IP without repeating the value, the reference can be given a name using the syntax @<id>:<name>.

Example:

We define a small and simple language. Most commands consist of just a list of simple tokens. The only complex constructs are found at the configure level.

The syntax is described in a somewhat informal manner: <> denotes a string, [] means that the construct is optional, the ellipsis (...) signifies that the previous construct may be repeated, | means pick one of many, and the rest are literals (strings, :, =).

Show cluster status. The status is displayed by crm_mon. Supply additional arguments for more information or different format. See crm_mon(8) for more details.

Usage:

Whole-cluster configuration management with High Availability awareness.

The commands on the cluster level allows configuration and modification of the underlying cluster infrastructure, and also supplies tools to do whole-cluster systems management.

These commands enable easy installation and maintenance of a HA cluster, by providing support for package installation, configuration of the cluster messaging layer, file system setup and more.

Starts the cluster-related system services on this node.

Usage:

Stops the cluster-related system services on this node.

Usage:

Installs and configures a basic HA cluster on a set of nodes.

Usage:

This command simplifies the process of adding a new node to a running cluster. The new node will be installed and configured with the packages and configuration files needed to run the cluster resources. If a cluster file system is used, the new node will be set up to host the file system.

This command should be executed from a node already in the cluster.

Usage:

This command simplifies the process of removing a node from the cluster, moving any resources hosted by that node to other nodes.

Usage:

Reports the status for the cluster messaging layer on the local node.

Usage:

Runs a larger set of tests and queries on all nodes in the cluster to verify the general system health and detect potential problems.

Usage:

Mostly useful in scripts or automated workflows, this command will attempt to connect to the local cluster node repeatedly. The command will keep trying until the cluster node responds, or the timeout elapses. The timeout can be changed by supplying a value in seconds as an argument.

Usage:

This command takes a shell statement as argument, executes that statement on all nodes in the cluster, and reports the result.

Usage:

Example:

Cluster scripts can perform cluster-wide configuration, validation and management. See the list command for an overview of available scripts.

Lists the available cluster scripts.

Usage:

Mainly useful when creating new scripts, this command verifies that the script definition has all necessary fields and that the referenced actions exist.

Usage:

Prints a description and short summary of the cluster script, with descriptions of all parameters, both required and optional.

Usage:

List the names of all steps in the cluster script.

This command is intended for use by automated tools and the web frontend.

Usage:

Runs a cluster script. Can optionally take at least two arguments: * nodes=<nodes>: List of nodes that the script runs over * dry_run=yes|no: If set, the script will not perform any modifications.

Additional arguments may be available depending on the cluster script. Use the describe command to see what arguments are provided.

Usage:

Example:

Corosync is the underlying messaging layer for most HA clusters. This level provides commands for editing and managing the corosync configuration.

Displays the status of Corosync, including the votequorum state.

Usage:

Displays the corosync configuration on the current node.

Opens the Corosync configuration file in an editor.

Usage:

Opens the log file specified in the corosync configuration file. If no log file is configured, this command returns an error.

The pager used can be configured either using the PAGER environment variable or in crm.conf.

Usage:

Tells all instances of corosync in this cluster to reload corosync.conf.

After pushing a new configuration to all cluster nodes, call this command to make corosync use the new configuration.

Usage:

Pushes the corosync configuration file on this node to the list of nodes provided. If no target nodes are given, the configuration is pushed to all other nodes in the cluster.

It is recommended to use csync2 to distribute the cluster configuration files rather than relying on this command.

Usage:

Example:

Gets the corosync configuration from another node and copies it to this node.

Usage:

Diffs the corosync configurations on different nodes. If no nodes are given as arguments, the corosync configurations on all nodes in the cluster are compared.

diff takes an option argument --checksum, to force checksum mode.

If the number of nodes to compare are greater than two, diff automatically switches to checksum mode.

Usage:

Adds a node to the corosync configuration. This is used with the udpu type configuration in corosync.

A nodeid for the added node is generated automatically.

Note that this command assumes that only a single ring is used, and sets only the address for ring0.

Usage:

Removes a node from the corosync configuration. The argument given is the ring0_addr address set in the configuration file.

Usage:

Returns the value configured in corosync.conf, which is not necessarily the value used in the running configuration. See reload for telling corosync about configuration changes.

The argument is the complete dot-separated path to the value.

If there are multiple values configured with the same path, the command returns all values for that path. For example, to get all configured ring0_addr values, use this command:

Example:

Sets the value identified by the given path. If the value does not exist in the configuration file, it will be added. However, if the section containing the value does not exist, the command will fail.

Usage:

This level is for management of shadow CIBs. It is available both at the top level and the configure level.

All the commands are implemented using cib_shadow(8) and the CIB_shadow environment variable. The user prompt always includes the name of the currently active shadow or the live CIB.

Create a new shadow CIB. The live cluster configuration and status is copied to the shadow CIB.

If the name of the shadow is omitted, we create a temporary CIB shadow. It is useful if multiple level sessions are desired without affecting the cluster. A temporary CIB shadow is short lived and will be removed either on commit or on program exit. Note that if the temporary shadow is not committed all changes in the temporary shadow are lost.

Specify withstatus if you want to edit the status section of the shadow CIB (see the cibstatus section). Add force to force overwriting the existing shadow CIB.

To start with an empty configuration that is not copied from the live CIB, specify the empty keyword. (This also allows a shadow CIB to be created in case no cluster is running.)

Usage:

Delete an existing shadow CIB.

Usage:

Copy the current cluster configuration into the shadow CIB.

Usage:

Apply a shadow CIB to the cluster. If the shadow name is omitted then the current shadow CIB is applied.

Temporary shadow CIBs are removed automatically on commit.

Usage:

Choose a CIB source. If you want to edit the status from the shadow CIB specify withstatus (see cibstatus). Leave out the CIB name to switch to the running CIB.

Usage:

Print differences between the current cluster configuration and the active shadow CIB.

Usage:

List existing shadow CIBs.

Usage:

At times it may be useful to create a shadow file from the existing CIB. The CIB may be specified as file or as a PE input file number. The shell will look up files in the local directory first and then in the PE directory (typically /var/lib/pengine). Once the CIB file is found, it is copied to a shadow and this shadow is immediately available for use at both configure and cibstatus levels.

If the shadow name is omitted then the target shadow is named after the input CIB file.

Note that there are often more than one PE input file, so you may need to specify the full name.

Usage:

Examples:

Enter edit and manage the CIB status section level. See the CIB status management section.

This level contains commands which show various information about the installed resource agents. It is available both at the top level and at the configure level.

Print all resource agents' classes and, where appropriate, a list of available providers.

Usage:

List available resource agents for the given class. If the class is ocf, supply a provider to get agents which are available only from that provider.

Usage:

Example:

Show the meta-data of a resource agent type. This is where users can find information on how to use a resource agent. It is also possible to get information from some programs: pengine, crmd, cib, and stonithd. Just specify the program name instead of an RA.

Usage:

Example:

List providers for a resource agent type. The class parameter defaults to ocf.

Usage:

Example:

At this level resources may be managed.

All (or almost all) commands are implemented with the CRM tools such as crm_resource(8).

Print resource status. If the resource parameter is left out status of all resources is printed.

Usage:

Start a resource by setting the target-role attribute. If there are multiple meta attributes sets, the attribute is set in all of them. If the resource is a clone, all target-role attributes are removed from the children resources.

For details on group management see options manage-children.

Usage:

Stop a resource using the target-role attribute. If there are multiple meta attributes sets, the attribute is set in all of them. If the resource is a clone, all target-role attributes are removed from the children resources.

For details on group management see options manage-children.

Usage:

Restart a resource. This is essentially a shortcut for resource stop followed by a start. The shell is first going to wait for the stop to finish, that is for all resources to really stop, and only then to order the start action. Due to this command entailing a whole set of operations, informational messages are printed to let the user see some progress.

For details on group management see options manage-children.

Usage:

Example:

Promote a master-slave resource using the target-role attribute.

Usage:

Demote a master-slave resource using the target-role attribute.

Usage:

Manage a resource using the is-managed attribute. If there are multiple meta attributes sets, the attribute is set in all of them. If the resource is a clone, all is-managed attributes are removed from the children resources.

For details on group management see options manage-children.

Usage:

Unmanage a resource using the is-managed attribute. If there are multiple meta attributes sets, the attribute is set in all of them. If the resource is a clone, all is-managed attributes are removed from the children resources.

For details on group management see options manage-children.

Usage:

Migrate a resource to a different node. If node is left out, the resource is migrated by creating a constraint which prevents it from running on the current node. Additionally, you may specify a lifetime for the constraint---once it expires, the location constraint will no longer be active.

Usage:

Remove the constraint generated by the previous migrate command.

Usage:

Enables or disables the per-resource maintenance mode. When this mode is enabled, no monitor operations will be triggered for the resource.

Usage:

Example:

Show/edit/delete a parameter of a resource.

Usage:

Example:

Sensitive parameters can be kept in local files rather than CIB in order to prevent accidental data exposure. Use the secret command to manage such parameters. stash and unstash move the value from the CIB and back to the CIB respectively. The set subcommand sets the parameter to the provided value. delete removes the parameter completely. show displays the value of the parameter from the local file. Use check to verify if the local file content is valid.

Usage:

Example:

Show/edit/delete a meta attribute of a resource. Currently, all meta attributes of a resource may be managed with other commands such as resource stop.

Usage:

Example:

Show/edit/delete a utilization attribute of a resource. These attributes describe hardware requirements. By setting the placement-strategy cluster property appropriately, it is possible then to distribute resources based on resource requirements and node size. See also node utilization attributes.

Usage:

Example:

Show/edit/delete the failcount of a resource.

Usage:

Example:

Cleanup resource status. Typically done after the resource has temporarily failed. If a node is omitted, cleanup on all nodes. If there are many nodes, the command may take a while.

(Pacemaker 1.1.14) Pass force to cleanup the resource itself, otherwise the cleanup command will apply to the parent resource (if any).

Usage:

Refresh CIB from the LRM status.

Usage:

Probe for resources not started by the CRM.

Usage:

Start tracing RA for the given operation. The trace files are stored in $HA_VARLIB/trace_ra. If the operation to be traced is monitor, note that the number of trace files can grow very quickly.

If no operation name is given, crmsh will attempt to trace all operations for the RA. This includes any configured operations, start and stop as well as promote/demote for multistate resources.

To trace the probe operation which exists for all resources, either set a trace for monitor with interval 0, or use probe as the operation name.

Usage:

Example:

Stop tracing RA for the given operation. If no operation name is given, crmsh will attempt to stop tracing all operations in resource.

Usage:

Example:

Display the allocation scores for all resources.

Usage:

Node management and status commands.

Show nodes' status as XML. If the node parameter is omitted then all nodes are shown.

Usage:

Show a node definition. If the node parameter is omitted then all nodes are shown.

Usage:

Set a node to standby status. The node parameter defaults to the node where the command is run.

Additionally, you may specify a lifetime for the standby---if set to reboot, the node will be back online once it reboots. forever will keep the node in standby after reboot. The life time defaults to forever.

Usage:

Example:

Set a node to online status.

The node parameter defaults to the node where the command is run.

Usage:

Set the node status to maintenance. This is equivalent to the cluster-wide maintenance-mode property but puts just one node into the maintenance mode.

The node parameter defaults to the node where the command is run.

Usage:

Set the node’s maintenance status to off. The node should be now again fully operational and capable of running resource operations.

The node parameter defaults to the node where the command is run.

Usage:

Make CRM fence a node. This functionality depends on stonith resources capable of fencing the specified node. No such stonith resources, no fencing will happen.

Usage:

Resets and clears the state of the specified node. This node is afterwards assumed clean and offline. This command can be used to manually confirm that a node has been fenced (e.g., powered off).

Be careful! This can cause data corruption if you confirm that a node is down that is, in fact, not cleanly down - the cluster will proceed as if the fence had succeeded, possibly starting resources multiple times.

Usage:

Delete a node. This command will remove the node from the CIB and, in case the cluster stack is running, use the appropriate program (crm_node or hb_delnode) to remove the node from the membership.

If the node is still listed as active and a member of our partition we refuse to remove it. With the global force option (-F) we will try to delete the node anyway.

Usage:

Edit node attributes. This kind of attribute should refer to relatively static properties, such as memory size.

Usage:

Example:

Edit node utilization attributes. These attributes describe hardware characteristics as integer numbers such as memory size or the number of CPUs. By setting the placement-strategy cluster property appropriately, it is possible then to distribute resources based on resource requirements and node size. See also resource utilization attributes.

Usage:

Examples:

Edit node attributes which are in the CIB status section, i.e. attributes which hold properties of a more volatile nature. One typical example is attribute generated by the pingd utility.

Usage:

Example:

A cluster may consist of two or more subclusters in different and distant locations. This set of commands supports such setups.

Tickets are cluster-wide attributes. They can be managed at the site where this command is executed.

It is then possible to constrain resources depending on the ticket availability (see the rsc_ticket command for more details).

Usage:

Example:

The user may set various options for the crm shell itself.

Based on the skill-level setting, the user is allowed to use only a subset of commands. There are three levels: operator, administrator, and expert. The operator level allows only commands at the resource and node levels, but not editing or deleting resources. The administrator may do that and may also configure the cluster at the configure level and manage the shadow CIBs. The expert may do all.

Usage:

Sufficient privileges are necessary in order to manage a cluster: programs such as crm_verify or crm_resource and, ultimately, cibadmin have to be run either as root or as the CRM owner user (typically hacluster). You don’t have to worry about that if you run crm as root. A more secure way is to run the program with your usual privileges, set this option to the appropriate user (such as hacluster), and setup the sudoers file.

Usage:

Example:

The edit command invokes an editor. Use this to specify your preferred editor program. If not set, it will default to either the value of the EDITOR environment variable or to one of the standard UNIX editors (vi,emacs,nano).

Usage:

Example:

The view command displays text through a pager. Use this to specify your preferred pager program. If not set, it will default to either the value of the PAGER environment variable or to one of the standard UNIX system pagers (less,more,pg).

crm by default sorts CIB elements. If you want them appear in the order they were created, set this option to no.

Usage:

Example:

In normal operation, crm runs a command and gets back immediately to process other commands or get input from the user. With this option set to yes it will wait for the started transition to finish. In interactive mode dots are printed to indicate progress.

Usage:

Example:

crm can adorn configurations in two ways: in color (similar to for instance the ls --color command) and by showing keywords in upper case. Possible values are plain, color, and uppercase. It is possible to combine the latter two in order to get an upper case xmass tree. Just set this option to color,uppercase.

With output set to color, a comma separated list of colors from this option are used to emphasize:

crm can show colors only if there is curses support for python installed (usually provided by the python-curses package). The colors are whatever is available in your terminal. Use normal if you want to keep the default foreground color.

This user preference defaults to yellow,normal,cyan,red,green,magenta which is good for terminals with dark background. You may want to change the color scheme and save it in the preferences file for other color setups.

Example:

Semantic check of the CIB or elements modified or created may be done on every configuration change (always), when verifying (on-verify) or never. It is by default set to always. Experts may want to change the setting to on-verify.

The checks require that resource agents are present. If they are not installed at the configuration time set this preference to never.

See Configuration semantic checks for more details.

Semantic check of the CIB or elements modified or created may be done in the strict mode or in the relaxed mode. In the former certain problems are treated as configuration errors. In the relaxed mode all are treated as warnings. The default is strict.

See Configuration semantic checks for more details.

The shell (as in /bin/sh) parser strips quotes from the command line. This may sometimes make it really difficult to type values which contain white space. One typical example is the configure filter command. The crm shell will supply extra quotes around arguments which contain white space. The default is yes.

Some resource management commands, such as resource stop, when the target resource is a group, may not always produce desired result. Each element, group and the primitive members, can have a meta attribute and those attributes may end up with conflicting values. Consider the following construct:

Even though the element svc should be stopped, the group is actually running because all its members have the target-role set to Started:

Hence, if the user invokes resource stop svc the intention is not clear. This preference gives the user an opportunity to better control what happens if attributes of group members have values which are in conflict with the same attribute of the group itself.

Possible values are ask (the default), always, and never. If set to always, the crm shell removes all children attributes which have values different from the parent. If set to never, all children attributes are left intact. Finally, if set to ask, the user will be asked for each member what is to be done.

Display all current settings.

Given an option name as argument, show will display only the value of that argument.

Given all as argument, show displays all available user options.

Usage:

Example:

Sets the value of an option. Takes the fully qualified name of the option as argument, as displayed by show all.

The modified option value is stored in the user-local configuration file, usually found in ~/.config/crm/crm.conf.

Usage:

Example:

Save current settings to the rc file ($HOME/.config/crm/rc). On further crm runs, the rc file is automatically read and parsed.

This command resets all user options to the defaults. If used as a single-shot command, the rc file ($HOME/.config/crm/rc) is reset to the defaults too.

This level enables all CIB object definition commands.

The configuration may be logically divided into four parts: nodes, resources, constraints, and (cluster) properties and attributes. Each of these commands support one or more basic CIB objects.

Nodes and attributes describing nodes are managed using the node command.

Commands for resources are:

In order to streamline large configurations, it is possible to define a template which can later be referenced in primitives:

In that case the primitive inherits all attributes defined in the template.

There are three types of constraints:

It is possible to define fencing order (stonith resource priorities):

Finally, there are the cluster properties, resource meta attributes defaults, and operations defaults. All are just a set of attributes. These attributes are managed by the following commands:

In addition to the cluster configuration, the Access Control Lists (ACL) can be setup to allow access to parts of the CIB for users other than root and hacluster. The following commands manage ACL:

In Pacemaker 1.1.12 and up, this command replaces the user command for handling ACLs:

The changes are applied to the current CIB only on ending the configuration session or using the commit command.

Comments start with # in the first line. The comments are tied to the element which follows. If the element moves, its comments will follow.

The node command describes a cluster node. Nodes in the CIB are commonly created automatically by the CRM. Hence, you should not need to deal with nodes unless you also want to define node attributes. Note that it is also possible to manage node attributes at the node level.

Usage:

Example:

The primitive command describes a resource. It may be referenced only once in group, clone, or master-slave objects. If it’s not referenced, then it is placed as a single resource in the CIB.

Operations may be specified anonymously, as a group or by reference:

Operation attributes which are not recognized are saved as instance attributes of that operation. A typical example is OCF_CHECK_LEVEL.

For multistate resources, roles are specified as role=<role>.

A template may be defined for resources which are of the same type and which share most of the configuration. See rsc_template for more information.

Attributes containing time values, such as the interval attribute on operations, are configured either as a plain number, which is interpreted as a time in seconds, or using one of the following suffixes:

Usage:

Example:

Monitor is by far the most common operation. It is possible to add it without editing the whole resource. Also, long primitive definitions may be a bit uncluttered. In order to make this command as concise as possible, less common operation attributes are not available. If you need them, then use the op part of the primitive command.

Usage:

Example:

Note that after executing the command, the monitor operation may be shown as part of the primitive definition.

The group command creates a group of resources. This can be useful when resources depend on other resources and require that those resources start in order on the same node. A commmon use of resource groups is to ensure that a server and a virtual IP are located together, and that the virtual IP is started before the server.

Grouped resources are started in the order they appear in the group, and stopped in the reverse order. If a resource in the group cannot run anywhere, resources following it in the group will not start.

group can be passed the "container" meta attribute, to indicate that it is to be used to group VM resources monitored using Nagios. The resource referred to by the container attribute must be of type ocf:heartbeat:Xen, oxf:heartbeat:VirtualDomain or ocf:heartbeat:lxc.

Usage:

Example:

The clone command creates a resource clone. It may contain a single primitive resource or one group of resources.

Usage:

Example:

The ms command creates a master/slave resource type. It may contain a single primitive resource or one group of resources.

Usage:

Example:

The rsc_template command creates a resource template. It may be referenced in primitives. It is used to reduce large configurations with many similar resources.

Usage:

Example:

location defines the preference of nodes for the given resource. The location constraints consist of one or more rules which specify a score to be awarded if the rule matches.

The resource referenced by the location constraint can be one of the following:

The syntax for resource sets is described in detail for colocation.

For more details on how to configure resource sets, see Syntax: Resource sets.

Usage:

Examples:

This constraint expresses the placement relation between two or more resources. If there are more than two resources, then the constraint is called a resource set.

The score is used to indicate the priority of the constraint. A positive score indicates that the resources should run on the same node. A negative score that they should not run on the same node. Values of positive or negative infinity indicate a mandatory constraint.

In the two resource form, the cluster will place <with-rsc> first, and then decide where to put the <rsc> resource.

Collocation resource sets have an extra attribute (sequential) to allow for sets of resources which don’t depend on each other in terms of state. The shell syntax for such sets is to put resources in parentheses.

Sets cannot be nested.

The optional node-attribute references an attribute in nodes' instance attributes.

For more details on how to configure resource sets, see Syntax: Resource sets.

Usage:

Example:

This constraint expresses the order of actions on two resources or more resources. If there are more than two resources, then the constraint is called a resource set.

Ordered resource sets have an extra attribute to allow for sets of resources whose actions may run in parallel. The shell syntax for such sets is to put resources in parentheses.

If the subsequent resource can start or promote after any one of the resources in a set has done, enclose the set in brackets ([ and ]).

Sets cannot be nested.

Three strings are reserved to specify a kind of order constraint: Mandatory, Optional, and Serialize. It is preferred to use one of these settings instead of score. Previous versions mapped scores 0 and inf to keywords advisory and mandatory. That is still valid but deprecated.

For more details on how to configure resource sets, see Syntax: Resource sets.

Usage:

Example:

This constraint expresses dependency of resources on cluster-wide attributes, also known as tickets. Tickets are mainly used in geo-clusters, which consist of multiple sites. A ticket may be granted to a site, thus allowing resources to run there.

The loss-policy attribute specifies what happens to the resource (or resources) if the ticket is revoked. The default is either stop or demote depending on whether a resource is multi-state.

See also the site set of commands.

Usage:

Example:

Set the cluster (crm_config) options.

Usage:

Example:

Set defaults for the resource meta attributes.

Usage:

Example:

If multiple fencing (stonith) devices are available capable of fencing a node, their order may be specified by fencing_topology. The order is specified per node.

Stonith resources can be separated by , in which case all of them need to succeed. If they fail, the next stonith resource (or set of resources) is used. In other words, use comma to separate resources which all need to succeed and whitespace for serial order. It is not allowed to use whitespace around comma.

If the node is left out, the order is used for all nodes. That should reduce the configuration size in some stonith setups.

Usage:

Example:

An ACL role is a set of rules which describe access rights to CIB. Rules consist of an access right read, write, or deny and a specification denoting part of the configuration to which the access right applies. The specification can be an XPath or a combination of tag and id references. If an attribute is appended, then the specification applies only to that attribute of the matching element.

There is a number of shortcuts for XPath specifications. The meta, params, and utilization shortcuts reference resource meta attributes, parameters, and utilization respectively. The location may be used to specify location constraints most of the time to allow resource move and unmove commands. The property references cluster properties. The node allows reading node attributes. nodeattr and nodeutil reference node attributes and node capacity (utilization). The status shortcut references the whole status section of the CIB. Read access to status is necessary for various monitoring tools such as crm_mon(8) (aka crm status).

Usage:

Example:

Users which normally cannot view or manage cluster configuration can be allowed access to parts of the CIB. The access is defined by a set of read, write, and deny rules as in role definitions or by referencing roles. The latter is considered best practice.

Usage:

Example:

Defines an ACL target.

Usage:

Example:

Event-driven alerts enables calling scripts whenever interesting events occur in the cluster (nodes joining or leaving, resources starting or stopping, etc.).

The path is an arbitrary file path to an alert script. Existing external scripts used with ClusterMon resources can be used as alert scripts, since the interface is compatible.

Each alert may have a number of receipients configured. These will be passed to the script as arguments. The first recipient will also be passed as the CRM_alert_recipient environment variable, for compatibility with existing scripts that only support one recipient.

The available meta attributes are timeout (default 30s) and timestamp-format (default "%H:%M:%S.%06N").

Some configurations may require each recipient to be delimited by brackets, to avoid ambiguity. In the example alert-2 below, the meta attribute for timeout is defined after the recipient, so the brackets are used to ensure that the meta attribute is set for the alert and not just the recipient. This can be avoided by setting any alert attributes before defining the recipients.

Usage:

Example:

Set defaults for the operations meta attributes.

Usage:

Example:

Define a resource tag. A tag is an id referring to one or more resources, without implying any constraints between the tagged resources. This can be useful for grouping conceptually related resources.

Usage:

Example:

CIB’s content is validated by a RNG schema. Pacemaker supports several, depending on version. At least the following schemas are accepted by crmsh:

Use this command to display or switch to another RNG schema.

Usage:

Example:

The show command displays objects. It may display all objects or a set of objects. The user may also choose to see only objects which were changed.

Optionally, the XML code may be displayed instead of the CLI representation by passing xml as the first argument.

To show all objects of a certain type, use the type: prefix. To show all objects in a given tag, use the tag: prefix.

Usage:

Example:

This command invokes the editor with the object description. As with the show command, the user may choose to edit all objects or a set of objects.

If the user insists, he or she may edit the XML edition of the object. If you do that, don’t modify any id attributes.

Usage:

This command filters the given CIB elements through an external program. The program should accept input on stdin and send output to stdout (the standard UNIX filter conventions). As with the show command, the user may choose to filter all or just a subset of elements.

It is possible to filter the XML representation of objects, but probably not as useful as the configuration language. The presentation is somewhat different from what would be displayed by the show command---each element is shown on a single line, i.e. there are no backslashes and no other embelishments.

Don’t forget to put quotes around the filter if it contains spaces.

Usage:

Examples:

Delete one or more objects. If an object to be deleted belongs to a container object, such as a group, and it is the only resource in that container, then the container is deleted as well. Any related constraints are removed as well.

If the object is a started resource, it will not be deleted unless the --force flag is passed to the command, or the force option is set.

Usage:

This command takes the timeouts from the actions section of the resource agent meta-data and sets them for the operations of the primitive.

Usage:

Rename an object. It is recommended to use this command to rename a resource, because it will take care of updating all related constraints and a parent resource. Changing ids with the edit command won’t have the same effect.

If you want to rename a resource, it must be in the stopped state.

Usage:

Add or remove primitives in a group. The add subcommand appends the new group member by default. Should it go elsewhere, there are after and before clauses.

Usage:

Examples:

Refresh the internal structures from the CIB. All changes made during this session are lost.

Usage:

The erase clears all configuration. Apart from nodes. To remove nodes, you have to specify an additional keyword nodes.

Note that removing nodes from the live cluster may have some strange/interesting/unwelcome effects.

Usage:

Show PE (Policy Engine) motions using ptest(8) or crm_simulate(8).

A CIB is constructed using the current user edited configuration and the status from the running CIB. The resulting CIB is run through ptest (or crm_simulate) to show changes which would happen if the configuration is committed.

The status section may be loaded from another source and modified using the cibstatus level commands. In that case, the ptest command will issue a message informing the user that the Policy Engine graph is not calculated based on the current status section and therefore won’t show what would happen to the running but some imaginary cluster.

If you have graphviz installed and X11 session, dotty(1) is run to display the changes graphically.

Add a string of v characters to increase verbosity. ptest can also show allocation scores. utilization turns on information about the remaining capacity of nodes. With the actions option, ptest will print all resource actions.

The ptest program has been replaced by crm_simulate in newer Pacemaker versions. In some installations both could be installed. Use simulate to enfore using crm_simulate.

Usage:

Examples:

Test resources with current resource configuration. If no nodes are specified, tests are run on all known nodes.

The order of resources is significant: it is assumed that later resources depend on earlier ones.

If a resource is multi-state, it is assumed that the role on which later resources depend is master.

Tests are run sequentially to prevent running the same resource on two or more nodes. Tests are carried out only if none of the specified nodes currently run any of the specified resources. However, it won’t verify whether resources run on the other nodes.

Superuser privileges are obviously required: either run this as root or setup the sudoers file appropriately.

Note that resource testing may take some time.

Usage:

Examples:

This level is for management of shadow CIBs. It is available at the configure level to enable saving intermediate changes to a shadow CIB instead of to the live cluster. This short excerpt shows how:

Note how the current CIB in the prompt changed from live to test-2 after issuing the cib new command. See also the CIB shadow management for more information.

Enter edit and manage the CIB status section level. See the CIB status management section.

The specified template is loaded into the editor. It’s up to the user to make a good CRM configuration out of it. See also the template section.

Usage:

Example:

Commit the current configuration to the CIB in use. As noted elsewhere, commands in a configure session don’t have immediate effect on the CIB. All changes are applied at one point in time, either using commit or when the user leaves the configure level. In case the CIB in use changed in the meantime, presumably by somebody else, the crm shell will refuse to apply the changes.

If you know that it’s fine to still apply them, add force to the command line.

Usage:

Verify the contents of the CIB which would be committed.

Usage:

If you get the CIB not supported error, which typically means that the current CIB version is coming from the older release, you may try to upgrade it to the latest revision. The command to perform the upgrade is:

If we don’t recognize the current CIB as the old one, but you’re sure that it is, you may force the command.

Usage:

Save the current configuration to a file. Optionally, as XML. Use - instead of file name to write the output to stdout.

Usage:

Example:

Load a part of configuration (or all of it) from a local file or a network URL. The replace method replaces the current configuration with the one from the source. The update tries to import the contents into the current configuration. The file may be a CLI file or an XML file.

Usage:

Example:

Create a graphviz graphical layout from the current cluster configuration.

Currently, only dot (directed graph) is supported. It is essentially a visualization of resource ordering.

The graph may be saved to a file which can be used as source for various graphviz tools (by default it is displayed in the user’s X11 session). Optionally, by specifying the format, one can also produce an image instead.

For more or different graphviz attributes, it is possible to save the default set of attributes to an ini file. If this file exists it will always override the builtin settings. The exportsettings subcommand also prints the location of the ini file.

Usage:

Example:

Even though we promissed no xml, it may happen, but hopefully very very seldom, that an element from the CIB cannot be rendered in the configuration language. In that case, the element will be shown as raw xml, prefixed by this command. That element can then be edited like any other. If the shell finds out that after the change it can digest it, then it is going to be converted into the normal configuration language. Otherwise, there is no need to use xml for configuration.

Usage:

User may be assisted in the cluster configuration by templates prepared in advance. Templates consist of a typical ready configuration which may be edited to suit particular user needs.

This command enters a template level where additional commands for configuration/template management are available.

Create a new configuration from one or more templates. Note that configurations and templates are kept in different places, so it is possible to have a configuration name equal a template name.

If you already know which parameters are required, you can set them directly on the command line.

The parameter name id is set by default to the name of the configuration.

Usage:

Example:

Load an existing configuration. Further edit, show, and apply commands will refer to this configuration.

Usage:

Edit current or given configuration using your favourite editor.

Usage:

Remove a configuration. The loaded (active) configuration may be removed by force.

Usage:

List existing configurations or templates.

Usage:

Copy the current or given configuration to the current CIB. By default, the CIB is replaced, unless the method is set to "update".

Usage:

Process the current or given configuration and display the result.

Usage:

The status section of the CIB keeps the current status of nodes and resources. It is modified only on events, i.e. when some resource operation is run or node status changes. For obvious reasons, the CRM has no user interface with which it is possible to affect the status section. From the user’s point of view, the status section is essentially a read-only part of the CIB. The current status is never even written to disk, though it is available in the PE (Policy Engine) input files which represent the history of cluster motions. The current status may be read using the cibadmin -Q command.

It may sometimes be of interest to see how status changes would affect the Policy Engine. The set of ‘cibstatus` level commands allow the user to load status sections from various sources and then insert or modify resource operations or change nodes’ state.

The effect of those changes may then be observed by running the ptest command at the configure level or simulate and run commands at this level. The ptest runs with the user edited CIB whereas the latter two commands run with the CIB which was loaded along with the status section.

The simulate and run commands as well as all status modification commands are implemented using crm_simulate(8).

Load a status section from a file, a shadow CIB, or the running cluster. By default, the current (live) status section is modified. Note that if the live status section is modified it is not going to be updated if the cluster status changes, because that would overwrite the user changes. To make crm drop changes and resume use of the running cluster status, run load live.

All CIB shadow configurations contain the status section which is a snapshot of the status section taken at the time the shadow was created. Obviously, this status section doesn’t have much to do with the running cluster status, unless the shadow CIB has just been created. Therefore, the ptest command by default uses the running cluster status section.

Usage:

Example:

The current internal status section with whatever modifications were performed can be saved to a file or shadow CIB.

If the file exists and contains a complete CIB, only the status section is going to be replaced and the rest of the CIB will remain intact. Otherwise, the current user edited configuration is saved along with the status section.

Note that all modifications are saved in the source file as soon as they are run.

Usage:

Example:

Show the origin of the status section currently in use. This essentially shows the latest load argument.

Usage:

Show the current status section in the XML format. Brace yourself for some unreadable output. Add changed option to get a human readable output of all changes.

Usage:

Change the node status. It is possible to throw a node out of the cluster, make it a member, or set its state to unclean.

Usage:

Example:

Edit the outcome of a resource operation. This way you can tell CRM that it ran an operation and that the resource agent returned certain exit code. It is also possible to change the operation’s status. In case the operation status is set to something other than done, the exit code is effectively ignored.

Usage:

Example:

Set the quorum value.

Usage:

Example:

Modify the ticket status. Tickets can be granted and revoked. Granted tickets could be activated or put in standby.

Usage:

Example:

Run the policy engine with the edited status section.

Add a string of v characters to increase verbosity. Specify scores to see allocation scores also. utilization turns on information about the remaining capacity of nodes.

If you have graphviz installed and X11 session, dotty(1) is run to display the changes graphically.

Usage:

Example:

Run the policy engine with the edited status section and simulate the transition.

Add a string of v characters to increase verbosity. Specify scores to see allocation scores also. utilization turns on information about the remaining capacity of nodes.

If you have graphviz installed and X11 session, dotty(1) is run to display the changes graphically.

Usage:

Example:

The assist sublevel is a collection of helper commands that create or modify resources and constraints, to simplify the creation of certain configurations.

For more information on individual commands, see the help text for those commands.

A colocation between a group of resources says that the resources should be located together, but it also means that those resources are dependent on each other. If one of the resources fails, the others will be restarted.

If this is not desired, it is possible to circumvent: By placing the resources in a non-sequential set and colocating the set with a dummy resource which is not monitored, the resources will be placed together but will have no further dependency on each other.

This command creates both the constraint and the dummy resource needed for such a colocation.

Usage:

This command takes a list of primitives as argument, and creates a new rsc_template for these primitives. It can only do this if the primitives do not already share a template and are of the same type.

Usage:

Examining Pacemaker’s history is a particularly involved task. The number of subsystems to be considered, the complexity of the configuration, and the set of various information sources, most of which are not exactly human readable, keep analyzing resource or node problems accessible to only the most knowledgeable. Or, depending on the point of view, to the most persistent. The following set of commands has been devised in hope to make cluster history more accessible.

Of course, looking at all history could be time consuming regardless of how good tools at hand are. Therefore, one should first say which period he or she wants to analyze. If not otherwise specified, the last hour is considered. Logs and other relevant information is collected using hb_report. Since this process takes some time and we always need fresh logs, information is refreshed in a much faster way using pssh(1). If python-pssh is not found on the system, examining live cluster is still possible though not as comfortable.

Apart from examining live cluster, events may be retrieved from a report generated by hb_report (see also the -H option). In that case we assume that the period stretching the whole report needs to be investigated. Of course, it is still possible to further reduce the time range.

If you think you may have found a bug or just need clarification from developers or your support, the session pack command can help create a report.

Example:

In order to reduce report size and allow developers to concentrate on the issue, you should beforehand limit the time frame. Giving a meaningful session name helps too.

The info command provides a summary of the information source, which can be either a live cluster snapshot or a previously generated report.

Usage:

Example:

The latest command shows a bit of recent history, more precisely whatever happened since the last cluster change (the latest transition). If the transition is running, the shell will first wait until it finishes.

Usage:

Example:

All history commands look at events within certain period. It defaults to the last hour for the live cluster source. There is no limit for the hb_report source. Use this command to set the timeframe.

The time period is parsed by the dateutil python module. It covers wide range of date formats. For instance:

We won’t bother to give definition of the time specification in usage below. Either use common sense or read the dateutil documentation.

If dateutil is not available, then the time is parsed using strptime and only the kind as printed by date(1) is allowed:

Usage:

Examples:

Events to be examined can come from the current cluster or from a hb_report report. This command sets the source. source live sets source to the running cluster and system logs. If no source is specified, the current source information is printed.

In case a report source is specified as a file reference, the file is going to be unpacked in place where it resides. This directory is not removed on exit.

Usage:

Examples:

This command makes sense only for the live source and makes crm collect the latest logs and other relevant information from the logs. If you want to make a completely new report, specify force.

Usage:

How much detail to show from the logs.

Usage:

Example:

In case the host this program runs on is not part of the cluster, it is necessary to set the list of nodes.

Usage:

Example:

Show actions and any failures that happened on all specified resources on all nodes. Normally, one gives resource names as arguments, but it is also possible to use extended regular expressions. Note that neither groups nor clones or master/slave names are ever logged. The resource command is going to expand all of these appropriately, so that clone instances or resources which are part of a group are shown.

Usage:

Example:

Show important events that happened on a node. Important events are node lost and join, standby and online, and fence. Use either node names or extended regular expressions.

Usage:

Example:

Show messages logged on one or more nodes. Leaving out a node name produces combined logs of all nodes. Messages are sorted by time and, if the terminal emulations supports it, displayed in different colours depending on the node to allow for easier reading.

The sorting key is the timestamp as written by syslog which normally has the maximum resolution of one second. Obviously, messages generated by events which share the same timestamp may not be sorted in the same way as they happened. Such close events may actually happen fairly often.

Usage:

Example:

If a log is infested with irrelevant messages, those messages may be excluded by specifying a regular expression. The regular expressions used are Python extended. This command is additive. To drop all regular expressions, use exclude clear. Run exclude only to see the current list of regular expressions. Excludes are saved along with the history sessions.

Usage:

Example:

Every event in the cluster results in generating one or more Policy Engine (PE) files. These files describe future motions of resources. The files are listed as full paths in the current report directory. Add v to also see the creation time stamps.

Usage:

Example:

This command will print actions planned by the PE and run graphviz (dotty) to display a graphical representation of the transition. Of course, for the latter an X11 session is required. This command invokes ptest(8) in background.

The showdot subcommand runs graphviz (dotty) to display a graphical representation of the .dot file which has been included in the report. Essentially, it shows the calculation produced by pengine which is installed on the node where the report was produced. In optimal case this output should not differ from the one produced by the locally installed pengine.

The log subcommand shows the full log for the duration of the transition.

A transition can also be saved to a CIB shadow for further analysis or use with cib or configure commands (use the save subcommand). The shadow file name defaults to the name of the PE input file.

If the PE input file number is not provided, it defaults to the last one, i.e. the last transition. The last transition can also be referenced with number 0. If the number is negative, then the corresponding transition relative to the last one is chosen.

If there are warning and error PE input files or different nodes were the DC in the observed timeframe, it may happen that PE input file numbers collide. In that case provide some unique part of the path to the file.

After the ptest output, logs about events that happened during the transition are printed.

Usage:

Examples:

Every transition is saved as a PE file. Use this command to render that PE file either as configuration or status. The configuration output is the same as crm configure show.

Usage:

Examples:

Create a graphviz graphical layout from the PE file (the transition). Every transition contains the cluster configuration which was active at the time. See also generate a directed graph from configuration.

Usage:

Example:

A transition represents a change in cluster configuration or state. Use diff to see what has changed between two transitions.

If you want to specify the current cluster configuration and status, use the string live.

Normally, the first transition specified should be the one which is older, but we are not going to enforce that.

Note that a single configuration update may result in more than one transition.

Usage:

Examples:

A transition represents a change in cluster configuration or state. Use wdiff to see what has changed between two transitions as word differences on a line-by-line basis.

If you want to specify the current cluster configuration and status, use the string live.

Normally, the first transition specified should be the one which is older, but we are not going to enforce that.

Note that a single configuration update may result in more than one transition.

Usage:

Examples:

Sometimes you may want to get back to examining a particular history period or bug report. In order to make that easier, the current settings can be saved and later retrieved.

If the current history being examined is coming from a live cluster the logs, PE inputs, and other files are saved too, because they may disappear from nodes. For the existing reports coming from hb_report, only the directory location is saved (not to waste space).

A history session may also be packed into a tarball which can then be sent to support.

Leave out subcommand to see the current session.

Usage:

Examples:

Interface to a tool for creating a cluster report. A report is an archive containing log files, configuration files, system information and other relevant data for a given time period. This is a useful tool for collecting data to attach to bug reports, or for detecting the root cause of errors resulting in resource failover, for example.

See crmsh_hb_report(8) for more details on arguments, or call crm report -h

Usage:

Examples:

The end command ends the current level and the user moves to the parent level. This command is available everywhere.

Usage:

The help command prints help for the current level or for the specified topic (command). This command is available everywhere.

Usage:

Leave the program.

Even though all sensible configurations (and most of those that are not) are going to be supported by the crm shell, I suspect that it may still happen that certain XML constructs may confuse the tool. When that happens, please file a bug report.

The crm shell will not try to update the objects it does not understand. Of course, it is always possible to edit such objects in the XML format.

Dejan Muhamedagic, <dejan@suse.de> Kristoffer Gronlund <kgronlund@suse.com> and many OTHERS

crm_resource(8), crm_attribute(8), crm_mon(8), cib_shadow(8), ptest(8), dotty(1), crm_simulate(8), cibadmin(8)

Copyright (C) 2008-2013 Dejan Muhamedagic. Copyright (C) 2013 Kristoffer Gronlund.

Free use of this software is granted under the terms of the GNU General Public License (GPL).