Overview of Power Virtual Server with VPC landing zone deployable architecture

Provisioning Power Virtual Server with VPC landing zone by using deployable architectures provides an automated deployment method to create an isolated PowerVS 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 PowerVS 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.

Create a new architecture - Standard variation

Deploys VPC services and a Power Virtual Server workspace and interconnects them.

A proxy service for public internet access from the PowerVS workspace is configured. You can optionally configure some management components on VPC (such as an NFS as a Service, Client to site VPN, NTP forwarder, and DNS forwarder).

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.

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.

Create a new architecture - Quickstart variation

You can now deploy a Power Virtual Server (PowerVS) with VPC landing zone that creates VPC services, a Power Virtual Server workspace and interconnect them.

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:

Table 1. T-shirt size and configuration mapping
	XS	S	M	L
Cores	1	4	8	15
Memory	32	128	256	512
Storage Tier-3 (GB)	100	500	1000	2000

Table 1. T-shirt size and configuration mapping
	XS	S	M	L
Cores	0.25	1	2	4
Memory	8	32	64	132
Storage Tier-3 (GB)	100	500	1000	2000

Table 1. T-shirt size and configuration mapping
	US1 Test/Dev
Cores	4
Memory	128
Storage Tier-3 (GB)	750

Create a new architecture - Import variation

Create an IBM Cloud schematics workspace for your pre-existing VPC and PowerVS infrastructure resources using the new Power Virtual Server (PowerVS) with VPC landing zone variation - 'Import PowerVS 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' automations 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.

Check the pre-requisites for this variation here.

Other PowerVS related deployable architectures

In addition to the Power Virtual Server with VPC landing zone other deployable architectures and terraform based solutions might be deployed.