You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"description": "The Power Virtual Server with VPC landing zone as variation 'Create a new architecture' deploys VPC services and a Power Virtual Server workspace and interconnects them.\n\nRequired and optional management components are configured."
@@ -1194,7 +1194,7 @@
1194
1194
{
1195
1195
"diagram": {
1196
1196
"caption": "Power Virtual Server with VPC landing zone 'Quickstart' variation",
"description": "The Power Virtual Server with VPC landing zone as 'Quickstart' variation of 'Create a new architecture' option deploys VPC services and a Power Virtual Server workspace and interconnects them. It also creates one Power virtual server instance of chosen t-shirt size or custom configuration.\n\nRequired and optional management components are configured."
@@ -1520,7 +1520,7 @@
1520
1520
{
1521
1521
"diagram": {
1522
1522
"caption": "Power Virtual Server with VPC landing zone 'Import' variation",
"description": "This solution helps to install the deployable architecture 'Power Virtual Server for SAP HANA' on top of a pre-existing Power Virtual Server(PowerVS) landscape. 'Power Virtual Server for SAP HANA' automation requires a schematics workspace id for installation. The 'Import' solution creates a schematics workspace by taking pre-existing VPC and PowerVS infrastructure resource details as inputs. The ID of this schematics workspace will be the pre-requisite workspace id required by 'Power Virtual Server for SAP HANA' to create and configure the PowerVS instances for SAP on top of the existing infrastructure.\n\nRequired and optional management components are configured."
@@ -1838,7 +1838,7 @@
1838
1838
{
1839
1839
"diagram": {
1840
1840
"caption": "Power Virtual Server with VPC landing zone 'Standard Extend' variation",
"description": "The Power Virtual Server with VPC landing zone as variation 'Extend Power Virtual Server with VPC landing zone' creates an additional Power Virtual Server workspace and connects it with already created Power Virtual Server with VPC landing zone. It builds on existing Power Virtual Server with VPC landing zone deployed as a variation 'Create a new architecture'."
@@ -154,7 +154,7 @@ Creates VPC Landing Zone | Performs VPC VSI OS Config | Creates PowerVS Infrastr
154
154
| <aname="input_powervs_management_network"></a> [powervs\_management\_network](#input\_powervs\_management\_network)| Name of the IBM Cloud PowerVS management subnet and CIDR to create. | <pre>object({<br/> name = string<br/> cidr = string<br/> })</pre> | <pre>{<br/> "cidr": "10.51.0.0/24",<br/> "name": "mgmt_net"<br/>}</pre> | no |
155
155
| <aname="input_powervs_resource_group_name"></a> [powervs\_resource\_group\_name](#input\_powervs\_resource\_group\_name)| Existing IBM Cloud resource group name. |`string`| n/a | yes |
156
156
| <aname="input_powervs_zone"></a> [powervs\_zone](#input\_powervs\_zone)| IBM Cloud data center location where IBM PowerVS infrastructure will be created. |`string`| n/a | yes |
157
-
| <aname="input_prefix"></a> [prefix](#input\_prefix)| A unique identifier for resources. Must begin with a lowercase letter and end with a lowercase letter or number. This prefix will be prepended to any resources provisioned by this template. Prefixes must be 10 or fewer characters. |`string`| n/a | yes |
157
+
| <aname="input_prefix"></a> [prefix](#input\_prefix)| A unique identifier for resources. Must begin with a lowercase letter and end with a lowercase letter or number. Must contain only lowercase letters, numbers, and - characters. This prefix will be prepended to any resources provisioned by this template. Prefixes must be 16 or fewer characters. |`string`| n/a | yes |
158
158
| <aname="input_sm_service_plan"></a> [sm\_service\_plan](#input\_sm\_service\_plan)| The service/pricing plan to use when provisioning a new Secrets Manager instance. Allowed values: `standard` and `trial`. Only used if `existing_sm_instance_guid` is set to null. |`string`|`"standard"`| no |
159
159
| <aname="input_ssh_private_key"></a> [ssh\_private\_key](#input\_ssh\_private\_key)| Private SSH key (RSA format) to login to Intel VSIs to configure network management services (SQUID, NTP, DNS and ansible). Should match to public SSH key referenced by 'ssh\_public\_key'. The key is not uploaded or stored. For more information about SSH keys, see [SSH keys](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys). |`string`| n/a | yes |
160
160
| <aname="input_ssh_public_key"></a> [ssh\_public\_key](#input\_ssh\_public\_key)| Public SSH Key for VSI creation. Must be an RSA key with a key size of either 2048 bits or 4096 bits (recommended). Must be a valid SSH key that does not already exist in the deployment region. |`string`| n/a | yes |
description="A unique identifier for resources. Must begin with a lowercase letter and end with a lowercase letter or number. This prefix will be prepended to any resources provisioned by this template. Prefixes must be 10 or fewer characters."
12
+
description="A unique identifier for resources. Must begin with a lowercase letter and end with a lowercase letter or number. Must contain only lowercase letters, numbers, and - characters. This prefix will be prepended to any resources provisioned by this template. Prefixes must be 16 or fewer characters."
Copy file name to clipboardExpand all lines: reference-architectures/import/deploy-arch-ibm-pvs-inf-import.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
copyright:
3
3
years: 2024, 2025
4
-
lastupdated: "2025-03-18"
4
+
lastupdated: "2025-03-24"
5
5
keywords:
6
6
subcollection: deployable-reference-architectures
7
7
authors:
@@ -16,7 +16,7 @@ use-case: ITServiceManagement
16
16
industry: Technology
17
17
compliance:
18
18
content-type: reference-architecture
19
-
version: v8.2.1
19
+
version: v8.2.2
20
20
21
21
---
22
22
@@ -27,7 +27,7 @@ version: v8.2.1
27
27
{: toc-content-type="reference-architecture"}
28
28
{: toc-industry="Technology"}
29
29
{: toc-use-case="ITServiceManagement"}
30
-
{: toc-version="v8.2.1"}
30
+
{: toc-version="v8.2.2"}
31
31
32
32
This solution helps to install the deployable architecture ['Power Virtual Server for SAP HANA'](https://cloud.ibm.com/catalog/architecture/deploy-arch-ibm-pvs-sap-9aa6135e-75d5-467e-9f4a-ac2a21c069b8-global) on top of a pre-existing Power Virtual Server(PowerVS) landscape. 'Power Virtual Server for SAP HANA' automation requires a schematics workspace id for installation. The 'Import' solution creates a schematics workspace by taking pre-existing VPC and PowerVS infrastructure resource details as inputs. The ID of this schematics workspace will be the pre-requisite workspace id required by 'Power Virtual Server for SAP HANA' to create and configure the PowerVS instances for SAP on top of the existing infrastructure.
The Power Virtual Server with VPC landing zone as variation 'Extend Power Virtual Server with VPC landing zone' creates an additional Power Virtual Server workspace and connects it with the already created Power Virtual Server with VPC landing zone. It builds on the existing Power Virtual Server with VPC landing zone deployed as a variation 'Create a new architecture'.
Quickstart deployment of the Power Virtual Server with VPC landing zone creates VPC services, a Power Virtual Server workspace, and interconnects them. It also deploys a Power Virtual Server of chosen T-shirt size or custom configuration. Supported Os are Aix, IBM i, and Linux images.
The Standard deployment of the Power Virtual Server with VPC landing zone creates VPC services and a Power Virtual Server workspace and interconnects them.
0 commit comments