pcs rebase bz for 9.3
Preliminary changelog: ### Added - Support for output formats `json` and `cmd` to constraints config commands ([rhbz#2179388], [rhbz#1423473], [rhbz#2163953]) - Automatic restarts of the Puma web server in the legacy Ruby daemon to reduce its memory footprint ([rhbz#1860626]) - New URL for listing pcsd capabilities: `/capabilities` - It is now possible to list pcsd capabilities even if pcsd is not running: `pcsd --version --full` - Add lib commands `cluster_property.get_properties` and `cluster_property.get_properties_metadata` to API v2 - Add `pcs property defaults` and `pcs property describe` CLI commands - Support for output formats `json` and `cmd` to property config command ([rhbz#2163914]) - Commands `pcs resource describe` and `pcs stonith describe` print detailed info about resource options (data type or allowed values, default value) ### Fixed - Crash in commands that ask for user input (like `pcs cluster destroy`) when stdin is closed ([ghissue#612]) - Fix displaying differences between configuration checkpoints in `pcs config checkpoint diff` command ([rhbz#2175881]) - Fix `pcs stonith update-scsi-devices` command which was broken since Pacemaker-2.1.5-rc1 ([rhbz#2177996]) ### Changed - Commands for displaying cluster configuration have been slightly updated: - Headings of empty sections are no longer displayed - Resource listing is more dense as operations options are shown in a single line - Specifying `--full` to show IDs of elements now shows IDs of nvpairs as well ### Deprecated - Keyword `meta` in `pcs resource clone` and `pcs resource promotable` commands (it wasn't doing anything anyway) ([rhbz#2168155], [ghpull#648])
Changes in 0.11.6: ### Added - Support for output formats `json` and `cmd` to constraints config commands ([rhbz#2179388], [rhbz#1423473], [rhbz#2163953]) - Automatic restarts of the Puma web server in the legacy Ruby daemon to reduce its memory footprint ([rhbz#1860626]) - New URL for listing pcsd capabilities: `/capabilities` - It is now possible to list pcsd capabilities even if pcsd is not running: `pcsd --version --full` - Add lib commands `cluster_property.get_properties` and `cluster_property.get_properties_metadata` to API v2 - Add `pcs property defaults` and `pcs property describe` CLI commands - Support for output formats `json` and `cmd` to property config command ([rhbz#2163914]) - Commands `pcs resource describe` and `pcs stonith describe` print detailed info about resource options (data type or allowed values, default value) - Add warning to `pcs resource utilization` and `pcs node utilization` for the case configuration is not in effect (cluster property `placement-strategy` is not set appropriately) ([rhbz#1465829]) - New format of `pcs resource create` command which requires `meta` keyword for specifying clone and promotable meta attributes is available to be enabled by specifying --future ([rhbz#2168155]) ### Fixed - Crash in commands that ask for user input (like `pcs cluster destroy`) when stdin is closed ([ghissue#612]) - Fix displaying differences between configuration checkpoints in `pcs config checkpoint diff` command ([rhbz#2175881]) - Fix `pcs stonith update-scsi-devices` command which was broken since Pacemaker-2.1.5-rc1 ([rhbz#2177996]) - Make `pcs resource disable --simulate --brief` documentation clearer ([rhbz#2109852]) - Fixed a regression causing crash in `pcs resource move` command (broken since pcs-0.11.5) ([rhbz#2210855]) - Using `--force` in `pcs resource meta` command had no effect on a specific error message even if the message suggested otherwise. ### Changed - Commands for displaying cluster configuration have been slightly updated: - Headings of empty sections are no longer displayed - Resource listing is more dense as operations options are shown in a single line - Specifying `--full` to show IDs of elements now shows IDs of nvpairs as well ### Deprecated - Specifying clone and promotable meta attributes without the `meta` keyword is now deprecated, i.e. `pcs resource clone myResource name=value` is deprecated by `pcs resource clone myResource meta name=value` ([rhbz#2168155], [ghpull#648])