Merge pull request #86089 from alishaIBM/ipi_new_datacenters

OCP 4.18 IPI deployment on 4 new data centers of PowerVS

Author: xenolinux

modules/installation-configuration-parameters.adoc

@@ -743,44 +743,50 @@ ifdef::ibm-power-vs[]
 |platform:
   powervs:
     serviceInstanceGUID:
-|The ServiceInstanceGUID is the ID of the Power IAAS instance created from the {ibm-cloud-name} Catalog.
+|Specifies the ID of the Power IAAS instance created from the {ibm-cloud-name} Catalog.
 |String. For example, `existing_service_instance_GUID`.
 
 |platform:
   powervs:
     clusterOSImage:
-|The ClusterOSImage is a pre-created {ibm-power-server-name} boot image that overrides the default image for cluster nodes.
+|Specifies a pre-created {ibm-power-server-name} boot image that overrides the default image for cluster nodes.
 |String. For example, `existing_cluster_os_image`.
 
 |platform:
   powervs:
     defaultMachinePlatform:
-|The DefaultMachinePlatform is the default configuration used when installing on {ibm-power-server-name} for machine pools that do not define their own platform configuration.
+|Specifies the default configuration used when installing on {ibm-power-server-name} for machine pools that do not define their own platform configuration.
 |String. For example, `existing_machine_platform`.
 
 |platform:
   powervs:
     memoryGiB:
-|The size of a virtual machine's memory, in GB.
+|Specifies the size of a virtual machine's memory, in GB.
 |The valid integer must be an integer number of GB that is at least 2 and no more than 64, depending on the machine type.
 
 |platform:
   powervs:
     procType:
-|The ProcType defines the processor sharing model for the instance.
+|Defines the processor sharing model for the instance.
 |The valid values are Capped, Dedicated, and Shared.
 
 |platform:
   powervs:
     processors:
-|The Processors defines the processing units for the instance.
+|Defines the processing units for the instance.
 |The number of processors must be from .5 to 32 cores. The processors must be in increments of .25.
 
 |platform:
   powervs:
     sysType:
-|The SysType defines the system type for the instance.
-|The system type must be either `e980` or `s922`.
+|Defines the system type for the instance.
+|The system type must be `e980`, `s922`, `e1080`, or `s1022`. The available system types depend on the zone you want to target.
+
+|platform:
+  powervs:
+    tgName:
+|Defines the name of an existing Transit Gateway.
+|String. For example, `existing_tgName`.
 endif::ibm-power-vs[]
 |====
 

modules/installation-ibm-cloud-regions.adoc

@@ -43,6 +43,8 @@ Deploying your cluster in the `eu-es` (Madrid, Spain) region is not supported fo
 endif::ibm-vpc[]
 ifdef::ibm-power-vs[]
 
+* `tor` (Toronto, Canada)
+** `tor01`
 * `dal` (Dallas, USA)
 ** `dal10`
 ** `dal12`
@@ -61,9 +63,14 @@ ifdef::ibm-power-vs[]
 ** `sao04`
 * `syd` (Sydney, Australia)
 ** `syd04`
+** `syd05`
 * `wdc` (Washington DC, USA)
 ** `wdc06`
 ** `wdc07`
+* `us-east` (Washington DC, United States)
+** `us-east`
+* `us-south` (Dallas, United States)
+** `us-south`
 
 You might optionally specify the {ibm-cloud-name} region in which the installation program creates any VPC components.
 
@@ -74,6 +81,7 @@ If you do not specify the region, the installation program selects the region cl
 
 {ibm-cloud-name} supports the following regions:
 
+* `us-east`
 * `us-south`
 * `eu-de`
 * `eu-es`