Power Virtual Server with VPC landing zone - 'Standard Extend Variation'
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'.
Architecture diagram
Design requirements
IBM Cloud® Power Virtual Servers (PowerVS) is a public cloud offering that an enterprise can use to establish its own private IBM Power computing environment on shared public cloud infrastructure. PowerVS is logically isolated from all other public cloud tenants and infrastructure components, creating a private, secure place on the public cloud. This deployable architecture provides a framework to build a PowerVS offering according to the best practices and requirements from the IBM Cloud.
Components
PowerVS workspace architecture decisions
Requirement | Component | Choice | Alternative choice |
---|---|---|---|
|
Transit gateway | Set up a local transit gateway | |
|
Management network | Configure private network with default configurations | |
|
Backup network | Configure separate private network with default configurations and attach it to both cloud connections. Networks characteristics might be adapted by the users manually (for example to improve throughput) | |
|
Preloaded OS images | Preload Stock catalog OS images. | Modify the input parameter that specifies the list of preloaded OS images. |
|
Custom OS images | Import up to three images from COS into the PowerVS workspace. | Modify the optional input parameters that specify the list of custom OS images and the COS configuration and credentials . |
|
Preloaded SSH public key | Preload customer specified SSH public key |
PowerVS management services architecture decisions
Requirement | Component | Choice | Alternative choice |
---|---|---|---|
|
SQUID proxy | Set up SQUID proxy software on Linux virtual server instance that is running in edge VPC | |
|
File storage shares in VPC | Use the files storage share service running in VPC. Disk size is specified by the user. | |
|
NTP forwarder | Synchronize time by using public NTP servers. Set up time synchronization on Linux virtual server instance that is running in workload VPC. | By using time synchronization servers directly reachable from PowerVS workspace, NTP forwarder is not required. |
|
DNS forwarder | Configure DNS forwarder on Linux virtual server instance that is running in edge VPC | By using default IBM Cloud DNS service, DNS forwarder is not needed. Direct domain name resolution is possible. |
Key and password management architecture decisions
Requirement | Component | Choice | Alternative choice |
---|---|---|---|
|
Public SSH key - provided by customer. Private SSH key - provided by customer. | Ask customer to specify the keys. Accept the input as secure parameter or as reference to the key stored in IBM Cloud Secure Storage Manager. Do not print SSH keys in any log files. Do not persist private SSH key. Ask for private SSH key only if management components can be reconfigured, otherwise do not enforce private SSH key to be entered. |
Compliance
This reference architecture is certified for SAP deployments.
Next steps
Install the SAP on Power deployable architecture on this infrastructure.