SPLAT-898: day 2 configuration of multiple falure domains#54788
SPLAT-898: day 2 configuration of multiple falure domains#54788rvanderp3 wants to merge 1 commit into
Conversation
openshift-ci
Bot
added
the
size/L
|
cc: @JoelSpeed @gnufied @jcpowermac This is a procedure that attempts to document the migration of a non-failure domain aware cluster to one that is aware. Any feedback you might have would be greatly appreciated. |
|
🤖 Build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/7252 |
|
cc @duanwei33 |
|
|
||
| [IMPORTANT] | ||
| ==== | ||
| Once a failure domain has been created it must not be deleted or modified. However, new failure domains can be appended to the list of failure domains. |
There was a problem hiding this comment.
Do we plan to enumerate the things you must do before doing this? Would it help the end user to understand if we had a list of, here's what would break/here's what you'd need to do if you really wanted to remove one?
Statements like this always seem weird to me when they don't have justifications for why
There was a problem hiding this comment.
Thanks Joel. @gnufied would you mind providing a quick summary of the 'why' and I can incorporate it in to the PR?
There was a problem hiding this comment.
Sure, but some follow up questions. Is this storage only item? Say for example - if adding a failure-domain results in creation of VMs in that failure-domain , will removal of failure-domain result in deletion of VMs in that failure-domain? (i.e will get implemented?).
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
Bot
added
the
lifecycle/stale
openshift-merge-robot
added
the
needs-rebase
|
PR needs rebase. 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. |
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci
Bot
added
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. DetailsIn response to this:
Instructions 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. |
6 participants
Version(s):
4.13
Issue:
https://issues.redhat.com/browse/SPLAT-898
Link to docs preview: https://54788--docspreview.netlify.app/openshift-enterprise/latest/post_installation_configuration/vsphere-failure-domain-configuration.html
QE review:
Additional information: