Script files

The configuration and script files are provided on the GitHub repository https://github.com/IBM-Cloud/sap-infra-anydb-distributed.

For 2-tier and 3-tier VPC for SAP, you modify the input.auto.tfvars file to customize the resources for your solution. You specify zones, resource names, and SSH keys.

All of the other configuration files are provided and do not need to be modified.

The IBM Cloud Provider plug-in for Terraform on IBM Cloud uses these configuration files to provision a VPC in your IBM Cloud account.

What is created

A VPC is a private space in IBM Cloud where you can run an isolated environment with custom network policies. The variables that you define are used by the scripts to provision the following VPC infrastructure resources for you:

• 1 VPC where you provision your virtual server instance.
• 1 security group and rules for this security group to allow DNS and SSH connections to your virtual server instance and all outbound traffic.
• 1 subnet to enable networking in your VPC.
• 2 virtual server instances (1 SAP App VSI and 1 DB(anydb) instance server VSI).
• 2 storage volumes, 1 for swap and 1 for data for SAP app VSI and 4 storage 1 x SWAP and 3 x DATA volumes for DB VSI.

The VSIs are configured with Red Hat Enterprise Linux 8.x for SAP Applications (amd64) and Suse Enterprise Linux 15 (amd64) and they have at least one SSH key that are configured to access as root user. The VSIs have the following storage volumes:

DB virtual server instance disks: • 1x 40 GB disk with 10 IOPS / GB - SWAP • 1 x 32 GB disk with 10 IOPS / GB - DATA (DB LOG) • 1x 64 GB disk with 10 IOPS / GB - DATA (DB ARCHIVE LOG) • 1 x 128/256 GB disk with 10 IOPS / GB – DATA

SAP app virtual server instance disks: • 1x 40 GB disk with 10 IOPS / GB - SWAP • 1 x 128 GB disk with 10 IOPS / GB – DATA

Support

There are no warranties of any kind, and there is no service or technical support available for these materials from IBM®. As a recommended practice, review carefully any materials that you download from this site before using them on a live system.

Though the materials provided herein are not supported by the IBM Service organization, your comments are welcomed by the developers, who reserve the right to revise, re-adapt or remove the materials at any time. To report a problem, or provide suggestions or comments, open a GitHub issue.

Before you begin

1. If you do not have Terraform installed, Install the Terraform CLI and the IBM Cloud Provider plug-in.

   If you are using Terraform 0.13 and higher, you do not need to install the IBM Cloud Provider Plug-in. You modify the configuration files provided on the 1-Tier VPC for SAP GitHub repository to specify the plug-in version to use.

   If you are using Terraform 1.12.x and earlier, follow these IBM Cloud Provider Plug-in installation instructions. Do not configure the plug-in.

   Do not do any IBM Cloud Provider Plug-in configuration because those files are provided for you.

2. Create or retrieve an IBM Cloud API key. The API key is used to authenticate with the IBM Cloud platform and to determine your permissions for IBM Cloud services.

3. Create or retrieve your SSH key ID. You need the 40-digit UUID for the SSH key, not the SSH key name.

Procedure

Use these steps to configure the IBM Cloud Provider Plug-in and use Terraform to create a VPC for SAP.

1. Create a project folder in the Terraform installation folder, and change directory to your project folder.

   mkdir myproject && cd myproject

2. Copy the files from https://github.com/IBM-Cloud/sap-infra-anydb-distributed/tree/main to the project folder that you created in the Terraform installation directory.

3. Edit the input.auto.tfvars file to customize your solution. Modify the file to specify your VPC name, subnet, security group, hostname, profile, image, SSH keys, and disk sizes. You must modify:

   • VPC - Unique VPC name.
   • SECURITYGROUP - Change ic4sap to the VPC name.
   • SUBNET - Change ic4sap to the VPC name.
   • DB/APP HOSTNAME - Enter a hostname up to 13 characters. For more information, see the README file.

   For disk sizes, volumes are created with the required size and are attached to the VSIs. The size for the volumes is defined as a list in the VOLUME_SIZES variable with each value specifying capacity for a volume in GB.

   You need your 40-digit SSH key ID for this file. The second SSH key is optional.

   For more options for profile, see Instance Profiles. For more options for image, see Images.

   # General VPC variables:
   REGION        = "eu-de" # default value
   ZONE          = "eu-de-2" # default value
   VPC           = "ic4sap"
   SECURITYGROUP = "ic4sap-securitygroup"
   SUBNET        = "ic4sap-subnet"
   SSH_KEYS      = [ "r010-57bfc315-f9e5-46bf-bf61-d87a24a9ce7a" , "r010-3fcd9fe7-d4a7-41ce-8bb3-d96e936b2c7e" ]
   DB_PROFILE = "bx2-4x16"
   APP_PROFILE = "bx2-4x16"
   DB_IMAGE = "ibm-redhat-8-6-amd64-sap-applications-4"
   APP_IMAGE = "ibm-redhat-8-6-amd64-sap-applications-4"
   
   # SAP Database VSI variables:
   DB_HOSTNAME = "ep12db"
   DB_VOLUME_SIZES = [ "40" , "32" , "64" , "128" ]
   
   
   # SAP APPs VSI variables:
   APP_HOSTNAME = "ep12app" # default value
   APP_VOLUME_SIZES= [ "40" , "128" ]
   
   

   Parameter	Description
   REGION	The cloud region where the solution is deployed. The regions and zones for VPC are listed here.
   ZONE	The cloud zone where the solution is deployed.
   VPC	The name of the VPC. The list of VPCs is available here.
   SECURITYGROUP	The name of the Security Group. The list of Security Groups is available here
   SUBNET	The name of the Subnet. The list of Subnets is available here
   DB_PROFILE	The profile used for the VSI. A list of profiles is available here.
   APP_PROFILE	The profile used for the VSI. A list of profiles is available here.
   DB_IMAGE	The OS image used for the VSI. A list of images is available here.
   APP_IMAGE	The OS image used for the VSI. A list of images is available here.
   SSH_KEYS	List of SSH Keys IDs that are allowed to SSH as root to the VSI. Can contain one or more IDs. The list of SSH Keys is available here.
   [DB/APP]_HOSTNAME	The hostname for the VSI. The hostname must have up to 13 characters as required by SAP. For more information about rules regarding hostnames for SAP systems, see SAP Note 611361 - Hostnames of SAP ABAP Platform servers.

4. Initialize the Terraform CLI.

   terraform init
   

5. Create a Terraform execution plan. The Terraform execution plan summarizes all the actions that are done to create the VPC instance in your account.

   terraform init
   

6. Verify that the plan shows all of the resources that you want to create and that the names and values are correct. If the plan needs to be adjusted, edit the input.auto.tfvars file to correct resources and run terraform plan again.

7. Create the VPC for SAP instance and IAM access policy in IBM Cloud.

   terraform apply
   

   The VPC and components are created and you see output similar to the terraform plan output.

This automation is offered at no cost; however, the provisioned infrastructure comes at cost.

Next steps

If you need to rename your resources after they are created, modify the input.auto.tfvars file to change the names and run terraform plan and terraform apply again. Do not use the IBM Cloud Dashboard and user interface to modify your VPC after it is created. The Terraform scripts create a complete solution and selectively modifying resources with the user interface might cause unexpected results.

If you need to remove your VPC, go to your project folder and run terraform destroy.