Skip to content

Commit 1ff2fec

Browse files
authored
Merge pull request #97816 from dfitzmau/OCPBUGS-60660
OCPBUGS-60660: Updated vSphere disconnected doc to swap clusterOSImag…
2 parents f04d6aa + 5b235c3 commit 1ff2fec

File tree

2 files changed

+31
-4
lines changed

2 files changed

+31
-4
lines changed

modules/installation-initializing.adoc

Lines changed: 23 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -417,14 +417,36 @@ platform:
417417
----
418418
endif::osp+restricted[]
419419
ifdef::vsphere+restricted[]
420-
. In the `install-config.yaml` file, set the value of `platform.vsphere.clusterOSImage` to the image location or name. For example:
420+
. Choose one of the following methods to speficy an {op-system} image for your cluster than runs in a {vmw-full} vCenter environment.
421+
+
422+
.. The `clusterOSImage` parameter method: In the `install-config.yaml` file, set the value of `platform.vsphere.clusterOSImage` to the image location or name. For example:
421423
+
422424
[source,yaml]
423425
----
424426
platform:
425427
vsphere:
426428
clusterOSImage: http://mirror.example.com/images/rhcos-43.81.201912131630.0-vmware.x86_64.ova?sha256=ffebbd68e8a1f2a245ca19522c16c86f67f9ac8e4e0c1f0a812b068b16f7265d
427429
----
430+
+
431+
.. The `topology.template` parameter method:
432+
+
433+
... Download the *{op-system-first} - vSphere* image in Open Virtual Appliance (OVA) format to your local system. For more information, see "Creating the RHCOS image for restricted network installations".
434+
+
435+
... From the *Hosts and Clusters* tab on the {vmw-short} Client, right-click your cluster name and select *Deploy OVF Template*.
436+
+
437+
... On the *Select an OVF* tab, specify the name of the {op-system} OVA file that you downloaded.
438+
+
439+
... On the *Select a name and folder* tab, set a *Virtual machine name* for your template, such as `Template-{op-system}`.
440+
+
441+
... Click the name of your vSphere cluster and select the folder you created in the previous step.
442+
+
443+
... On the *Select a compute resource* tab, click the name of your vSphere cluster.
444+
+
445+
... On the *Select storage* tab, configure the storage options for your VM.
446+
+
447+
... When creating the OVF template, do not specify values on the *Customize template* tab or configure the template any further.
448+
+
449+
... In the `install-config.yaml` file, set the value of `topology.template` to the path where you imported the image to your {vmw-short} vCenter instance.
428450
endif::vsphere+restricted[]
429451
ifdef::nutanix+restricted[]
430452
. In the `install-config.yaml` file, set the value of `platform.nutanix.clusterOSImage` to the image location or name. For example:

modules/installation-installer-provisioned-vsphere-config-yaml.adoc

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,14 @@ endif::[]
1414
[id="installation-installer-provisioned-vsphere-config-yaml_{context}"]
1515
= Sample install-config.yaml file for an installer-provisioned VMware vSphere cluster
1616

17-
You can customize the `install-config.yaml` file to specify more details about
18-
your {product-title} cluster's platform or modify the values of the required
19-
parameters.
17+
You can customize the `install-config.yaml` file to specify more details about your {product-title} cluster's platform or change the values of the required parameters.
18+
19+
ifdef::restricted[]
20+
[NOTE]
21+
====
22+
The sample `install-config.yaml` file shows the `clusterOSImage` parameter to specify the URL for the {op-system-first} image. As an alternative to this configuration, you can use the `topology.template` parameter to point to the path in your vCenter environment that includes an {op-system} image in Open Virtual Appliance (OVA) format.
23+
====
24+
endif::restricted[]
2025

2126
[source,yaml]
2227
----

0 commit comments

Comments
 (0)