Description
Summary
Aligning community.general.pacemaker_cluster with the module utils for pacemaker will be helpful in maintaining the module. Unit tests should be added for the module, with the addition of supporting maintenance mode which can be beneficial for users that need to manage the cluster without enforcing pacemaker lifecycle.
In summary, the following action items associated with this issue:
- Enhance
pacemaker_clusterto utilizemodule_utils/pacemaker - Add feature for
pacemaker_clusterwhich enables the module to managemaintenance modefor the cluster - Add unit tests for
pacemaker_cluster - Potentially add in support for integration testing (This may or may not be possible? See below.)
Integration testing:
I initially wanted to add this for pacemaker_resource but was running into issues with setting the cluster up. I'm currently using pcs in a Vagrant test environment (with a docker image supporting pcs) so I believe there might be potential in enabling integration testing here. Furthermore, pacemaker_cluster can be useful for other pacemaker modules if integration testing is feasible.
Issue Type
Feature Idea
Component Name
pacemaker_cluster
Additional Information
The addition of a new state: maintenance:
- name: Enable maintenance mode
community.general.pacemaker_cluster:
state: maintenance
- name: Bring the cluster online and disable maintenance mode
community.general.pacemaker_cluster:
state: onlineThe idea is that maintenance mode can stop pacemaker lifecycle management. Additionally, bringing the cluster online implies that pacemaker can resume lifecycle management.
Code of Conduct
- I agree to follow the Ansible Code of Conduct