13. Quick Comparison of pcs and crm shell¶
pcs and crm shell are two popular higher-level command-line interfaces
to Pacemaker. Each has its own syntax; this chapter gives a quick comparion of
how to accomplish the same tasks using either one. Some examples also show the
equivalent command using low-level Pacemaker command-line tools.
These examples show the simplest syntax; see the respective man pages for all possible options.
13.1. Show Cluster Configuration and Status¶
13.2. Manage Nodes¶
13.3. Manage Cluster Properties¶
13.4. Show Resource Agent Information¶
You can also use the full class:provider:type format with crmsh and pcs if
multiple RAs with the same name are available.
13.5. Manage Resources¶
Both crmsh and pcs determine the standard and provider (ocf:heartbeat) automatically
since IPaddr2 is unique, and automatically create operations (including
monitor) based on the agent’s meta-data.
crmsh also has an edit command which edits the simplified CIB syntax (same commands as the command line) via a configurable text editor.
Using the interactive shell mode of crmsh, multiple changes can be edited and verified before committing to the live configuration:
crmsh supports both ways (‘configure ms’ is deprecated) to configure promotable clone since crmsh 4.4.0. pcs will generate the clone name automatically if it is omitted from the command line.
13.6. Manage Constraints¶
13.7. Advanced Configuration¶
13.7.1. Manipulate Configuration Elements by Type¶
crmsh’s show and edit commands can be used to manage resources and constraints by type: