Merge pull request #96881 from dfitzmau/OSDOCS-14020-14

[enterprise-4.14] OSDOCS-14020-14: Updated IPI/UPI vSphere vCenter data center explanations

Author: lahinson

modules/installation-vsphere-installer-infra-requirements.adoc

@@ -3,6 +3,10 @@
 // * installing/installing_vsphere/ipi/ipi-vsphere-installation-reqs.adoc
 // * installing_vsphere/upi/upi-vsphere-installation-reqs.adoc
 
+// Note: The ifndef statements add content to IPI documents
+ifeval::["{context}" == "ipi-vsphere-installation-reqs"]
+:ipi:
+endif::[]
 ifeval::["{context}" == "upi-vsphere-installation-reqs"]
 :upi:
 endif::[]
@@ -127,8 +131,13 @@ endif::upi[]
 `VirtualMachine.Provisioning.MarkAsTemplate`
 `VirtualMachine.Provisioning.DeployTemplate`
 
-|vSphere vCenter Datacenter
-|If the installation program creates the virtual machine folder. For UPI, `VirtualMachine.Inventory.Create` and `VirtualMachine.Inventory.Delete` privileges are optional if your cluster does not use the Machine API.
+|vSphere vCenter data center
+ifdef::ipi[]
+|The installation program creates the virtual machine folder.
+endif::ipi[]
+ifdef::upi[]
+|`VirtualMachine.Inventory.Create` and `VirtualMachine.Inventory.Delete` privileges are optional if your cluster does not use the Machine API. See the "Minimum permissions for the Machine API" table.
+endif::upi[]
 |
 [%hardbreaks]
 `InventoryService.Tagging.ObjectAttachable`
@@ -257,8 +266,13 @@ endif::upi[]
 `"Virtual machine".Provisioning."Mark as template"`
 `"Virtual machine".Provisioning."Deploy template"`
 
-|vSphere vCenter Datacenter
-|If the installation program creates the virtual machine folder. For UPI, `VirtualMachine.Inventory.Create` and `VirtualMachine.Inventory.Delete` privileges are optional if your cluster does not use the Machine API.
+|vSphere vCenter data center
+ifdef::ipi[]
+|The installation program creates the virtual machine folder.
+endif::ipi[]
+ifdef::upi[]
+|`VirtualMachine.Inventory.Create` and `VirtualMachine.Inventory.Delete` privileges are optional if your cluster does not use the Machine API.
+endif::upi[]
 |
 [%hardbreaks]
 `"vSphere Tagging"."Assign or Unassign vSphere Tag on Object"`
@@ -313,14 +327,16 @@ Additionally, the user requires some `ReadOnly` permissions, and some of the rol
 |False
 |Listed required privileges
 
-.2+|vSphere vCenter Datacenter
+ifdef::ipi[]
+.2+|vSphere vCenter data center
 |Existing folder
 |False
 |`ReadOnly` permission
 
 |Installation program creates the folder
 |True
 |Listed required privileges
+endif::ipi[]
 
 .2+|vSphere vCenter Cluster
 |Existing resource pool
@@ -481,6 +497,9 @@ default. This record must be resolvable by both clients external to the cluster
 and from all the nodes within the cluster.
 |===
 
+ifeval::["{context}" == "ipi-vsphere-installation-reqs"]
+:!ipi:
+endif::[]
 ifeval::["{context}" == "upi-vsphere-installation-reqs"]
 :!upi:
 endif::[]

modules/machineset-vsphere-required-permissions.adoc

@@ -67,8 +67,8 @@ If you cannot use an account with global administrative privileges, you must cre
 `VirtualMachine.Inventory.Delete`
 `VirtualMachine.Provisioning.Clone`
 
-|vSphere vCenter Datacenter
-|If the installation program creates the virtual machine folder
+|vSphere vCenter data center
+|If the installation program creates the virtual machine folder.
 |
 [%hardbreaks]
 `Resource.AssignVMToPool`