CORS-2728: Nutanix failure domains support#1578
CORS-2728: Nutanix failure domains support#1578openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
Conversation
|
Hello @yanhua121! Some important instructions when contributing to openshift/api: |
cd05cf7 to
7d9a7fb
Compare
|
/assign @JoelSpeed |
|
/retest-required |
JoelSpeed
left a comment
There was a problem hiding this comment.
Do we have proof of concepts for how this will work with Machines and then ControlPlaneMachineSets? I'm curious as to whether we really need/want to put this failure domain information into the infrastructure object, or just follow the patterns set out by AWS/Azure/GCP for this.
That said, vSphere has embarked on a similar route to this, so perhaps this is a good path forward.
The open questions I have currently are:
- How will this work for Machines? How will they be configured and validated
- How will this work in a cluster that is upgraded?
- How will the CPMS injection the failure domain into the providerSpec/know which machines to update?
- Are the failure domains mutable? If so, how can you tell that a machine is correctly installed within a failure domain?
7d9a7fb to
b9e531c
Compare
@JoelSpeed See the feature design doc at https://docs.google.com/document/d/1TA9vCH-3X_GttJ4fHg39sstdhBPCR7S83N1R8rzXFuk/. |
b9e531c to
eb37dd4
Compare
|
@yanhua121 If you have work in progress implementations for the CPMS and Machine related components could you please open the PRs as WIP so that we can review how this code is going to be used in the future |
eb37dd4 to
bf3fa11
Compare
@JoelSpeed Okay. Can you take another look at this PR, I made changes based on your review comments and our discussion. |
bf3fa11 to
28f4dcc
Compare
28f4dcc to
ae2f15c
Compare
ae2f15c to
c0d1f31
Compare
bce018a to
f63e425
Compare
8387d7d to
7d84778
Compare
|
/retest-required |
|
/assign @elmiko @rvanderp3 |
7d84778 to
c3972ac
Compare
c3972ac to
333996e
Compare
44627b5 to
8644753
Compare
8644753 to
18bb5b5
Compare
18bb5b5 to
7f10a1b
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed, yanhua121 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@yanhua121: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build ose-cluster-config-api-container-v4.15.0-202311210610.p0.gb867610.assembly.stream for distgit ose-cluster-config-api. |
https://issues.redhat.com/browse/OCPSTRAT-257
The proof of concept PRs using the Nutanix failure domains api:
openshift/cluster-control-plane-machine-set-operator#258
openshift/machine-api-provider-nutanix#56