Hacluster
- By OpenStack Charmers
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/edge | 145 | 21 Aug 2024 | |
latest/edge | 144 | 21 Aug 2024 | |
latest/edge | 143 | 21 Aug 2024 | |
latest/edge | 141 | 21 Jun 2024 | |
latest/edge | 133 | 15 May 2024 | |
latest/edge | 118 | 01 Mar 2023 | |
latest/edge | 29 | 11 Nov 2020 | |
latest/edge | 16 | 11 Nov 2020 | |
latest/edge | 0 | 11 Nov 2020 | |
2.4/stable | 131 | 08 Dec 2023 | |
2.4/edge | 142 | 21 Jun 2024 | |
2.4/edge | 141 | 21 Jun 2024 | |
2.4/edge | 140 | 21 Jun 2024 | |
2.4/edge | 139 | 21 Jun 2024 | |
2.0.3/stable | 132 | 07 Mar 2024 | |
1.1.18/edge | 83 | 04 Mar 2022 | |
1.1.18/edge | 92 | 25 Feb 2022 | |
1.1.18/edge | 90 | 25 Feb 2022 |
juju deploy hacluster --channel 2.4/stable
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
cleanup
Trigger cluster resource cleanup
- Params
-
resource string
Resource name to cleanup
-
delete-node-from-ring
Delete a node from the corosync ring. Must be run on the hacluster leader node.
- Params
-
node string
Node name to be removed. i.e. hostname of the node
- Required
node
-
pause
Put hacluster unit in crm standby mode which migrates resources from this unit to another unit in the hacluster
-
resume
-
status
Show cluster status
- Params
-
history boolean
Show cluster status history
-
resources boolean
Show cluster resources
-
update-ring
Trigger corosync node members cleanup.
WARNING This action updates the corosync cluster members by adding or removing nodes, which may lead to a loss of quorum and other unexpected side-effects. It is strongly encouraged to manually remove nodes individually using the delete-node-from-ring action.
- Params
-
i-really-mean-it boolean
This must be toggled to enable actually performing this action.
- Required
i-really-mean-it