feat: switch tor01 and us-south DC to PER DC (#657)

Author: surajsbharadwaj

ibm_catalog.json

@@ -83,7 +83,7 @@
                             "required": true,
                             "options": [
                                 {
-                                    "displayname": "Dallas (dallas)",
+                                    "displayname": "Dallas (dallas) PER",
                                     "value": "us-south"
                                 },
                                 {
@@ -139,7 +139,7 @@
                                     "value": "tok04"
                                 },
                                 {
-                                    "displayname": "Toronto 01 (tor01)",
+                                    "displayname": "Toronto 01 (tor01) PER",
                                     "value": "tor01"
                                 },
                                 {
@@ -398,7 +398,7 @@
                             "required": true,
                             "options": [
                                 {
-                                    "displayname": "Dallas (dallas)",
+                                    "displayname": "Dallas (dallas) PER",
                                     "value": "us-south"
                                 },
                                 {
@@ -454,7 +454,7 @@
                                     "value": "tok04"
                                 },
                                 {
-                                    "displayname": "Toronto 01 (tor01)",
+                                    "displayname": "Toronto 01 (tor01) PER",
                                     "value": "tor01"
                                 },
                                 {

modules/pi-sap-system-type1/main.tf

@@ -15,7 +15,7 @@ resource "ibm_pi_network" "sap_network" {
 #####################################################
 
 locals {
-  pi_non_per_dc_list = ["mon01", "tor01", "lon04", "us-south", "us-east"]
+  pi_non_per_dc_list = ["mon01", "lon04", "us-east"]
   pi_per_disabled    = contains(local.pi_non_per_dc_list, var.pi_zone)
 }
 

reference-architectures/sap-ready-to-go/deploy-arch-ibm-pvs-sap-ready-to-go.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2023, 2024
-lastupdated: "2024-05-01"
+lastupdated: "2024-05-11"
 
 keywords:
 
@@ -12,7 +12,7 @@ authors:
   - name: Arnold Beilmann
   - name: Suraj Bharadwaj
 
-version: v1.10.0
+version: v1.11.0
 
 # Whether the reference architecture is published to Cloud Docs production.
 # When set to false, the file is available only in staging. Default is false.
@@ -53,7 +53,7 @@ content-type: reference-architecture
 {: toc-industry="Technology"}
 {: toc-use-case="ITServiceManagement"}
 {: toc-compliance="SAPCertified"}
-{: toc-version="1.10.0"}
+{: toc-version="1.11.0"}
 
 The SAP-ready PowerVS variation of the Power Virtual Server for SAP HANA creates a basic and expandable SAP system landscape. The variation builds on the foundation of the VPC landing zone and Power Virtual Server with VPC landing zone. PowerVS instances for SAP HANA, SAP NetWeaver, and optionally for shared SAP files are deployed and preconfigured for SAP installation.
 

reference-architectures/sap-s4hana-bw4hana/deploy-arch-ibm-pvs-sap-s4hana-bw4hana.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2023, 2024
-lastupdated: "2024-05-01"
+lastupdated: "2024-05-11"
 
 keywords:
 
@@ -12,7 +12,7 @@ authors:
   - name: Arnold Beilmann
   - name: Suraj Bharadwaj
 
-version: v1.10.0
+version: v1.11.0
 
 # Whether the reference architecture is published to Cloud Docs production.
 # When set to false, the file is available only in staging. Default is false.
@@ -53,7 +53,7 @@ content-type: reference-architecture
 {: toc-industry="Technology"}
 {: toc-use-case="ITServiceManagement"}
 {: toc-compliance="SAPCertified"}
-{: toc-version="1.10.0"}
+{: toc-version="1.11.0"}
 
 'SAP S/4HANA or BW/4HANA' variation of 'Power Virtual Server for SAP HANA' creates a basic and expandable SAP system landscape built on the foundation of 'Power Virtual Server with VPC landing zone'. PowerVS instances for SAP HANA, SAP NetWeaver, and optionally for shared SAP files are deployed and preconfigured for SAP installation. The S/4HANA or BW/4HANA solution is installed based on the selected version.