Skip to content

Commit 1248fc8

Browse files
author
Kimmo Forss
committed
Workload zone command updates
1 parent 1d98aa8 commit 1248fc8

File tree

1 file changed

+36
-49
lines changed

1 file changed

+36
-49
lines changed

articles/sap/automation/deploy-workload-zone.md

Lines changed: 36 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -14,20 +14,22 @@ ms.subservice: sap-automation
1414

1515
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).
1616

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)
1818

1919
The following services are provided by the SAP workload zone:
2020

2121
- Azure Virtual Network, including subnets and network security groups.
2222
- Azure Key Vault, for system credentials.
2323
- Storage account for boot diagnostics
2424
- Storage account for cloud witnesses
25+
- Azure NetApp account and capacity pools (optional)
26+
- Azure Files NFS Shares (optional)
2527

2628
:::image type="content" source="./media/deployment-framework/workload-zone.png" alt-text="Diagram SAP Workload Zone.":::
2729

2830
The workload zones are typically deployed in spokes in a hub and spoke architecture. They may be in their own subscriptions.
2931

30-
Supports the Private DNS from the Control Plane.
32+
Supports the Private DNS from the Control Plane or from a configurable source.
3133

3234

3335
## Core configuration
@@ -89,9 +91,9 @@ az role assignment create --assignee <appId> \
8991

9092
## Deploying the SAP Workload zone
9193

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.
9395

94-
Running the command below will deploy the SAP Workload Zone.
96+
Running the following command deploys the SAP Workload Zone.
9597

9698
# [Linux](#tab/linux)
9799

@@ -103,62 +105,47 @@ You can copy the sample configuration files to start testing the deployment auto
103105
```bash
104106
cd ~/Azure_SAP_Automated_Deployment
105107

106-
cp -R sap-automation/samples/WORKSPACES WORKSPACES
108+
cp -R sap-automation/samples/WORKSPACES config
107109

108110
```
109111

110112

111113
```bash
112114

113-
export subscriptionId="<subscriptionId>"
114-
export spn_id="<appId>"
115-
export spn_secret="<password>"
116-
export tenant_id="<tenantId>"
117-
export env_code="MGMT"
118-
export region_code="<region_code>"
115+
export subscriptionId="<subscriptionId>"
116+
export spn_id="<appId>"
117+
export spn_secret="<password>"
118+
export tenant_id="<tenantId>"
119+
export env_code="DEV"
120+
export region_code="<region_code>"
121+
export vnet_code="SAP02"
122+
export deployer_environment="MGMT"
123+
export deployer_tfstate_key="MGMT"
124+
125+
az login --service-principal -u $spn_id -p=$spn_secret --tenant $tenant_id
126+
119127

120128
export DEPLOYMENT_REPO_PATH="${HOME}/Azure_SAP_Automated_Deployment/sap-automation"
121129
export ARM_SUBSCRIPTION_ID="${subscriptionId}"
122-
123-
${DEPLOYMENT_REPO_PATH}/deploy/scripts/prepare_region.sh \
124-
--deployer_parameter_file DEPLOYER/${env_code}-${region_code}-DEP00-INFRASTRUCTURE/${env_code}-${region_code}-DEP00-INFRASTRUCTURE.tfvars \
125-
--library_parameter_file LIBRARY/${env_code}-${region_code}-SAP_LIBRARY/${env_code}-${region_code}-SAP_LIBRARY.tfvars \
126-
--subscription "${subscriptionId}" \
127-
--spn_id "${spn_id}" \
128-
--spn_secret "${spn_secret}" \
129-
--tenant_id "${tenant_id}" \
130-
--auto-approve
130+
export CONFIG_REPO_PATH="${HOME}/Azure_SAP_Automated_Deployment/config/WORKSPACES"
131+
export SAP_AUTOMATION_REPO_PATH="${HOME}/Azure_SAP_Automated_Deployment/sap-automation"
132+
133+
cd "${CONFIG_REPO_PATH}/LANDSCAPE/${env_code}-${region_code}-${vnet_code}-INFRASTRUCTURE"
134+
parameterFile="${env_code}-${region_code}-${vnet_code}-INFRASTRUCTURE.tfvars"
135+
136+
$SAP_AUTOMATION_REPO_PATH/deploy/scripts/install_workloadzone.sh \
137+
--parameterfile "${parameterFile}" \
138+
--deployer_environment "${deployer_environment}" \
139+
--subscription "${subscriptionId}" \
140+
--spn_id "${spn_id}" \
141+
--spn_secret "${spn_secret}" \
142+
--tenant_id "${tenant_id}" \
143+
--auto-approve
144+
131145
```
132146
# [Windows](#tab/windows)
133147

134-
You can copy the sample configuration files to start testing the deployment automation framework.
135-
136-
```powershell
137-
138-
cd C:\Azure_SAP_Automated_Deployment
139-
140-
xcopy sap-automation\samples\WORKSPACES WORKSPACES
141-
142-
```
143-
144-
145-
```powershell
146-
$subscription="<subscriptionID>"
147-
$spn_id="<appID>"
148-
$spn_secret="<password>"
149-
$tenant_id="<tenant>"
150-
$keyvault=<keyvaultName>
151-
$storageaccount=<storageaccountName>
152-
$statefile_subscription=<statefile_subscription>
153-
$region_code="WEEU"
154-
155-
cd C:\Azure_SAP_Automated_Deployment\WORKSPACES\LANDSCAPE\DEV-$region_code-SAP01-INFRASTRUCTURE
156-
157-
New-SAPWorkloadZone -Parameterfile DEV-$region_code-SAP01-INFRASTRUCTURE.tfvars
158-
-Subscription $subscription -SPN_id $spn_id -SPN_password $spn_secret -Tenant_id $tenant_id
159-
-State_subscription $statefile_subscription -Vault $keyvault -$StorageAccountName $storageaccount
160-
```
161-
148+
It isn't possible to perform the deployment from Windows.
162149
---
163150

164151
> [!NOTE]
@@ -175,7 +162,7 @@ Open (https://dev.azure.com) and go to your Azure DevOps Services project.
175162
> [!NOTE]
176163
> 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'.
177164
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.
179166

180167
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.
181168

0 commit comments

Comments
 (0)