Review hacluster subordinates for cluster quorum
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack HA Cluster Charm |
In Progress
|
Undecided
|
Unassigned | ||
juju-verify |
Won't Fix
|
Low
|
Xav Paice |
Bug Description
When a requested unit is an application with an hacluster subordinate, we need to ensure that there are enough remaining units of the same hacluster application such that removing the requested principal does not cause the pacemaker cluster to lose quorum and therefore stop the managed services and VIPs.
Requirements:
* specify a principal unit, e.g. mysql/4 or nova-cloud-
* if hacluster is found, ensure there are enough online units that removing the principal does not lose quorum
* If the principal is a known application not needing other checks, add to the supported list
* support listing more than one unit from the same application
* support listing more than one application (e.g. if we wish to shut down a machine hosting multiple units)
* Initial support for the following charms:
* openstack-dashboard
* Openstack APIs: all that do not store data, and are fully HA with the aid of hacluster
Output:
* Issue a warning if the principal application is not one supported, but don't fail for that reason
* Fail if any hacluster application would lose quorum as a result of the requested reboot/shutdown
* if a requested unit holds the VIP, issue a warning.
Actions required on hacluster charm:
* status (existing, has the information required)
Specific exclusions:
* Postgresql will not be in the list of supported charms since it is only used on the Maas hosts, which have many other reasons to manually check before rebooting
* percona-cluster (because it stores data and we need to additionally check the replication status). TODO write a separate bug for percona-cluster.
Changed in charm-hacluster: | |
status: | New → In Progress |
Changed in juju-verify: | |
assignee: | nobody → Xav Paice (xavpaice) |
status: | New → In Progress |
Changed in juju-verify: | |
status: | In Progress → Triaged |
importance: | Undecided → Low |
added charm-hacluster because though the status action provides the cluster status, we need to know the hostname of the unit it just ran on. That information isn't provided by Juju, and for some providers (e.g. the openstack provider) we have no link between the machine hostname and the unit/machine/ installation- id. The dns-name shows just an IP address.
Request for the charm therefore: add a 'hostname' field to the action output.