Skip to content

Latest commit

 

History

History
66 lines (54 loc) · 6.23 KB

File metadata and controls

66 lines (54 loc) · 6.23 KB

IBM Power Virtual Server with VPC Landing Zone

Graduated (Supported) semantic-release pre-commit latest release Renovate enabled

Summary

This repository contains deployable architecture solutions that help provision VPC landing zones, PowerVS workspaces, and interconnect them. The solutions are available in the IBM Cloud Catalog and can also be deployed without the catalog, except for the second solution below.

Four solutions are offered:

  1. Standard
    • Creates a VPC and Power Virtual Server workspace, interconnects them, and configures OS network management services (SQUID proxy, NTP, NFS, and DNS services) using Ansible Galaxy collection roles ibm.power_linux_sap collection.
  2. Standard Extend
    • Extends the standard solution by creating a new Power Virtual Server workspace in a different zone and interconnects with the previous solution.
    • This solution is typically used for High Availability scenarios where a single management VPC can be used to reach both PowerVS workspaces.
  3. Quickstart (Standard plus VSI)
    • Creates a VPC and a Power Virtual Server workspace, interconnects them, and configures operating network management services (SQUID proxy, NTP, NFS, and DNS services) using Ansible Galaxy collection roles ibm.power_linux_sap collection.
    • Additionally creates a Power Virtual Server Instance of a selected t-shirt size.
    • This solution is typically utilized for PoCs, demos, and quick onboarding to PowerVS Infrastructure.
  4. Import
    • Takes information about an existing infrastructure and creates a schematics workspace.
    • The schematics workspace's ID and the outputs from it can be used to install the terraform solution 'Power Virtual Server for SAP HANA' on top of a pre-existing PowerVS infrastructure.
    • It creates the ACL and security group rules necessary for management services (NTP, NFS, DNS, and proxy server) and schematics engine access.
    • This solution is typically used for converting an existing Power Virtual Server landscape to a Schematics workspace.

Reference architectures

Solutions

Variation Available on IBM Catalog Requires IBM Schematics Workspace ID Creates VPC Landing Zone Performs VPC VSI OS Config Creates PowerVS Infrastructure Creates PowerVS Instance Performs PowerVS OS Config
Standard ✔️ N/A ✔️ ✔️ ✔️ N/A N/A
Standard Extend ✔️ ✔️ N/A N/A ✔️ N/A N/A
Quickstart (Standard plus VSI) ✔️ N/A ✔️ ✔️ ✔️ ✔️ N/A
Import ✔️ N/A N/A N/A N/A N/A N/A

Required IAM access policies

You need the following permissions to run this module.

  • Account Management
    • Resource Group service
      • Viewer platform access
    • IAM Services
      • Workspace for Power Virtual Server service
      • Power Virtual Server service
        • Editor platform access
      • VPC Infrastructure Services service
        • Editor platform access
      • Transit Gateway service
        • Editor platform access
      • Direct Link service
        • Editor platform access

Contributing

You can report issues and request features for this module in GitHub issues in the module repository. See Report an issue or request a feature.

To set up your local development environment, see Local development setup in the project documentation.