-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
[spike] Support Dedicated Hosts on Azure
-
BU Product Work
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-1730 - Support Dedicated Hosts on Azure
-
-
100% To Do, 0% In Progress, 0% Done
Epic Goal
- Research what is required to support deploying OpenShift nodes (control and compute) on existing/pre-allocated Azure Dedicated Hosts[1]
- What is the existing limitation?
- Does CAPA provides support setting parameters do specify the dedicated node?
- Does MAPI support Dedicated nodes?
- What is the fields on installer that is required when deploying in this method?
- Is there any other limitation?
Non-goal:
- openshift-install create the Dedicated Node
[1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/launching-dedicated-hosts-instances.html
Why is this important?
Scenarios
Acceptance Criteria
- Spike/Research document created mapping the existing support in components used by machine management (installer, CAPA, MAPI controllers, etc) to feed OCPSTRAT-1730
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
