Overview of Power Virtual Server with VPC landing zone deployable architectures
Provisioning Power Virtual Server with VPC landing zone by using deployable architectures provides an automated deployment method to create an isolated Power Virtual Server workspace and connect it with IBM Cloud services and public internet. Network management components like DNS, NTP, proxy servers and NFS as a Service might be installed. Comparing the provisioning through the projects UI, user interaction is minimized and ready-to-go deployment time of a Power Virtual Server workspace is reduced from days to less than 1 hour.
Automated Power Virtual Server with VPC landing zone provisioning that is described in this guide is based on IBM Cloud catalog deployable architectures. In this documentation, we describe only specifics that are related to Power Virtual Server with VPC landing zone deployable architecture.
In the following sections, the deployable architecture variants are described.
Standard variation
This deployable architecture variation supports these features:
- A VPC Infrastructure with the following components:
- One RHEL VSI for management (jump/bastion)
- One RHEL VSI for network-services configured as squid proxy, NTP and DNS servers(using Ansible Galaxy collection roles ibm.power_linux_sap collection. This VSI also acts as central ansible execution node
- Optional Client to site VPN server
- Optional File storage share
- Optional Application load balancer
- IBM Cloud Object storage(COS) Virtual Private endpoint gateway(VPE)
- IBM Cloud Object storage(COS) Instance and buckets
- VPC flow logs
- KMS keys
- Activity tracker
- Optional Secrets Manager Instance Instance with private certificate
- A local or global transit gateway
- A Power Virtual Server workspace with the following network topology:
- Creates two private networks: a management network and a backup network
- Attaches Power Virtual Server workspace to transit gateway
- Creates an SSH key
- Optionally imports list of stock catalog images.
- Optionally imports up to three custom images from Cloud Object Storage.
Extend Power Virtual Server with VPC landing zone - Standard variation
This variation has a prerequisite. You must deploy the 'Create a new architecture Standard' variant first.
The 'Extend Power Virtual Server with VPC landing zone' variation creates an additional Power Virtual Server workspace and connects it to the existing 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'. This is typically used for High Availability scenarios in the same regions.
This deployable architecture variation supports these features:
- A Power Virtual Server workspace with the following network topology:
- Creates two private networks: a management network and a backup network
- Attaches the Power Virtual Server workspace to transit gateway
- Creates an SSH key
- Optionally imports list of stock catalog images.
- Optionally imports up to three custom images from Cloud Object Storage.
Quickstart variation
This deployable architecture variation supports these features:
- A VPC Infrastructure with the following components:
- One RHEL VSI for management (jump/bastion)
- One RHEL VSI for network-services configured as squid proxy, NTP and DNS servers(using Ansible Galaxy collection roles ibm.power_linux_sap collection. This VSI also acts as central ansible execution node.
- Optional Client to site VPN server
- Optional File storage share
- Optional Application load balancer
- IBM Cloud Object storage(COS) Virtual Private endpoint gateway(VPE)
- IBM Cloud Object storage(COS) Instance and buckets
- VPC flow logs
- KMS keys
- Activity tracker
- Optional Secrets Manager Instance Instance with private certificate.
- A local or global transit gateway
- A Power Virtual Server workspace with the following network topology:
- Creates two private networks: a management network and a backup network
- Attaches the Power Virtual Server workspace to transit gateway
- Creates an SSH key
- Imports cloud catalog stock images
- A Power Virtual Server Instance with following options:
- t-shirt profile (Aix/IBMi/SAP Image)
- Custom profile ( cores, memory, storage and image)
- 1 volume
You can run AIX, IBM i, and Linux images on your virtual server instances. Select the required T-shirt size and a virtual server instance with chosen T-shirt size or custom configuration is deployed. The T-shirt sizes and the configuration parameters mapping are shown in the following table:
| XS | S | M | L | |
|---|---|---|---|---|
| Cores | 1 | 4 | 8 | 15 |
| Memory | 32 | 128 | 256 | 512 |
| Storage Tier-3 (GB) | 100 | 500 | 1000 | 2000 |
| XS | S | M | L | |
|---|---|---|---|---|
| Cores | 0.25 | 1 | 2 | 4 |
| Memory | 8 | 32 | 64 | 132 |
| Storage Tier-3 (GB) | 100 | 500 | 1000 | 2000 |
| US1 Test/Dev |
|
|---|---|
| Cores | 4 |
| Memory | 128 |
| Storage Tier-3 (GB) | 750 |
Import variation
Create an IBM Cloud schematics workspace for your pre-existing VPC and Power Virtual Server infrastructure resources using the new Power Virtual Server (PowerVS) with VPC landing zone variation - 'Import Power Virtual Server Workspace'.
This variation 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 Power Virtual Server 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 Power Virtual Server instances for SAP on top of the existing infrastructure.
Check the pre-requisites for this variation here.
Other Power Virtual Server related deployable architectures
In addition to the Power Virtual Server with VPC landing zone other deployable architectures and terraform based solutions might be deployed.