Use Ansible to deploy various SAP Software solution scenarios onto different Hyperscaler Cloud Service Providers and Hypervisors platforms.
These Ansible Playbooks for SAP are designed to be:
licensed for corporate usage
by SAP Customers, SAP Service Partners and SAP Technology PartnersNote: Ansible Playbooks for SAP optionally use Ansible > Terraform. To instead use Terraform > Ansible, see Terraform Templates for SAP
Please read the full documentation for how-to guidance, requirements, and all other details. Summary documentation is below:
Ansible Playbooks are available for Operating Systems:
Ansible Playbooks are available for Infrastructure Platforms:
[Experimental]
[Beta]
Ansible Playbooks are available for SAP Software Solution Scenarios:
Ansible Playbooks available with Special Actions for SAP Software:
[Experimental]
[Experimental]
[Experimental]
Get Started: See full documentation section Example execution of Ansible Playbooks for SAP
Below is a summary of the execution method and deployment options:
Execution Method | Ansible with existing host/s | Ansible provisions host/s | Ansible uses Terraform to provision minimal landing zone and host/s[Beta] |
---|---|---|---|
Interactive variable prompts[Coming Soon] |
Not Available | Enter ansible when prompted to Please choose Infrastructure-as-Code automation from list |
Enter ansible_to_terraform when prompted to Please choose Infrastructure-as-Code automation from list |
Standard (non-interactive) | In Extra Vars file, set sap_vm_provision_iac_type: existing_hosts |
In Extra Vars file, set sap_vm_provision_iac_type: ansible |
In Extra Vars file, set sap_vm_provision_iac_type: ansible_to_terraform |
Summary:SAP installation :white_check_mark: Provisions hosts :x: Infrastructure setup :x: |
Summary:SAP installation :white_check_mark: Provisions hosts :white_check_mark: Infrastructure setup :x: |
Summary:SAP installation :white_check_mark: Provisions hosts :white_check_mark: Infrastructure setup :white_check_mark: |
|
Intended usage: SAP installation to existing host/s, using an existing setup on an Infrastructure Platform. Target hosts are defined using an Ansible Inventory file. |
Intended usage: SAP installation to host/s provisioned by Ansible, using an existing setup on an Infrastructure Platform. Target hosts are defined using a dynamically generated Ansible Inventory created during runtime (after hosts are provisioned). |
Intended usage: SAP installation to host/s provisioned by executing Terraform to create a minimal setup on an Infrastructure Platform. Target hosts are defined using a dynamically generated Ansible Inventory created during runtime (after hosts are provisioned). |
These are common SAP Software Solution Scenarios which are codified using Ansible to provide for Infrastructure-as-Code (IaC) Automation for SAP and Configuration-as-Code (CaC) Automation for SAP. 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 it 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 Ansible Playbooks 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.
Key contributors are shown within the contributors file.