Skip to content

Commit 93eed2c

Browse files
committed
Review comments
1 parent 2e53288 commit 93eed2c

7 files changed

+12
-12
lines changed

articles/virtual-machines/workloads/sap/automation-configure-control-plane.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -280,7 +280,7 @@ deployer_vnet="DEP00"
280280
```
281281

282282

283-
## Next step
283+
## Next steps
284284

285285
> [!div class="nextstepaction"]
286286
> [Configure SAP system](automation-configure-system.md)

articles/virtual-machines/workloads/sap/automation-configure-devops.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -190,7 +190,7 @@ The pipelines use a custom task to run Ansible. The custom task can be installed
190190
The pipelines use a custom task to perform cleanup activities post deployment. The custom task can be installed from [Post Build Cleanup](https://marketplace.visualstudio.com/items?itemName=mspremier.PostBuildCleanup). Install it to your Azure DevOps organization before running the pipelines.
191191

192192

193-
## Preparations for Self hosted agent
193+
## Preparations for self-hosted agent
194194

195195

196196
1. Create an Agent Pool by navigating to the Organizational Settings and selecting _Agent Pools_ from the Pipelines section. Click the _Add Pool_ button and choose Self-hosted as the pool type. Name the pool to align with the workload zone environment, for example `DEV-WEEU-POOL`. Ensure _Grant access permission to all pipelines_ is selected and create the pool using the _Create_ button.
@@ -344,4 +344,4 @@ The agent will now be configured and started.
344344
## Next step
345345

346346
> [!div class="nextstepaction"]
347-
> [DevOps Hands on Lab](automation-devops-tutorial.md)
347+
> [DevOps hands on lab](automation-devops-tutorial.md)

articles/virtual-machines/workloads/sap/automation-configure-system.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -393,5 +393,5 @@ az keyvault secret set --name "<prefix>-fencing-spn-tenant" --vault-name "<workl
393393
## Next steps
394394

395395
> [!div class="nextstepaction"]
396-
> [Deploy SAP System](automation-deploy-system.md)
396+
> [Deploy SAP system](automation-deploy-system.md)
397397

articles/virtual-machines/workloads/sap/automation-deploy-control-plane.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -131,11 +131,11 @@ The deployment will use the configuration defined in the Terraform variable file
131131

132132
Run the pipeline by selecting the _Deploy control plane_ pipeline from the Pipelines section. Enter the configuration names for the deployer and the SAP library. Use 'MGMT-WEEU-DEP00-INFRASTRUCTURE' as the Deployer configuration name and 'MGMT-WEEU-SAP_LIBRARY' as the SAP Library configuration name.
133133

134-
:::image type="content" source="media/automation-devops/automation-run-pipeline.png" alt-text="Picture showing the DevOps tutorial run pipeline dialog":::
134+
:::image type="content" source="media/automation-devops/automation-run-pipeline.png" alt-text="Screenshot of Azure DevOps run pipeline dialog.":::
135135

136136
You can track the progress in the Azure DevOps portal. Once the deployment is complete, you can see the Control Plane details in the _Extensions_ tab.
137137

138-
:::image type="content" source="media/automation-devops/automation-run-pipeline-control-plane.png" alt-text="Picture showing the DevOps tutorial run pipeline results":::
138+
:::image type="content" source="media/automation-devops/automation-run-pipeline-control-plane.png" alt-text="Screenshot of the run Azure DevOps pipeline run results.":::
139139

140140
---
141141

articles/virtual-machines/workloads/sap/automation-deploy-system.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ You can track the progress in the Azure DevOps Services portal. Once the deploym
178178

179179
### Output files
180180

181-
The deployment will create a Ansible hosts file (`SID_hosts.yaml`) and an Ansible parameter file (`sap-parameters.yaml`) that are required input for the Ansible playbooks.
181+
The deployment will create an Ansible hosts file (`SID_hosts.yaml`) and an Ansible parameter file (`sap-parameters.yaml`) that are required input for the Ansible playbooks.
182182
## Next steps
183183

184184
> [!div class="nextstepaction"]

articles/virtual-machines/workloads/sap/automation-deploy-workload-zone.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,7 @@ You can track the progress in the Azure DevOps Services portal. Once the deploym
186186
> [!TIP]
187187
> If the scripts fail to run, it can sometimes help to clear the local cache files by removing `~/.sap_deployment_automation/` and `~/.terraform.d/` directories before running the scripts again.
188188
189-
## Next step
189+
## Next steps
190190

191191
> [!div class="nextstepaction"]
192192
> [About SAP system deployment in automation framework](automation-configure-system.md)

articles/virtual-machines/workloads/sap/automation-devops-tutorial.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -78,11 +78,11 @@ Ensure that the 'Deployment_Configuration_Path' variable in the 'SDAF-General' v
7878

7979
Run the pipeline by selecting the _Deploy control plane_ pipeline from the Pipelines section. Enter 'MGMT-WEEU-DEP00-INFRASTRUCTURE' as the Deployer configuration name and 'MGMT-WEEU-SAP_LIBRARY' as the SAP Library configuration name.
8080

81-
:::image type="content" source="media/automation-devops/automation-run-pipeline.png" alt-text="Picture showing the DevOps tutorial run pipeline dialog":::
81+
:::image type="content" source="media/automation-devops/automation-run-pipeline.png" alt-text="Screenshot of the DevOps tutorial run pipeline dialog.":::
8282

8383
You can track the progress in the Azure DevOps Services portal. Once the deployment is complete, you can see the Control Plane details in the _Extensions_ tab.
8484

85-
:::image type="content" source="media/automation-devops/automation-run-pipeline-control-plane.png" alt-text="Picture showing the DevOps tutorial run pipeline results":::
85+
:::image type="content" source="media/automation-devops/automation-run-pipeline-control-plane.png" alt-text="Screenshot of the DevOps run pipeline results.":::
8686

8787

8888
## Deploy the Workload zone
@@ -114,7 +114,7 @@ Run the pipeline by selecting the _Configuration and SAP installation_ pipeline
114114

115115
Choose the playbooks to execute.
116116

117-
:::image type="content" source="media/automation-devops/automation-os-sap.png" alt-text="Picture showing the DevOps tutorial, OS and SAP configuration":::
117+
:::image type="content" source="media/automation-devops/automation-os-sap.png" alt-text="Screenshot showing the DevOps tutorial, OS and SAP configuration.":::
118118

119119
You can track the progress in the Azure DevOps Services portal.
120120

@@ -141,7 +141,7 @@ Enter 'DEV-WEEU-SAP01-INFRASTRUCTURE' as the SAP workload zone configuration nam
141141

142142
Enter 'MGMT-WEEU-DEP00-INFRASTRUCTURE' as the Deployer configuration name and 'MGMT-WEEU-SAP_LIBRARY' as the
143143
SAP Library configuration name.
144-
## Next step
144+
## Next steps
145145

146146
> [!div class="nextstepaction"]
147147
> [Configure Control Plane](automation-configure-control-plane.md)

0 commit comments

Comments
 (0)