-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Future Sustainability
-
False
-
-
False
-
None
-
3
-
None
-
None
-
None
{}USER STORY:{}
As an OpenShift engineer, I want CI jobs to run even if specific vSphere Capacity Manager pools are unavailable, so that job runs are more resilient to infrastructure changes.
{}DESCRIPTION:{}
Modify job scheduling to remove dependency on specific vSphere Capacity Manager pools, allowing pools to be taken out of the scheduler without causing catastrophic failure.
{}Required:{}
{}Nice to have:{}
{}ACCEPTANCE CRITERIA:{}
- CI jobs can be scheduled and run successfully even if specific vSphere Capacity Manager pools are unavailable.
- Job scheduling logic is updated to distribute jobs across available pools.
- System can gracefully handle the removal of a vSphere Capacity Manager pool from the scheduler.
- Documentation is updated to reflect the changes in job scheduling.
{}ENGINEERING DETAILS:{}
<!--
Any additional information that might be useful for engineers: related
repositories or pull requests, related email threads, GitHub issues or
other online discussions, how to set up any required accounts and/or
environments if applicable, and so on.
-->