You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# The environment value is a mandatory field, it is used for partitioning the environments, for example, PROD and NP.
329
329
environment = "LAB"
330
330
# The location/region value is a mandatory field, it is used to control where the resources are deployed
331
-
location = "westeurope"
331
+
location = "swedencentral"
332
332
333
333
#Defines the DNS suffix for the resources
334
334
dns_label = "lab.sdaf.contoso.net"
@@ -349,9 +349,9 @@ Use the [deploy_controlplane.sh](bash/deploy-controlplane.md) script to deploy t
349
349
350
350
The deployment goes through cycles of deploying the infrastructure, refreshing the state, and uploading the Terraform state files to the library storage account. All of these steps are packaged into a single deployment script. The script needs the location of the configuration file for the deployer and library, and some other parameters.
351
351
352
-
For example, choose **West Europe** as the deployment location, with the four-character name `WEEU`, as previously described. The sample deployer configuration file `LAB-WEEU-DEP05-INFRASTRUCTURE.tfvars` is in the `${HOME}/Azure_SAP_Automated_Deployment/WORKSPACES/DEPLOYER/LAB-WEEU-DEP05-INFRASTRUCTURE` folder.
352
+
For example, choose **West Europe** as the deployment location, with the four-character name `SECE`, as previously described. The sample deployer configuration file `LAB-SECE-DEP05-INFRASTRUCTURE.tfvars` is in the `${HOME}/Azure_SAP_Automated_Deployment/WORKSPACES/DEPLOYER/LAB-SECE-DEP05-INFRASTRUCTURE` folder.
353
353
354
-
The sample SAP library configuration file `LAB-WEEU-SAP_LIBRARY.tfvars` is in the `${HOME}/Azure_SAP_Automated_Deployment/WORKSPACES/LIBRARY/LAB-WEEU-SAP_LIBRARY` folder.
354
+
The sample SAP library configuration file `LAB-SECE-SAP_LIBRARY.tfvars` is in the `${HOME}/Azure_SAP_Automated_Deployment/WORKSPACES/LIBRARY/LAB-SECE-SAP_LIBRARY` folder.
355
355
356
356
Set the environment variables for the service principal:
- name: "Kernel Part I ; OS: Linux on x86_64 64bit ; DB: Database independent"
846
846
```
847
847
848
-
For this example configuration, the resource group is `LAB-WEEU-DEP05-INFRASTRUCTURE`. The deployer key vault name contains `LABWEEUDEP05user`in the name. You use this information to configure your deployer's key vault secrets.
848
+
For this example configuration, the resource group is `LAB-SECE-DEP05-INFRASTRUCTURE`. The deployer key vault name contains `LABSECEDEP05user`in the name. You use this information to configure your deployer's key vault secrets.
849
849
850
850
1. Connect to your deployer VM for the following steps. A copy of the repo is now there.
851
851
@@ -916,13 +916,16 @@ The SAP application installation happens through Ansible playbooks.
916
916
Go to the system deployment folder.
917
917
918
918
```bash
919
-
cd ${HOME}/Azure_SAP_Automated_Deployment/WORKSPACES/SYSTEM/LAB-WEEU-SAP04-L00/
919
+
cd ${HOME}/Azure_SAP_Automated_Deployment/WORKSPACES/SYSTEM/LAB-SECE-SAP04-L00/
920
920
```
921
921
922
922
Make sure you have the following files in the current folders: `sap-parameters.yaml` and `L00_host.yaml`.
923
923
924
924
For a standalone SAP S/4HANA system, there are eight playbooks to run in sequence. One way you can run the playbooks is to use the **Configuration** menu.
925
925
926
+
:::image type="content" source="./media/deployment-framework/automation-diagram-full.png" alt-text="Diagram that shows the SAP Deployment Automation Framework environment.":::
927
+
928
+
926
929
Run the `configuration_menu` script.
927
930
928
931
```bash
@@ -991,28 +994,28 @@ Before you begin, sign in to your Azure account. Then, check that you're in the
991
994
992
995
### Remove the SAP infrastructure
993
996
994
-
Go to the `DEV-WEEU-SAP01-X00` subfolder inside the `SYSTEM` folder. Then, run this command:
997
+
Go to the `LAB-SECE-SAP01-L00` subfolder inside the `SYSTEM` folder. Then, run this command:
0 commit comments