Cluster/Pair Scheduling

Cluster/Pair Scheduling

Change jobs scheduled to redundant services (active/passive or active/active) should be scheduled in such a way to preserve availability.

Ideally end users should be able to denote that these services should follow a round-robin schedule (1 node at a time) with a post-maintenance validation step (e.g. OM availability/performance metrics normal) before service begins on the next node.

Inherent modeling and handling of clusters would also vastly simplify the interaction with users for emergency change actions (e.g. critical vulnerability fixes) which currently require manual verification and scheduling of the next node for service.

Tags (2)
1 Comment
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.