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
Copy file name to clipboardExpand all lines: articles/sap/automation/deploy-workload-zone.md
+36-49Lines changed: 36 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,20 +14,22 @@ ms.subservice: sap-automation
14
14
15
15
An [SAP application](deployment-framework.md#sap-concepts) typically has multiple development tiers. For example, you might have development, quality assurance, and production tiers. The [SAP on Azure Deployment Automation Framework](deployment-framework.md) refers to these tiers as [workload zones](deployment-framework.md#deployment-components).
16
16
17
-
You can use workload zones in multiple Azure regions. Each workload zone then has its own Azure Virtual Network (Azure VNet)
17
+
You can use workload zones in multiple Azure regions. Each workload zone then has its own Azure Virtual Network (Azure virtual network)
18
18
19
19
The following services are provided by the SAP workload zone:
20
20
21
21
- Azure Virtual Network, including subnets and network security groups.
22
22
- Azure Key Vault, for system credentials.
23
23
- Storage account for boot diagnostics
24
24
- Storage account for cloud witnesses
25
+
- Azure NetApp account and capacity pools (optional)
26
+
- Azure Files NFS Shares (optional)
25
27
26
28
:::image type="content" source="./media/deployment-framework/workload-zone.png" alt-text="Diagram SAP Workload Zone.":::
27
29
28
30
The workload zones are typically deployed in spokes in a hub and spoke architecture. They may be in their own subscriptions.
29
31
30
-
Supports the Private DNS from the Control Plane.
32
+
Supports the Private DNS from the Control Plane or from a configurable source.
31
33
32
34
33
35
## Core configuration
@@ -89,9 +91,9 @@ az role assignment create --assignee <appId> \
89
91
90
92
## Deploying the SAP Workload zone
91
93
92
-
The sample Workload Zone configuration file `DEV-WEEU-SAP01-INFRASTRUCTURE.tfvars` is located in the `~/Azure_SAP_Automated_Deployment/samples/WORKSPACES/LANDSCAPE/DEV-WEEU-SAP01-INFRASTRUCTURE` folder.
94
+
The sample Workload Zone configuration file `DEV-WEEU-SAP01-INFRASTRUCTURE.tfvars` is located in the `~/Azure_SAP_Automated_Deployment/samples/Terraform/WORKSPACES/LANDSCAPE/DEV-WEEU-SAP01-INFRASTRUCTURE` folder.
93
95
94
-
Running the command below will deploy the SAP Workload Zone.
96
+
Running the following command deploys the SAP Workload Zone.
95
97
96
98
# [Linux](#tab/linux)
97
99
@@ -103,62 +105,47 @@ You can copy the sample configuration files to start testing the deployment auto
It isn't possible to perform the deployment from Windows.
162
149
---
163
150
164
151
> [!NOTE]
@@ -175,7 +162,7 @@ Open (https://dev.azure.com) and go to your Azure DevOps Services project.
175
162
> [!NOTE]
176
163
> Ensure that the 'Deployment_Configuration_Path' variable in the 'SDAF-General' variable group is set to the folder that contains your configuration files, for this example you can use 'samples/WORKSPACES'.
177
164
178
-
The deployment will use the configuration defined in the Terraform variable file located in the 'samples/WORKSPACES/LANDSCAPE/DEV-WEEU-SAP01-INFRASTRUCTURE' folder.
165
+
The deployment uses the configuration defined in the Terraform variable file located in the 'samples/WORKSPACES/LANDSCAPE/DEV-WEEU-SAP01-INFRASTRUCTURE' folder.
179
166
180
167
Run the pipeline by selecting the _Deploy workload zone_ pipeline from the Pipelines section. Enter the workload zone configuration name and the deployer environment name. Use 'DEV-WEEU-SAP01-INFRASTRUCTURE' as the Workload zone configuration name and 'MGMT' as the Deployer Environment Name.
0 commit comments