PACEMAKER(8)

πŸ‘‘ PACEMAKER β€” the pacemaker(8) page, but make it make sense πŸ’…

okay so real talk: this is the Pacemaker manual page β€” part of the Pacemaker cluster resource manager β€” and it's literally just about crm_attribute. Like, that's the whole vibe here: query and update Pacemaker cluster options and node attributes. no cap, that's it. ✨


🌸 SYNOPSIS 🌸

crm_attribute -n <attribute> <command> [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

crm_attribute β€” bestie, this is your girl for querying and updating Pacemaker cluster options and node attributes. that's the whole job description and she does it gorgeously. 🫢


✨ OPTIONS ✨

πŸŽ€ Help Options:

  • -h, --help β€” show the help options, babes
  • --help-all β€” show all the help options, the whole buffet
  • --help-output β€” show output help
  • --help-selections β€” show the selecting options
  • --help-command β€” show the command options
  • --help-additional β€” show the additional options

πŸ’– Output Options:

  • --output-as=FORMAT β€” pick your output format, one of: text (that's the default, mwah) or xml
  • --output-to=DEST β€” say where the output goes, a file name (or "-" for stdout, iconic)

🧚 Selecting attributes:

  • -a, --all β€” with -L/--list-options, this includes advanced and deprecated options in the output. and lowkey, this is always treated as true when --output-as=xml is specified β€” no take-backs
  • -i, --id=XML_ID β€” (Advanced, ooh) operate on the instance of the specified attribute with this XML ID
  • -n, --name=NAME β€” operate on the attribute or option with this name. for queries this is optional, and if you skip it, all the matching attributes get returned to you. generous queen
  • -P, --pattern=PATTERN β€” operate on all attributes matching this pattern (with -v, -D, or -G)
  • -p, --promotion=RESOURCE β€” operate on the node attribute used as the promotion score for the specified resource, or for the resource given in the OCF_RESOURCE_INSTANCE environment variable if none is specified; this also defaults -l/--lifetime to reboot (normally invoked from an OCF resource agent, iykyk)
  • -s, --set-name=NAME β€” (Advanced) operate on the instance of the specified attribute that lives within the set with this XML ID

πŸ”₯ Commands:

  • -L, --list-options=TYPE β€” list all the available options of the given type. allowed values: cluster
  • -D, --delete β€” delete the attribute/option (with -n or -P). bye bestie πŸ‘‹
  • -G, --query β€” query the current value of the attribute/option. see also: -n, -P
  • -v, --update=VALUE β€” update the value of the attribute/option (with -n or -P)

πŸ’œ Additional options:

  • -d, --default=VALUE β€” (Advanced) the default value to display if none is found in configuration
  • -l, --lifetime=LIFETIME β€” lifetime of the node attribute. valid values: reboot, forever
  • -N, --node=NODE β€” set a node attribute for the named node (instead of a cluster option). see also: -l
  • -t, --type=SECTION β€” which part of the configuration to update/delete/query the option in. valid values: crm_config, rsc_defaults, op_defaults, tickets
  • --score β€” treat new attribute values as atomic score updates where possible (with --update/-v, when running against a CIB file or updating an attribute outside the status section; enabled by default if --promotion/-p is specified). details below, because there are layers πŸ§…
⚠️ okay so listen: this currently happens by default and cannot be disabled, but this default behavior is deprecated and will be removed in a future release (exception: this will remain the default with --promotion/-p). set this flag if this behavior is what you want.

This option takes effect when updating XML attributes. for an attribute named "name", if the new value is "name++" or "name+=X" for some score X, the new value is set as follows:

  • if attribute "name" is not already set to some value in the element being updated, the new value is set as a literal string.
  • if the new value is "name++", then the attribute is set to its existing value (parsed as a score) plus 1.
  • if the new value is "name+=X" for some score X, then the attribute is set to its existing value plus X, where the existing value and X are parsed and added as scores.

Scores are integer values capped at INFINITY and -INFINITY. refer to Pacemaker Explained for more details on scores, including how they're parsed and added. πŸ“š

  • -W, --wait=UNTIL β€” wait for some event to occur before returning. the values are 'no' (wait only for the attribute daemon to acknowledge the request), 'local' (wait until the change has propagated to where a local query will return the request value, or the value set by a later request), or 'cluster' (wait until the change has propagated to where a query anywhere on the cluster will return the requested value, or the value set by a later request). default is 'no'. (with -N, and one of -D or -u) ⏳
  • -z, --utilization β€” set an utilization attribute for the node

🌈 Application Options:

  • -$, --version β€” display the software version and exit
  • -V, --verbose β€” increase debug output (may be specified multiple times β€” go off, stack it)
  • -q, --quiet β€” print only the value on stdout, minimal, clean, immaculate πŸ’…

πŸ’€ EXAMPLES πŸ’€

Add a new node attribute called 'location' with the value of 'office' for host 'myhost':

crm_attribute --node myhost --name location --update office

Query the value of the 'location' node attribute for host 'myhost':

crm_attribute --node myhost --name location --query

Change the value of the 'location' node attribute for host 'myhost':

crm_attribute --node myhost --name location --update backoffice

Delete the 'location' node attribute for host 'myhost':

crm_attribute --node myhost --name location --delete

Query the value of the 'cluster-delay' cluster option:

crm_attribute --type crm_config --name cluster-delay --query

Query the value of the 'cluster-delay' cluster option and print only the value:

crm_attribute --type crm_config --name cluster-delay --query
--quiet

🫢 AUTHOR 🫢

Written by Andrew Beekhof and the Pacemaker project contributors. legends, fr fr. πŸ‘‘


and that's the page, bestie!! πŸ¦‹ this lil' beauty is from Pacemaker 3.0.3+20260728.7052..., dated September 2026 β€” the PACEMAKER(8) system administration utilities manual, serving cluster realness since forever. mwah, go update some attributes πŸ’–πŸŽ€βœ¨

πŸ“¦ where this page comes from