add new regions config files for ibm cloud

Signed-off-by: Petr Balogh <[email protected]>

conf/deployment/ibmcloud/ibm_cloud_vpc_cluster_zone_jp_tok_1.yaml

@@ -0,0 +1,29 @@
+
+# This is the basic config for IBM cloud usage
+---
+ENV_DATA:
+  platform: 'ibm_cloud'
+  deployment_type: 'managed'
+  region: 'jp-tok'
+  worker_availability_zone: 'jp-tok-1'
+  provider: "vpc-gen2"
+  worker_instance_type: "bx2.16x64"
+  master_replicas: 0
+  worker_replicas: 3
+  worker_availability_zones:
+    - 'jp-tok-1'
+  rhel_workers: true
+  # Following values needs to be set in separate config and passed to ocs-ci in
+  # order to deploy OCP/OCS cluster on IBM Cloud
+  # vpc_id: VPC ID PLACEHOLDER
+  # subnet_id: SUBNET ID PLACEHOLDER
+  # cos_instance: COS INSTANCE PLACEHOLDER
+#AUTH:
+#  ibmcloud:
+#    api_key: IBM CLOUD API KEY PLACEHOLDER
+#    account_id: ACCOUNT ID PLACEHOLDER
+#    ibm_cos_access_key_id: KEY PLACEHOLDER
+#    ibm_cos_secret_access_key: SECRET PLACEHOLDER
+DEPLOYMENT:
+  cnv_latest_stable: true
+  # ocs_secret_dockerconfigjson: BASE64 OF QUAY SECRET PLACEHOLDER

conf/deployment/ibmcloud/ibm_cloud_vpc_cluster_zone_jp_tok_2.yaml

@@ -0,0 +1,29 @@
+
+# This is the basic config for IBM cloud usage
+---
+ENV_DATA:
+  platform: 'ibm_cloud'
+  deployment_type: 'managed'
+  region: 'jp-tok'
+  worker_availability_zone: 'jp-tok-2'
+  provider: "vpc-gen2"
+  worker_instance_type: "bx2.16x64"
+  master_replicas: 0
+  worker_replicas: 3
+  worker_availability_zones:
+    - 'jp-tok-2'
+  rhel_workers: true
+  # Following values needs to be set in separate config and passed to ocs-ci in
+  # order to deploy OCP/OCS cluster on IBM Cloud
+  # vpc_id: VPC ID PLACEHOLDER
+  # subnet_id: SUBNET ID PLACEHOLDER
+  # cos_instance: COS INSTANCE PLACEHOLDER
+#AUTH:
+#  ibmcloud:
+#    api_key: IBM CLOUD API KEY PLACEHOLDER
+#    account_id: ACCOUNT ID PLACEHOLDER
+#    ibm_cos_access_key_id: KEY PLACEHOLDER
+#    ibm_cos_secret_access_key: SECRET PLACEHOLDER
+DEPLOYMENT:
+  cnv_latest_stable: true
+  # ocs_secret_dockerconfigjson: BASE64 OF QUAY SECRET PLACEHOLDER

conf/deployment/ibmcloud/ibm_cloud_vpc_cluster_zone_jp_tok_3.yaml

@@ -0,0 +1,29 @@
+
+# This is the basic config for IBM cloud usage
+---
+ENV_DATA:
+  platform: 'ibm_cloud'
+  deployment_type: 'managed'
+  region: 'jp-tok'
+  worker_availability_zone: 'jp-tok-3'
+  provider: "vpc-gen2"
+  worker_instance_type: "bx2.16x64"
+  master_replicas: 0
+  worker_replicas: 3
+  worker_availability_zones:
+    - 'jp-tok-3'
+  rhel_workers: true
+  # Following values needs to be set in separate config and passed to ocs-ci in
+  # order to deploy OCP/OCS cluster on IBM Cloud
+  # vpc_id: VPC ID PLACEHOLDER
+  # subnet_id: SUBNET ID PLACEHOLDER
+  # cos_instance: COS INSTANCE PLACEHOLDER
+#AUTH:
+#  ibmcloud:
+#    api_key: IBM CLOUD API KEY PLACEHOLDER
+#    account_id: ACCOUNT ID PLACEHOLDER
+#    ibm_cos_access_key_id: KEY PLACEHOLDER
+#    ibm_cos_secret_access_key: SECRET PLACEHOLDER
+DEPLOYMENT:
+  cnv_latest_stable: true
+  # ocs_secret_dockerconfigjson: BASE64 OF QUAY SECRET PLACEHOLDER

conf/deployment/ibmcloud/ibm_cloud_vpc_cluster_zone_us_east_1.yaml

@@ -0,0 +1,29 @@
+
+# This is the basic config for IBM cloud usage
+---
+ENV_DATA:
+  platform: 'ibm_cloud'
+  deployment_type: 'managed'
+  region: 'us-east'
+  worker_availability_zone: 'us-east-1'
+  provider: "vpc-gen2"
+  worker_instance_type: "bx2.16x64"
+  master_replicas: 0
+  worker_replicas: 3
+  worker_availability_zones:
+    - 'us-east-1'
+  rhel_workers: true
+  # Following values needs to be set in separate config and passed to ocs-ci in
+  # order to deploy OCP/OCS cluster on IBM Cloud
+  # vpc_id: VPC ID PLACEHOLDER
+  # subnet_id: SUBNET ID PLACEHOLDER
+  # cos_instance: COS INSTANCE PLACEHOLDER
+#AUTH:
+#  ibmcloud:
+#    api_key: IBM CLOUD API KEY PLACEHOLDER
+#    account_id: ACCOUNT ID PLACEHOLDER
+#    ibm_cos_access_key_id: KEY PLACEHOLDER
+#    ibm_cos_secret_access_key: SECRET PLACEHOLDER
+DEPLOYMENT:
+  cnv_latest_stable: true
+  # ocs_secret_dockerconfigjson: BASE64 OF QUAY SECRET PLACEHOLDER

conf/deployment/ibmcloud/ibm_cloud_vpc_cluster_zone_us_east_2.yaml

@@ -0,0 +1,29 @@
+
+# This is the basic config for IBM cloud usage
+---
+ENV_DATA:
+  platform: 'ibm_cloud'
+  deployment_type: 'managed'
+  region: 'us-east'
+  worker_availability_zone: 'us-east-2'
+  provider: "vpc-gen2"
+  worker_instance_type: "bx2.16x64"
+  master_replicas: 0
+  worker_replicas: 3
+  worker_availability_zones:
+    - 'us-east-2'
+  rhel_workers: true
+  # Following values needs to be set in separate config and passed to ocs-ci in
+  # order to deploy OCP/OCS cluster on IBM Cloud
+  # vpc_id: VPC ID PLACEHOLDER
+  # subnet_id: SUBNET ID PLACEHOLDER
+  # cos_instance: COS INSTANCE PLACEHOLDER
+#AUTH:
+#  ibmcloud:
+#    api_key: IBM CLOUD API KEY PLACEHOLDER
+#    account_id: ACCOUNT ID PLACEHOLDER
+#    ibm_cos_access_key_id: KEY PLACEHOLDER
+#    ibm_cos_secret_access_key: SECRET PLACEHOLDER
+DEPLOYMENT:
+  cnv_latest_stable: true
+  # ocs_secret_dockerconfigjson: BASE64 OF QUAY SECRET PLACEHOLDER

conf/deployment/ibmcloud/ibm_cloud_vpc_cluster_zone_us_east_3.yaml

@@ -0,0 +1,29 @@
+
+# This is the basic config for IBM cloud usage
+---
+ENV_DATA:
+  platform: 'ibm_cloud'
+  deployment_type: 'managed'
+  region: 'us-east'
+  worker_availability_zone: 'us-east-3'
+  provider: "vpc-gen2"
+  worker_instance_type: "bx2.16x64"
+  master_replicas: 0
+  worker_replicas: 3
+  worker_availability_zones:
+    - 'us-east-3'
+  rhel_workers: true
+  # Following values needs to be set in separate config and passed to ocs-ci in
+  # order to deploy OCP/OCS cluster on IBM Cloud
+  # vpc_id: VPC ID PLACEHOLDER
+  # subnet_id: SUBNET ID PLACEHOLDER
+  # cos_instance: COS INSTANCE PLACEHOLDER
+#AUTH:
+#  ibmcloud:
+#    api_key: IBM CLOUD API KEY PLACEHOLDER
+#    account_id: ACCOUNT ID PLACEHOLDER
+#    ibm_cos_access_key_id: KEY PLACEHOLDER
+#    ibm_cos_secret_access_key: SECRET PLACEHOLDER
+DEPLOYMENT:
+  cnv_latest_stable: true
+  # ocs_secret_dockerconfigjson: BASE64 OF QUAY SECRET PLACEHOLDER