Terraform Templates for deployment of various SAP Software solution scenarios onto different Hyperscaler Cloud Service Providers and Hypervisors platforms.

Infrastructure-as-Code (IaC) for deployment of host infrastructure uses Terraform, which will subsequently perform Configuration-as-Code (CaC) for configuraton of OS and installation of SAP Software using Ansible.

These Terraform Templates for SAP are designed to be:

• simple to understand,
• highly reconfigurable,
• result in an equal installation performed to any Infrastructure Platform

for more detail: Available SAP solution scenarios and Infrastructure Platforms

It is recommended to fully read the README below for context and understanding, before you execute this code.

To get started immediately, requirements:

• Infrastructure Platform credentials and required authorizations (see Infrastructure Guidance); depending on choice may require OS Vendor subscription
• SAP ONE Support Launchpad credentials, with Software Download privileges
• Terraform and Ansible installed
• Optional, depending on choice SAP solution scenario: SAP System Copy backup file

cd /terraform.templates_for_sap/sap_s4hana_single_node_install_maintenance_plan/ibmcloud_vs
terraform init
terraform apply -var-file=variables_generic_for_cli.tfvars

This project is designed to be outcome-focused and highly-reusable.

Each Terraform Template is for a pre-defined SAP Software solution scenario on a given Infrastructure Platform, e.g. SAP HANA installation to Microsoft Azure, or SAP ECC on HANA System Copy (Homogeneous) to IBM Cloud.

This Project is built of two technology components:

• Infrastructure-as-Code (IaC) for deployment of host infrastructure. Uses Terraform.
• Configuration-as-Code (CaC) for configuraton of OS and installation of SAP Software. Uses Ansible, dynamically altered by Terraform.

These Terraform Templates are constructed using the custom Terraform Modules for SAP, which can be combined to create new Terraform Templates for different scenarios. The provided solution scenarios are a baseline, from which amendments and extensions can be made to create any SAP Software solution scenario on any Infrastructure Platform.

The project addresses common SAP System activities such as:

• initial SAP software installations (Maintenance Planner)
• move or clone SAP Systems to new infrastructure (System Copy)

The project therefore assists SAP-run enterprises to achieve various outcomes, such as:

Each Terraform Template is for a deployment of a SAP Software solution scenario to a platform, and reuses custom Terraform Modules for SAP to provision resources (e.g. host machines) and execute Ansible Playbooks (referencing Ansible Collection Role/s) for configuration of OS and installation of SAP software.

Segregation of definitions for the Infrastructure and SAP Software follows the same delineation:

• Terraform defines the Infrastructure Specification templates
• Ansible defines the SAP Software installation / SAP System templates

An overview of the execution flow is provided in the image below, for full details please see:

• the Execution Flow documentation
• the Infrastructure Platform guidance to use Terraform Templates for SAP
• the FAQ, includes information for customized deployments of SAP Software solution scenarios
• the detailed documentation in Terraform Modules for SAP

The following is a list of Infrastructure Platforms and Operating System vendors which the Terraform Templates are compatible with, and the various SAP solution scenarios which are developed.

Hyperscaler Cloud Service Providers, provisioned via Terraform:

• Amazon Web Services (AWS), EC2 instance (Intel Virtual Machine)
• Google Cloud Platform (GCP), Compute Engine Intel Virtual Machine [after initial release]
• IBM Cloud, Intel Virtual Server
• IBM Cloud, IBM Power Virtual Server
• Microsoft Azure, Intel Virtual Machine

Hypervisors, provisioned via Terraform:

• IBM PowerVM LPAR
• OVirt / Red Hat Virtualization Virtual Machine [after initial release]
• VMware vSphere Virtual Machine [after initial release]

Operating Systems:

• Red Hat Enterprise Linux for SAP Solutions (RHEL4SAP)
• SUSE Linux Enterprise Server for SAP Applications (SLES4SAP)

Solution Architecture scenarios, provisioned via Ansible:

Key:

• ✅ Ready and Tested
• ⚠️ Pending work; either the Terraform Template has not been created/tested for this SAP solution scenario and infrastructure platform, or work is pending to underlying Terraform Modules for SAP
• ❌ Not available yet

Future SAP solution scenarios:

There are various suggested/requested SAP solution scenarios under consideration by the SAP LinuxLab open-source team (across multiple SAP Technology Partners), which have been suggested from customers and SAP Service Partners.

While the Ansible Collections for SAP are compatbile with almost any installation (e.g. SAP SolMan, SAP WebDispatcher, SAP BW/4HANA) - our focus in this project is to provide a common end-to-end automated deployment for common scenarios, therefore we are unable to working code for all combinations. For additional detail, see Disclaimer section.

Any contributors who would are available for development and testing of these proposed future SAP solution scenarios in this project are greatly welcomed, please read the Contributors document. As described in the SAP LinuxLab initiative governance processes, any customer or SAP Partner may submit proposals of new code or direction.

The following list is not a commitment but is a statement of intent beyond the initial release, the terraform.templates_for_sap project seeks to include in future:

SAP software installation media must be obtained from SAP directly, and requires valid license agreements with SAP in order to access these files.

An SAP Company Number (SCN) contains one or more Installation Number/s, providing licences for specified SAP Software. When an SAP User ID is created within the SAP Customer Number (SCN), the administrator must provide SAP Download authorizations for the SAP User ID.

When an SAP User ID (e.g. S-User) is enabled with and part of an SAP Universal ID, then the sap_launchpad Ansible Collection must use:

• the SAP User ID
• the password for login with the SAP Universal ID

In addition, if a SAP Universal ID is used then the recommendation is to check and reset the SAP User ID ‘Account Password’ in the SAP Universal ID Account Manager, which will help to avoid any potential conflicts.

The execution/controller host of the Terraform Templates must contain:

• Terraform 1.0+
• Ansible Core 2.11+, may work with Ansible 2.9+ but is not fully tested
• git client
• Python 3+ (i.e. CPython distribution)

Tests with Ansible Core release versions:

• Ansible Core 2.11.5 community edition

Tests with Python release versions:

• Python 3.9.7 (i.e. CPython distribution)

Tests with Operating System release versions:

• macOS 11.6 (Big Sur) and 12.3 (Monterey), with Homebrew used for Python 3.x via PyEnv (using iTerm with Bash 5.1 or Terminal with zsh 5.8)
• Windows 10, November 2021 Update (21H2), with Windows Subsystem for Linux v2 (WSL2) and Ubuntu 20.04

These are common SAP solution scenarios which are codified using Infrastructure Automation for SAP (Terraform) and Build Automation for SAP (Ansible). These can be extended as needed for bespoke requirements.

This does not intend (and can not) replicate every SAP software deployment scenario, and does not replace any existing SAP installation procedures detailed in the SAP Help Portal or SAP Notes on SAP ONE Support. However, with the Ansible Role for SAP SWPM is possible to install any SAP Software which is supported by SAP Software Provisioning Manager (SWPM 1.0/2.0).

For move-fast activities, such as rapid provisioning and administration testing tasks (latest software releases and revision/patch levels, system copy restore to Cloud etc.), these Terraform Templates for SAP can be amended to suit these requirements.

For greater support in automating the lifecycle of SAP Systems themselves, it is recommended to consider SAP Landscape Management Enterprise Edition.

For greater demo and evaluation of SAP Software business functionality, it is recommended to consider SAP Cloud Appliance Library.