[RFE] expose a configuration option to set pacemaker in maintenance mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack HA Cluster Charm |
Fix Released
|
Undecided
|
Felipe Reyes |
Bug Description
In a long running environment maintenance is part of its lifecycle, for example when firmware updates in switches is needed. So the ability to set pacemaker in maintenance mode at the cluster level[0] and at the unit level[1]
I think the global cluster maintenance status should be managed via a configuration option (juju config hacluster maintenance-
In both cases the unit's status message should reflect the internal state of pacemaker.
[Other Info]
* https:/
[0] crm configure property maintenance-
[1] crm node maintenance juju-xxx
Changed in charm-hacluster: | |
assignee: | nobody → Felipe Reyes (freyes) |
description: | updated |
Changed in charm-hacluster: | |
status: | In Progress → Fix Committed |
Changed in charm-hacluster: | |
milestone: | none → 17.08 |
Changed in charm-hacluster: | |
status: | Fix Committed → Fix Released |
Why is the global maintenance mode (cluster level) managed through a config option while the node level through an action?
- Application level manipulation feels more appropriate in a config flag that will be able to express the current state of the application, but actions are executed against a unit.
I believe there is not "wrong" approach on this, this is more a thing of design decision.