SPLAT-898: day 2 configuration of multiple falure domains

[rvanderp3]

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:

• QE has approved this change.

Additional information:

[rvanderp3]

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.

[ocpdocs-previewbot]

🤖 Build preview is available at:
https://54788--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/7252

[gnufied]

cc @duanwei33

[JoelSpeed]

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

[rvanderp3]

Thanks Joel. @gnufied would you mind providing a quick summary of the 'why' and I can incorporate it in to the PR?

[gnufied]

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?).

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-merge-robot]

PR needs rebase.

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.

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.