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
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'.
The PowerVS workspace deployment of the Power Virtual Server with VPC landing zone creates VPC services and a Power Virtual Server workspace and interconnects them.
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-workspace' 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.
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.
|[ibm_schematics_output.schematics_output](https://registry.terraform.io/providers/IBM-Cloud/ibm/1.61.0/docs/data-sources/schematics_output)| data source |
55
+
|[ibm_schematics_workspace.schematics_workspace](https://registry.terraform.io/providers/IBM-Cloud/ibm/1.61.0/docs/data-sources/schematics_workspace)| data source |
56
+
57
+
### Inputs
58
+
59
+
| Name | Description | Type | Default | Required |
| <aname="input_IC_SCHEMATICS_WORKSPACE_ID"></a> [IC\_SCHEMATICS\_WORKSPACE\_ID](#input\_IC\_SCHEMATICS\_WORKSPACE\_ID)| leave blank if running locally. This variable will be automatically populated if running from an IBM Cloud Schematics workspace |`string`|`""`| no |
62
+
| <aname="input_cloud_connection"></a> [cloud\_connection](#input\_cloud\_connection)| Cloud connection configuration: speed (50, 100, 200, 500, 1000, 2000, 5000, 10000 Mb/s), count (1 or 2 connections), global\_routing (true or false), metered (true or false). Not applicable for DCs where PER is enabled. | <pre>object({<br> count = number<br> speed = number<br> global_routing = bool<br> metered = bool<br> })</pre> | <pre>{<br> "count": 2,<br> "global_routing": true,<br> "metered": true,<br> "speed": 5000<br>}</pre> | no |
63
+
| <aname="input_ibmcloud_api_key"></a> [ibmcloud\_api\_key](#input\_ibmcloud\_api\_key)| The IBM Cloud platform API key needed to deploy IAM enabled resources. |`string`| n/a | yes |
64
+
| <aname="input_powervs_backup_network"></a> [powervs\_backup\_network](#input\_powervs\_backup\_network)| Name of the IBM Cloud PowerVS backup network and CIDR to create. | <pre>object({<br> name = string<br> cidr = string<br> })</pre> | <pre>{<br> "cidr": "10.62.0.0/24",<br> "name": "bkp_net"<br>}</pre> | no |
65
+
| <aname="input_powervs_image_names"></a> [powervs\_image\_names](#input\_powervs\_image\_names)| List of Images to be imported into cloud account from catalog images. Supported values can be found [here](https://github.com/terraform-ibm-modules/terraform-ibm-powervs-infrastructure/blob/main/solutions/full-stack/docs/catalog_image_names.md)|`list(string)`| <pre>[<br> "IBMi-75-02-2924-1",<br> "IBMi-75-02-2984-1",<br> "7300-01-02",<br> "7200-05-06",<br> "SLES15-SP4-SAP",<br> "SLES15-SP4-SAP-NETWEAVER",<br> "RHEL8-SP6-SAP",<br> "RHEL8-SP6-SAP-NETWEAVER"<br>]</pre> | no |
66
+
| <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.61.0.0/24",<br> "name": "mgmt_net"<br>}</pre> | no |
67
+
| <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 |
68
+
| <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 |
69
+
| <aname="input_prerequisite_workspace_id"></a> [prerequisite\_workspace\_id](#input\_prerequisite\_workspace\_id)| IBM Cloud Schematics workspace ID of the prerequisite infrastructure. If you do not have an existing deployment yet, create a new architecture using the same catalog tile. |`string`| n/a | yes |
70
+
| <aname="input_tags"></a> [tags](#input\_tags)| List of tag names for the IBM Cloud PowerVS workspace |`list(string)`|`[]`| no |
71
+
72
+
### Outputs
73
+
74
+
| Name | Description |
75
+
|------|-------------|
76
+
| <aname="output_access_host_or_ip"></a> [access\_host\_or\_ip](#output\_access\_host\_or\_ip)| Access host for created PowerVS infrastructure. |
77
+
| <aname="output_cloud_connection_count"></a> [cloud\_connection\_count](#output\_cloud\_connection\_count)| Number of cloud connections configured in created PowerVS infrastructure. |
78
+
| <aname="output_dns_host_or_ip"></a> [dns\_host\_or\_ip](#output\_dns\_host\_or\_ip)| DNS forwarder host for created PowerVS infrastructure. |
79
+
| <aname="output_nfs_host_or_ip_path"></a> [nfs\_host\_or\_ip\_path](#output\_nfs\_host\_or\_ip\_path)| NFS host for created PowerVS infrastructure. |
80
+
| <aname="output_ntp_host_or_ip"></a> [ntp\_host\_or\_ip](#output\_ntp\_host\_or\_ip)| NTP host for created PowerVS infrastructure. |
81
+
| <aname="output_powervs_backup_subnet"></a> [powervs\_backup\_subnet](#output\_powervs\_backup\_subnet)| Name, ID and CIDR of backup private network in created PowerVS infrastructure. |
| <aname="output_powervs_management_subnet"></a> [powervs\_management\_subnet](#output\_powervs\_management\_subnet)| Name, ID and CIDR of management private network in created PowerVS infrastructure. |
84
+
| <aname="output_powervs_resource_group_name"></a> [powervs\_resource\_group\_name](#output\_powervs\_resource\_group\_name)| IBM Cloud resource group where PowerVS infrastructure is created. |
85
+
| <aname="output_powervs_ssh_public_key"></a> [powervs\_ssh\_public\_key](#output\_powervs\_ssh\_public\_key)| SSH public key name and value in created PowerVS infrastructure. |
86
+
| <aname="output_powervs_workspace_guid"></a> [powervs\_workspace\_guid](#output\_powervs\_workspace\_guid)| PowerVS infrastructure workspace guid. The GUID of the resource instance. |
87
+
| <aname="output_powervs_workspace_id"></a> [powervs\_workspace\_id](#output\_powervs\_workspace\_id)| PowerVS infrastructure workspace id. The unique identifier of the new resource instance. |
| <aname="output_powervs_zone"></a> [powervs\_zone](#output\_powervs\_zone)| Zone where PowerVS infrastructure is created. |
90
+
| <aname="output_prefix"></a> [prefix](#output\_prefix)| The prefix that is associated with all resources |
91
+
| <aname="output_proxy_host_or_ip_port"></a> [proxy\_host\_or\_ip\_port](#output\_proxy\_host\_or\_ip\_port)| Proxy host:port for created PowerVS infrastructure. |
92
+
| <aname="output_schematics_workspace_id"></a> [schematics\_workspace\_id](#output\_schematics\_workspace\_id)| ID of the IBM Cloud Schematics workspace. Returns null if not ran in Schematics |
93
+
| <aname="output_ssh_public_key"></a> [ssh\_public\_key](#output\_ssh\_public\_key)| The string value of the ssh public key used when deploying VPC |
94
+
| <aname="output_transit_gateway_id"></a> [transit\_gateway\_id](#output\_transit\_gateway\_id)| The ID of transit gateway. |
95
+
| <aname="output_transit_gateway_name"></a> [transit\_gateway\_name](#output\_transit\_gateway\_name)| The name of the transit gateway. |
96
+
| <aname="output_vpc_names"></a> [vpc\_names](#output\_vpc\_names)| A list of the names of the VPC. |
97
+
| <aname="output_vsi_list"></a> [vsi\_list](#output\_vsi\_list)| A list of VSI with name, id, zone, and primary ipv4 address, VPC Name, and floating IP. |
98
+
| <aname="output_vsi_names"></a> [vsi\_names](#output\_vsi\_names)| A list of the vsis names provisioned within the VPCs. |
0 commit comments