Edit

Share via

Get started with manual deployment

  • Article

Along with automated deployment, you can also do manual deployment of the SAP on Azure Deployment Automation Framework. Use this example configuration and sample parameter files to get started.

Tip

This guide covers only how to perform a manual deployment. If you want to get started quickly, see the automated deployment guide instead.

These steps reference and use the default naming convention for the automation framework. Example values are also used for naming throughout the code. For example, the deployer name is DEMO-EUS2-DEP00-INFRASTRUCTURE. In this example, the environment is a demo (DEMO), the region is East US 2 (EUS2), and the deployer virtual network is DEP00.

Prerequisites

Deployer setup

Before you begin, check you're in the correct Azure subscription. Then, set up your deployer:

  1. Download and install Terraform.
  2. Clone and configure the automation framework repository on the deployer.
  3. Initialize Terraform
  4. Get your SSH keys for use in the rest of your deployment.

Check Azure subscription

Verify that you're using the appropriate Azure subscription:

  1. Sign in to the Azure portal.

  2. Open Azure Cloud Shell.

  3. Check that you're in the subscription you want to use:

    az account list --output=table | grep -i true

  4. If necessary, change the active subscription to the subscription you want to use.

Download Terraform

Download Terraform to your environment:

  1. Create and navigate to a new directory, bin.

    mkdir -p ~/bin; cd $_

  2. Retrieve the appropriate Terraform binary. For example:

    wget  https://releases.hashicorp.com/terraform/0.14.7/terraform_0.14.7_linux_amd64.zip

  3. Unzip the Terraform binary. For example:

    unzip terraform_0.14.7_linux_amd64.zip

  4. Verify your Terraform download:

    hash terraform

  5. Create a directory for your SAP automated deployment.

    mkdir -p ~/Azure_SAP_Automated_Deployment; cd $_

Set up repository

Clone and configure the automation framework repository.

  1. Clone the repository from GitHub:

    git clone https://github.com/Azure/sap-automation.git

  2. Navigate to the sap-automation folder.

    cd  ~/Azure_SAP_Automated_Deployment/sap-automation

  3. Optionally, check out a different branch than the main branch. The main branch for the repository is the default.

    1. Replace <branch> with the branch name or commit hash you want to use.

      git checkout <branch>

    2. Check that your branch is at the expected revision.

      git rev-parse HEAD

Initialize Terraform

  1. Create a working directory. The directory name must observe the default naming convention. For example:

    mkdir -p ~/Azure_SAP_Automated_Deployment/WORKSPACES/DEPLOYER/DEMO-EUS2-DEP00-INFRASTRUCTURE; cd $_

  2. Create the JSON parameter file.

    cat <<EOF > DEMO-EUS2-DEP00-INFRASTRUCTURE.json
{
  "infrastructure": {
    "environment"                         : "DEMO",
    "region"                              : "eastus2",
    "vnets": {
      "management": {
        "name"                            : "DEP00",
        "address_space"                   : "10.0.0.0/25",
        "subnet_mgmt": {
          "prefix"                        : "10.0.0.64/28"
        },
        "subnet_fw": {
          "prefix"                        : "10.0.0.0/26"
        }
      }
    }
  },
  "options": {
    "enable_deployer_public_ip"           : true
  },
  "firewall_deployment"                   : true
}
EOF

  3. Initialize Terraform.

    terraform init  ../../../sap-automation/deploy/terraform/bootstrap/sap_deployer/

  4. Create a Terraform execution plan that follows the default naming convention.

    terraform plan                                                                    \
                --var-file=DEMO-EUS2-DEP00-INFRASTRUCTURE.json                    \
                ../../../sap-automation/deploy/terraform/bootstrap/sap_deployer/

  5. Apply your Terraform execution plan to deploy the resources.

    terraform apply --auto-approve                                                    \
                --var-file=DEMO-EUS2-DEP00-INFRASTRUCTURE.json                    \
                ../../../sap-automation/deploy/terraform/bootstrap/sap_deployer/

  6. Note the output.

Get SSH keys

  1. Using the output from the Terraform deployment, note the values for the following fields.

    1. Public IP address: deployer_public_ip_address.

    2. Key vault's username: deployer_kv_user_name.

    3. Private key vault's name: deployer_kv_prvt_name.

    4. Public key's name: deployer_public_key_secret_name.

    5. Private key's name: deployer_private_key_secret_name.

  2. Run the post-processing script.

    ./post_deployment.sh

  3. Extract the private SSH key:

    az keyvault secret show               \
  --vault-name DEMOEUS2DEP00userE27   \
  --name DEMO-EUS2-DEP00-sshkey     | \
  jq -r .value > sshkey

  4. Extract the public SSH key:

    az keyvault secret show               \
  --vault-name DEMOEUS2DEP00userF6A   \
  --name DEMO-EUS2-DEP00-sshkey-pub | \
  jq -r .value > sshkey.pub

  5. Download the private and public key pair. In the Cloud Shell menu, select Upload/Download files > Download.

Service principal configuration

The deployer uses a service principal to deploy resources into a subscription.

  1. Sign in to the Azure CLI.

    az login

  2. Create a service principal. Be sure to replace <subscription-id> with your Azure subscription identifier. Also replace <sp-name> with a name for your service principal.

    az ad sp create-for-rbac --role="Contributor" --scopes="/subscriptions/<subscription-id>" --name="<sp-name>"

  3. Note the output, which contains information about the service principal. Copy down the values of the following fields:

    1. Application identifier: appId.

    2. Password: password.

    3. Tenant identifier: tenant.

  4. Create a role assignment for the service principal. Make sure to replace <appId> with the application identifier you noted in the previous step.

    az role assignment create --assignee <appId> --role "User Access Administrator" --scope /subscriptions/<subscription-id>/resourceGroups/<resource-group-name>

  5. Add keys for the service principal to the key vault as follows. Be sure to replace the placeholder values with the information you noted in previous steps. Replace <environment> with the name of your environment, such as DEMO.

    az keyvault secret set --name "<environment>-subscription-id" --vault-name "<deployer_kv_user_name>" --value "<subscription-id>";
az keyvault secret set --name "<environment>-tenant-id"       --vault-name "<deployer_kv_user_name>" --value "<tenant>";
az keyvault secret set --name "<environment>-client-id"       --vault-name "<deployer_kv_user_name>" --value "<appId>";
az keyvault secret set --name "<environment>-client-secret"   --vault-name "<deployer_kv_user_name>" --value "<password>";

Library configuration

  1. Sign in to the deployer using your SSH client and the SSH keys that you retrieved during the deployer setup. If you're using PuTTY as your SSH client, convert the SSH keys to .ppk format before using.

  2. Navigate to where you cloned the automation framework repository.

    cd  ~/Azure_SAP_Automated_Deployment/sap-automation

  3. Optionally, check out a different branch than the main branch. The main branch for the repository is the default.

    1. Replace <branch> with the branch name or commit hash you want to use.

      git checkout <branch>

    2. Check that your branch is at the expected revision.

      git rev-parse HEAD

  4. Create a working directory.

    mkdir -p ~/Azure_SAP_Automated_Deployment/WORKSPACES/LIBRARY/DEMO-EUS2-SAP_LIBRARY; cd $_

  5. Create the JSON configuration file.

    cat <<EOF > DEMO-EUS2-SAP_LIBRARY.json
{
  "infrastructure": {
    "environment"                         : "DEMO",
    "region"                              : "eastus2"
  },
  "deployer": {
    "environment"                         : "DEMO",
    "region"                              : "eastus2",
    "vnet"                                : "DEP00"
  }
}
EOF

  6. Initialize Terraform.

    terraform init  ../../../sap-automation/deploy/terraform/bootstrap/sap_library/

  7. Create a Terraform execution plan that follows the default naming convention.

    terraform plan                                                                  \
            --var-file=DEMO-EUS2-SAP_LIBRARY.json                           \
            ../../../sap-automation/deploy/terraform/bootstrap/sap_library

  8. Apply your Terraform execution plan to deploy the resources.

    terraform apply --auto-approve                                                  \
            --var-file=DEMO-EUS2-SAP_LIBRARY.json                           \
            ../../../sap-automation/deploy/terraform/bootstrap/sap_library/

Reinitialize deployment

Reinitialize both the deployer and the SAP library.

Reinitialize deployer

  1. Stay signed in to your deployer in the SSH client. Or, sign in again.

  2. Navigate to the working directory that you created.

    cd ~/Azure_SAP_Automated_Deployment/WORKSPACES/LOCAL/DEMO-EUS2-DEP00-INFRASTRUCTURE

  3. Create another parameter file called backend. Again, follow the default naming conventions. For resource_group_name, use the name of the resource group where the storage account with your Terraform state files (.tfstate) is located. For storage_account_name, replace <tfstate_storage_account_name> with the name of the storage account from the SAP Library deployment for .tfstate files. For key, combine the deployer's resource group name with the extension .terraform.tfstate. For example:

    cat <<EOF > backend
resource_group_name   = "DEMO-EUS2-SAP_LIBRARY"
storage_account_name  = "<tfstate_storage_account_name>"
container_name        = "tfstate"
key                   = "DEMO-EUS2-DEP00-INFRASTRUCTURE.terraform.tfstate"
EOF

  4. Initialize Terraform again.

    terraform init  --backend-config backend                                        \
                ../../../sap-automation/deploy/terraform/run/sap_deployer/

  5. When prompted Do you want to copy existing state to the new backend?, enter yes.

  6. Remove the local state file.

    rm terraform.tfstate*

  7. Create a Terraform execution plan. Again, follow the default naming conventions. For example:

    terraform plan                                                                  \
                --var-file=DEMO-EUS2-DEP00-INFRASTRUCTURE.json                  \
                ../../../sap-automation/deploy/terraform/run/sap_deployer/

  8. Apply the Terraform execution plan. For example:

    terraform apply --auto-approve                                                  \
                --var-file=DEMO-EUS2-DEP00-INFRASTRUCTURE.json                  \
                ../../../sap-automation/deploy/terraform/run/sap_deployer/

Reinitialize SAP Library

  1. Stay signed in to your deployer in the SSH client. Or, sign in again.

  2. Navigate to the working directory that you created.

    cd ~/Azure_SAP_Automated_Deployment/WORKSPACES/LIBRARY/DEMO-EUS2-SAP_LIBRARY

  3. Create another parameter file called backend. Again, follow the default naming conventions. For resource_group_name, use the name of the resource group where the storage account with your Terraform state files (.tfstate) is located. For storage_account_name, replace <tfstate_storage_account_name> with the name of the storage account from the SAP Library deployment for .tfstate files. For key, combine the deployer's resource group name with the extension .terraform.tfstate. For example:

    cat <<EOF > backend
resource_group_name   = "DEMO-EUS2-SAP_LIBRARY"
storage_account_name  = "<tfstate_storage_account_name>"
container_name        = "tfstate"
key                   = "DEMO-EUS2-SAP_LIBRARY.terraform.tfstate"
EOF

  4. Add a new key-value pair immediately after the opening bracket ({) of the parameter file backend. For tfstate_resource_id, use the resource identifier for the Terraform state file storage account. For deployer_tfstate_key, use the key name for the deployer state file. For example:

    {
    "tfstate_resource_id"                   : "<identifier>",
    "deployer_tfstate_key"                  : "<key>",
    "infrastructure": {
        ...
}

  5. Initialize Terraform again.

    terraform init  --backend-config backend                                          \
                ../../../sap-automation/deploy/terraform/run/sap_library/

  6. When prompted Do you want to copy existing state to the new backend?, enter yes.

  7. Remove the local state file.

    rm terraform.tfstate*

  8. Create a Terraform execution plan. Again, follow the default naming conventions. For example:

    terraform plan                                                                    \
                --var-file=DEMO-EUS2-SAP_LIBRARY.json                             \
                ../../../sap-automation/deploy/terraform/run/sap_library/

  9. Apply the Terraform execution plan. For example:

    terraform apply --auto-approve                                                    \
                --var-file=DEMO-EUS2-SAP_LIBRARY.json                             \
                ../../../sap-automation/deploy/terraform/run/sap_library/

Deploy workload virtual network

Next, deploy the SAP workload virtual network.

  1. Stay signed in to your deployer in the SSH client. Or, sign in again.

  2. Create a working directory. Follow the default naming conventions.

    mkdir -p ~/Azure_SAP_Automated_Deployment/WORKSPACES/LANDSCAPE/DEMO-EUS2-SAP00-INFRASTRUCTURE; cd $_

  3. Create a parameter file called backend. For resource_group_name, use the name of the resource group where the storage account with your Terraform state files (.tfstate) is located. For storage_account_name, replace <tfstate_storage_account_name> with the name of the storage account from the SAP Library deployment for .tfstate files. For key, combine the deployer's resource group name with the extension .terraform.tfstate. For example:

    cat <<EOF > backend
resource_group_name   = "DEMO-EUS2-SAP_LIBRARY"
storage_account_name  = "<tfstate_storage_account_name>"
container_name        = "tfstate"
key                   = "DEMO-EUS2-SAP00-INFRASTRUCTURE.terraform.tfstate"
EOF

  4. Initialize Terraform again.

    terraform init  --backend-config backend                                        \
                ../../../sap-automation/deploy/terraform/run/sap_landscape/

  5. Create a Terraform execution plan. Again, follow the default naming conventions. For example:

    terraform plan                                                                  \
            --var-file=DEMO-EUS2-SAP00-INFRASTRUCTURE.json                  \
            ../../../sap-automation/deploy/terraform/run/sap_landscape/

  6. Apply the Terraform execution plan. For example:

    terraform apply --auto-approve                                                  \
                --var-file=DEMO-EUS2-SAP00-INFRASTRUCTURE.json                  \
                ../../../sap-automation/deploy/terraform/run/sap_landscape/

SAP deployment unit

Next, set up the SAP deployment unit.

  1. Stay signed in to your deployer in the SSH client. Or, sign in again

  2. Create a working directory. Follow the default naming conventions.

    mkdir -p ~/Azure_SAP_Automated_Deployment/WORKSPACES/SYSTEM/DEMO-EUS2-SAP00-X00; cd $_

  3. Create another parameter file called backend. For resource_group_name, use the name of the resource group where the storage account with your Terraform state files (.tfstate) is located. For storage_account_name, replace <tfstate_storage_account_name> with the name of the storage account from the SAP Library deployment for .tfstate files. For key, combine the deployer's resource group name with the extension .terraform.tfstate. For example:

    cat <<EOF > backend
resource_group_name   = "DEMO-EUS2-SAP_LIBRARY"
storage_account_name  = "<tfstate_storage_account_name>"
container_name        = "tfstate"
key                   = "DEMO-EUS2-SAP00-X00.terraform.tfstate"
EOF

  4. Create a JSON parameter file with input parameters as follows. Make sure to replace the sample values with your own.

    cat <<EOF > DEMO-EUS2-SAP00-X00.json
{
  "tfstate_resource_id"                   : "<resource-id>",
  "deployer_tfstate_key"                  : "DEMO-EUS2-DEP00-INFRASTRUCTURE.terraform.tfstate",
  "landscape_tfstate_key"                 : "DEMO-EUS2-SAP00-INFRASTRUCTURE.terraform.tfstate",
  "infrastructure": {
    "environment"                         : "DEMO",
    "region"                              : "eastus2",
    "vnets": {
      "sap": {
        "name"                            : "SAP00",
        "subnet_db": {
          "prefix"                        : "0.0.0.0/28"
        },
        "subnet_web": {
          "prefix"                        : "0.0.0.0/28"
        },
        "subnet_app": {
          "prefix"                        : "0.0.0.0/27"
        },
        "subnet_admin": {
          "prefix"                        : "0.0.0.0/27"
        }
      }
    }
  },
  "databases": [
    {
      "platform"                          : "HANA",
      "high_availability"                 : false,
      "size"                              : "S4Demo",
      "os": {
        "publisher"                       : "SUSE",
        "offer"                           : "sles-sap-12-sp5",
        "sku"                             : "gen2",
        "version"                         : "latest"
      }
    }
  ],
  "application": {
    "enable_deployment"                   : true,
    "sid"                                 : "X00",
    "scs_instance_number"                 : "00",
    "ers_instance_number"                 : "10",
    "scs_high_availability"               : false,
    "application_server_count"            : 3,
    "webdispatcher_count"                 : 1,
    "authentication": {
      "type"                              : "key",
      "username"                          : "azureadm"
    }
  }
}
EOF

  5. Initialize Terraform again.

    terraform init  --backend-config backend                                        \
                ../../../sap-automation/deploy/terraform/run/sap_system/

  6. Create a Terraform execution plan. Again, follow the default naming conventions. For example:

    terraform plan                                                                  \
                --var-file=DEMO-EUS2-SAP00-X00.json                             \
                ../../../sap-automation/deploy/terraform/run/sap_system/

  7. Apply the Terraform execution plan. For example:

    terraform apply --auto-approve                                                  \
                --var-file=DEMO-EUS2-SAP00-X00.json                             \
                ../../../sap-automation/deploy/terraform/run/sap_system/

Ansible configuration

Configure your setup by executing Ansible playbooks. These playbooks are located in the automation framework repository in /sap-automation/deploy/ansible.

Filename Description
playbook_01_os_base_config.yaml Base operating system (OS) configuration
playbook_02_os_sap_specific_config.yaml SAP-specific OS configuration
playbook_03_bom_processing.yaml SAP Bill of Materials (BOM) processing software download
playbook_04a_sap_scs_install.yaml SAP central services (SCS) installation
playbook_05a_hana_db_install.yaml SAP HANA database installation
playbook_06a_sap_dbload.yaml Database loader
playbook_06b_sap_pas_install.yaml SAP primary application server (PAS) installation
playbook_06c_sap_app_install.yaml SAP application server installation
playbook_06d_sap_web_install.yaml SAP web dispatcher installation
playbook_06_00_00_pacemaker.yaml Pacemaker cluster configuration
playbook_06_00_01_pacemaker_scs.yaml Pacemaker configuration for SCS
playbook_06_00_03_pacemaker_hana.yaml Pacemaker configuration for SAP HANA database

To execute a playbook or multiple playbooks, use the command ansible-playbook as follows. Be sure to change all placeholder values to your own information:

  • Change <your-sapbits-path> to the path to your storage account sapbits for the SAP Library.
  • Change <azure-admin> to your Azure administrator username.
  • Change <ssh-key> to the private SSH key you want to use.
  • Change other values under --extra-vars as needed for your settings.

If you experience issues, make sure you've downloaded the SAP software to your Azure environment.

export           ANSIBLE_HOST_KEY_CHECKING=False
# export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=Yes
# export           ANSIBLE_KEEP_REMOTE_FILES=1


ansible-playbook                                                                                                      \
  --inventory   new-hosts.yaml                                                                                        \
  --user        <azure-admin>                                                                                              \
  --private-key <ssh-key>                                                                                                \
  --extra-vars="{                                                                                                     \
                  \"bom_base_name\":                \"HANA_2_00_053_v001\",                                           \
                  \"download_templates\":           \"false\",                                                        \
                  \"sapbits_location_base_path\":   \"<your-sapbits-path>",        \
                  \"target_media_location\":        \"/usr/sap/install\",                                             \
                  \"sap_sid\":                      \"X00\",                                                          \
                  \"hdb_sid\":                      \"HDB\"                                                           \
                }"                                                                                                    \
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/playbook_00_transition_start_for_sap_install_refactor.yaml     \
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/playbook_01_os_base_config.yaml                       \
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/playbook_02_os_sap_specific_config.yaml               \
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/playbook_03_bom_processing.yaml                       \
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/playbook_04a_sap_scs_install.yaml                     \
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/playbook_05a_hana_db_install.yaml                     \
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/playbook_06a_sap_dbload.yaml                          \
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/playbook_06b_sap_pas_install.yaml                     \
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/playbook_06c_sap_app_install.yaml                     \
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/playbook_06d_sap_web_install.yaml

Next steps

Get started quickly with an automated deployment