openstack
/
charm-hacluster
Code Issues Proposed changes

Remove moved content from README 

The content in section 'update-ring action' has been
moved and integrated into a cloud operation in the CDG:
"Scale back an application with hacluster"

Depends-On: I98a687a9ac9a3336ece99a4ecb2a00189453869d
Change-Id: I5a19440c03f4e559ef3f22f5cb51d4ba911ad550
This commit is contained in:
Peter Matulis 2021-06-11 15:53:50 -04:00
parent 7431fd21f1
commit 155a213446
1 changed files with 0 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
README.md
View File

@ -76,28 +76,6 @@ Actions allow specific operations to be performed on a per-unit basis.
To display action descriptions run `juju actions hacluster`. If the charm is
not deployed then see file ``actions.yaml``.
### update-ring action
The `update-ring` action requires a parameter (`i-really-mean-it=true`) to make
sure tidying up the list of available corosync nodes in the ring is intended.
The operation expects:
1. `juju run-action hacluster/N pause --wait`. This will make sure no Pacemaker
resources run on the unit.
2. `juju remove-unit principal-unit/N`. Iterate through this step as many times
as units want to be removed (ie. to scale back from 6 to 3 units).
3. `juju run-action hacluster/leader update-ring i-really-mean-it=true --wait`.
This step will remove corosync nodes from the ring and update corosync.conf
to list an updated number of nodes (min_quorum is recalculated).
In case a unit goes into lost state (ie. caused by hardware failure), the
initial step (pause a unit) can be skipped. Unit removal may also be replaced
by `juju remove-machine N --force`, where N is the Juju machine ID where the
unit to be removed runs.
## Presenting status information
Here are a few examples of how to present useful information with the `status`