Supported terraform version 1.1.X

• libvirt/KVM
• azure
• google cloud
• aws
• OpenStack

• HA Clusters and HANA deployment
• Preparing SAP software
• Monitoring of cluster
• S/4HANA and NetWeaver
• DRBD
• Saptune
• Fencing mechanism
• IP addresses auto generation

We provide minimal templates for setting up the terraform variables in order to get started with the project. For fine tuning refer to variable specification.

• templates

This project is based in terraform and salt usage.

Components:

• terraform: Terraform is used to create the required infrastructure in the specified provider. The code is divided in different terraform modules to make the code modular and more maintanable.
• salt: Salt configures all the created machines by terraform based in the provided pillar files that give the option to customize the deployment.

The project can deploy and configure the next components (they can be enabled/disabled through configuration options):

• SAP HANA environment: The HANA deployment is configurable. It might be deployed as a single HANA database, a dual configuration with system replication, and a HA cluster can be set in top of that.
• ISCSI server: The ISCSI server provides a network based storage mostly used by sbd fencing mechanism.
• Monitoring services server: The monitoring solution is based in prometheus and grafana and it provides informative and customizable dashboards to the users and administrators.
• DRBD cluster: The DRBD cluster is used to mount a HA NFS server in top of it to mount NETWEAVER shared files.
• SAP NETWEAVER environment: A SAP NETWEAVER environment with ASCS, ERS, PAS and AAS instances can be deployed using HANA database as storage.

This project is organized in folders containing the Terraform configuration files per Public or Private Cloud providers, each also containing documentation relevant to the use of the configuration files and to the cloud provider itself.

This project uses Terraform for the deployment and Saltstack for the provisioning.

Be careful with what instance type you will use because default choice is systems certified by SAP, so cost could be expensive if you leave the default value.

These are links to find certified systems for each provider:

• SAP Certified IaaS Platforms for AWS

• SAP Certified IaaS Platforms for GCP

• SAP Certified IaaS Platforms for Azure (Be carreful with Azure, clustering means scale-out scenario)

In the case you have some issue, take a look at the troubleshooting guide