Skip to content

Commit 20f627a

Browse files
authored
Merge pull request #180291 from KimForss/kimforss-url-update2
Repo URL updates
2 parents 1bbb663 + 80ca369 commit 20f627a

File tree

3 files changed

+39
-41
lines changed

3 files changed

+39
-41
lines changed

articles/virtual-machines/workloads/sap/automation-manual-deployment.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -84,18 +84,18 @@ Download Terraform to your environment:
8484
8585
## Set up repository
8686
87-
Clone and configure the [automation framework repository](https://github.com/Azure/sap-hana).
87+
Clone and configure the [automation framework repository](https://github.com/Azure/sap-automation).
8888
8989
1. Clone the repository from GitHub:
9090
9191
```azurecli-interactive
92-
git clone https://github.com/Azure/sap-hana.git
92+
git clone https://github.com/Azure/sap-automation.git
9393
```
9494
95-
1. Navigate to the `sap-hana` folder.
95+
1. Navigate to the `sap-automation` folder.
9696
9797
```azurecli-interactive
98-
cd ~/Azure_SAP_Automated_Deployment/sap-hana
98+
cd ~/Azure_SAP_Automated_Deployment/sap-automation
9999
```
100100
101101
1. Optionally, check out a different branch than the main branch. The main branch for the repository is the default.
@@ -152,23 +152,23 @@ Clone and configure the [automation framework repository](https://github.com/Azu
152152
1. Initialize Terraform.
153153
154154
```azurecli-interactive
155-
terraform init ../../../sap-hana/deploy/terraform/bootstrap/sap_deployer/
155+
terraform init ../../../sap-automation/deploy/terraform/bootstrap/sap_deployer/
156156
```
157157
158158
1. Create a Terraform execution plan that follows the default naming convention.
159159
160160
```azurecli-interactive
161161
terraform plan \
162162
--var-file=DEMO-EUS2-DEP00-INFRASTRUCTURE.json \
163-
../../../sap-hana/deploy/terraform/bootstrap/sap_deployer/
163+
../../../sap-automation/deploy/terraform/bootstrap/sap_deployer/
164164
```
165165
166166
1. Apply your Terraform execution plan to deploy the resources.
167167
168168
```azurecli-interactive
169169
terraform apply --auto-approve \
170170
--var-file=DEMO-EUS2-DEP00-INFRASTRUCTURE.json \
171-
../../../sap-hana/deploy/terraform/bootstrap/sap_deployer/
171+
../../../sap-automation/deploy/terraform/bootstrap/sap_deployer/
172172
```
173173
174174
1. Note the output.
@@ -261,7 +261,7 @@ The deployer uses a service principal to deploy resources into a subscription.
261261
1. Navigate to where you cloned the automation framework repository.
262262
263263
```bash
264-
cd ~/Azure_SAP_Automated_Deployment/sap-hana
264+
cd ~/Azure_SAP_Automated_Deployment/sap-automation
265265
```
266266
267267
1. Optionally, check out a different branch than the main branch. The main branch for the repository is the default.

articles/virtual-machines/workloads/sap/automation-plan-deployment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ For your own parameter files, it's a best practice to keep these files in a sour
6767
6868
### Folder structure
6969
70-
The following sample folder hierarchy shows how to structure your configuration files along with the automation framework files. The first top-level folder, called **sap-hana**, has the automation framework files that you don't need to change in most use cases. The second top-level folder, called **WORKSPACES**, contains subfolders with configuration files for your deployment settings.
70+
The following sample folder hierarchy shows how to structure your configuration files along with the automation framework files. The first top-level folder, called **sap-automation**, has the automation framework files that you don't need to change in most use cases. The second top-level folder, called **WORKSPACES**, contains subfolders with configuration files for your deployment settings.
7171
7272
| Folder name | Contents | Description |
7373
| ----------- | -------- | ----------- |

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

Lines changed: 30 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: virtual-machines-sap
1212
# Enterprise Scale for SAP Automation Framework Deployment - Hands-on Lab
1313

1414

15-
This tutorial shows how to do enterprise scaling for deployments using the [SAP deployment automation framework on Azure](automation-deployment-framework.md). This example uses Azure Cloud Shell to deploy the control plane infrastructure. The deployer virtual machine (VM) creates the remaining infrastructure and SAP HANA configurations. There's a feature-locked branch in the [GitHub repository for the automation framework](https://github.com/Azure/sap-hana/), named `sap-level-up`, for use with this tutorial.
15+
This tutorial shows how to do enterprise scaling for deployments using the [SAP deployment automation framework on Azure](automation-deployment-framework.md). This example uses Azure Cloud Shell to deploy the control plane infrastructure. The deployer virtual machine (VM) creates the remaining infrastructure and SAP HANA configurations.
1616

1717
During this lab, you will perform the following tasks
1818

@@ -37,7 +37,7 @@ There are three main steps of an SAP deployment on Azure with the automation fra
3737

3838
3. Deploying the system. This step includes the infrastructure for the SAP system.
3939

40-
There are several workflows in the deployment automation process. However, this tutorial focuses on one workflow for ease of deployment. You can deploy this workflow, the SAP-S4HANA standalone environment, using Bash. The tutorial describes the general hierarchy and different phases of the deployment.
40+
There are several workflows in the deployment automation process. However, this tutorial focuses on one workflow for ease of deployment. You can deploy this workflow, the SAP S4 HANA standalone environment, using Bash. The tutorial describes the general hierarchy and different phases of the deployment.
4141
### Environment Overview
4242

4343
The SAP on Azure deployment automation framework has two main components:
@@ -79,7 +79,7 @@ The system deployment consists of the virtual machines that will be running the
7979

8080
### Prerequisites
8181

82-
The [SAP deployment automation framework repository](https://github.com/Azure/sap-hana) is available on GitHub.
82+
The [SAP deployment automation framework repository](https://github.com/Azure/sap-automation) is available on GitHub.
8383

8484
> [!IMPORTANT]
8585
> Before you begin, make sure to change from the default branch to **sap-level-up**.
@@ -120,7 +120,7 @@ az account list --query "[?isDefault]"
120120
**or**
121121

122122
```cloudshell-interactive
123-
az account list -o table | grep True
123+
az account list -o table | grep True
124124
```
125125

126126
Create the deployment folder and clone the repository.
@@ -130,16 +130,15 @@ mkdir -p ~/Azure_SAP_Automated_Deployment
130130
131131
cd ~/Azure_SAP_Automated_Deployment
132132
133-
git clone https://github.com/Azure/sap-hana.git \
134-
--single-branch --branch=sap-level-up
133+
git clone https://github.com/Azure/sap-automation.git
135134
136-
cd ~/Azure_SAP_Automated_Deployment/sap-hana
135+
cd ~/Azure_SAP_Automated_Deployment/sap-automation
137136
```
138137

139138
Optionally, validate the version of Terraform, and the Azure Command-Line Interface (Azure CLI) available on your instance of the Cloud Shell.
140139

141140
```bash
142-
./util/check_workstation.sh
141+
deploy/scripts/check_workstation.sh
143142
```
144143

145144
To run the automation framework, update to the following versions.
@@ -148,7 +147,6 @@ To run the automation framework, update to the following versions.
148147

149148
1. `terraform` version 1.0.8 or higher. [Upgrade using the Terraform instructions](https://www.terraform.io/upgrade-guides/0-12.html) as necessary.
150149

151-
152150
## Create service principal
153151

154152
The SAP automation deployment framework uses service principals for deployment. Create a service principal for your control plane deployment as follows. Make sure to use an account with permissions to create service principals.
@@ -171,7 +169,7 @@ Review the output. For example:
171169
{
172170
"appId": "<AppID>",
173171
"displayName": "<environment>-Deployment-Account ",
174-
"name": "<AppID>,
172+
"name": "<AppID>",
175173
"password": "<AppSecret>",
176174
"tenant": "<Tenant ID>"
177175
}
@@ -204,7 +202,7 @@ Copy the sample configurations to a local workspace directory:
204202
```bash
205203
cd ~/Azure_SAP_Automated_Deployment
206204

207-
cp -Rp ./sap-hana/deploy/samples/WORKSPACES ./
205+
cp -Rp ./sap-automation/training_materials/WORKSPACES ./
208206
```
209207

210208
Open VS Code from Cloud Shell
@@ -266,12 +264,12 @@ The sample SAP Library configuration file `MGMT-NOEU-SAP_LIBRARY.tfvars` is in t
266264
```bash
267265
cd ~/Azure_SAP_Automated_Deployment/WORKSPACES
268266

269-
subscriptionID=<subscriptionID>
270-
appId=<appID>
271-
spn_secret="<password>"
272-
tenant_id=<tenant>
267+
export subscriptionID=<subscriptionID>
268+
export appId=<appID>
269+
export spn_secret="<password>"
270+
export tenant_id=<tenant>
273271

274-
export DEPLOYMENT_REPO_PATH="${HOME}/Azure_SAP_Automated_Deployment/sap-hana"
272+
export DEPLOYMENT_REPO_PATH="${HOME}/Azure_SAP_Automated_Deployment/sap-automation"
275273
export ARM_SUBSCRIPTION_ID="${subscriptionID}"
276274

277275
${DEPLOYMENT_REPO_PATH}/deploy/scripts/prepare_region.sh \
@@ -373,7 +371,7 @@ A sample extract of a BOM file looks like:
373371
```yaml
374372

375373
---
376-
name: 'S41909SPS03_v0005ms'
374+
name: 'S41909SPS03_v0006ms'
377375
target: 'S/4 HANA 1909 SPS 03'
378376
version: 6
379377

@@ -443,7 +441,7 @@ kv_name: MGMTNOEUDEP00user99F
443441
Execute the Ansible playbooks. One way you can execute the playbooks is to use the validator test menu. Run the validator test menu script.
444442

445443
```bash
446-
~/Azure_SAP_Automated_Deployment/sap-hana/deploy/ansible/validator_test_menu.sh
444+
~/Azure_SAP_Automated_Deployment/sap-automation/deploy/ansible/validator_test_menu.sh
447445
```
448446

449447
Select which playbooks to execute.
@@ -484,20 +482,20 @@ Go into the *Azure_SAP_Automated_Deployment* folder in your home directory. Remo
484482
rm -rf WORKSPACES
485483
```
486484

487-
Go to the **sap-hana** folder. Check out the **sap-level-up** branch.
485+
Go to the **sap-automation** folder.
488486

489487
```bash
490-
cd ~/Azure_SAP_Automated_Deployment/sap-hana/
488+
cd ~/Azure_SAP_Automated_Deployment/sap-automation/
491489
492-
git checkout sap-level-up
490+
git pull
493491
```
494492

495493
Copy the sample configuration files from the repository.
496494

497495
```bash
498496
cd ~/Azure_SAP_Automated_Deployment/
499497
500-
cp -Rp ./sap-hana/deploy/samples/WORKSPACES ./
498+
cp -Rp ./sap-automation/training_materials/WORKSPACES ./
501499
```
502500

503501
## Deploy the Workload Zone
@@ -529,20 +527,20 @@ Start deployment of the workload zone:
529527
```bash
530528
cd ~/Azure_SAP_Automated_Deployment/WORKSPACES/LANDSCAPE/DEV-NOEU-SAP01-INFRASTRUCTURE
531529
532-
subscriptionID=<subscriptionID>
533-
appId=<appID>
534-
spn_secret="<password>"
535-
tenant_id=<tenant>
536-
storageaccount=<storageaccountName>
537-
statefile_subscription=<subscriptionID>
530+
export subscriptionID=<subscriptionID>
531+
export appId=<appID>
532+
export spn_secret="<password>"
533+
export tenant_id=<tenant>
534+
export storage_account=<storageaccountName>
535+
export statefile_subscription=<subscriptionID>
538536
key_vault=<vaultID>
539537
540538
${DEPLOYMENT_REPO_PATH}/deploy/scripts/install_workloadzone.sh \
541539
--parameterfile ./DEV-NOEU-SAP01-INFRASTRUCTURE.tfvars \
542540
--deployer_environment MGMT \
543541
--deployer_tfstate_key MGMT-NOEU-DEP00-INFRASTRUCTURE.terraform.tfstate \
544542
--keyvault $key_vault \
545-
--storageaccountname $storageaccount \
543+
--storageaccountname $storage_account \
546544
--state_subscription $statefile_subscription \
547545
--subscription $subscriptionID \
548546
--spn_id $appID \
@@ -557,7 +555,7 @@ Wait for the deployment to finish. The new resource group appears in the Azure p
557555
## Deploy SAP system infrastructure
558556

559557
Once the Workload zone is complete, you can deploy the SAP system infrastructure resources. The SAP system creates your VMs and supporting components for your SAP application.
560-
Use the [installler.sh](bash/automation-installer.md) script to deploy the SAP system.
558+
Use the [installer.sh](bash/automation-installer.md) script to deploy the SAP system.
561559

562560
The SAP system deploys:
563561

@@ -583,7 +581,7 @@ The deployment command for the `northeurope` example will look like:
583581
cd ~/Azure_SAP_Automated_Deployment/WORKSPACES/SYSTEM/DEV-NOEU-SAP01-X00
584582
585583
${DEPLOYMENT_REPO_PATH}/deploy/scripts/installer.sh \
586-
--parameter_file DEV-NOEU-SAP01-X00.tfvars \
584+
--parameterfile DEV-NOEU-SAP01-X00.tfvars \
587585
--type sap_system \
588586
--auto-approve
589587
```
@@ -697,7 +695,7 @@ cd ~/Azure_SAP_Automated_Deployment/WORKSPACES/
697695
Export the following two environment variables.
698696

699697
```bash
700-
export DEPLOYMENT_REPO_PATH=~/Azure_SAP_Automated_Deployment/sap-hana
698+
export DEPLOYMENT_REPO_PATH=~/Azure_SAP_Automated_Deployment/sap-automation
701699
702700
export ARM_SUBSCRIPTION_ID=<subscriptionID>
703701
```

0 commit comments

Comments
 (0)