This parameter is not used by the installer and completely ignored
during the installation, so it just confuses users and should be removed.
The real region value is taken from clouds.yaml file.
Make it clear that the `computeFlavor` property sets the flavor for
both compute and control-plane nodes, unless overridden via the
machine-pool `type` property.
This is a bit more accessible than pointing folks at Godocs, since it
allows us to focus on the YAML property names (while Godocs
understandably focus on Go property names) and YAML renderings. Also
break up our old "one big example" install-config.yaml into a minimal
per-platform example and a series of small extentions excercising
groups of properties.
The vSphere docs are based heavily on [1].
Also drop proxy.md. It was added in e7edbf71fd (Add proxy
configuration to bootstrap node, 2019-06-24, #1832), but:
* Proxy testing and Squid configuration information belongs in
openshift/release, not in the installer repository.
* docs/user/customization.md now contains a more complete proxy-config
fragment.
OpenStack computeFlavor precedence is based on [2].
[1]: https://github.com/openshift/openshift-docs/blob/enterprise-4.2/modules/installation-vsphere-config-yaml.adoc
Last touched by commit openshift/openshift-docs@25afc7626d , 2019-08-19
[2]: https://github.com/openshift/installer/pull/2162#discussion_r322410878
Refresh the user documentation with the current state of deployment on
OpenStack.
Co-Authored-By: Emilio Garcia <egarcia@redhat.com>
Co-Authored-By: Ramon Acedo Rodriguez <racedoro@redhat.com>
Co-Authored-By: Martin André <m.andre@redhat.com>
