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/virtual-machines/workloads/sap/automation-configure-system.md
+51-51Lines changed: 51 additions & 51 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,8 +15,8 @@ Configuration for the [SAP deployment automation framework on Azure](automation-
15
15
16
16
The automation supports both creating resources (greenfield deployment) or using existing resources (brownfield deployment).
17
17
18
-
For the greenfield scenario the automation defines default names for resources, however some resource names may be defined in the tfvars file.
19
-
For the brownfield scenario the Azure resource identifiers for the resources must be specified.
18
+
For the greenfield scenario, the automation defines default names for resources, however some resource names may be defined in the tfvars file.
19
+
For the brownfield scenario, the Azure resource identifiers for the resources must be specified.
20
20
21
21
22
22
## Deployment topologies
@@ -31,21 +31,21 @@ The automation framework can be used to deploy the following SAP architectures:
31
31
32
32
In the Standalone architecture all the SAP roles are installed on a single server.
33
33
34
-
To configure this topology define the database tier values and set `enable_app_tier_deployment` to false.
34
+
To configure this topology, define the database tier values and set `enable_app_tier_deployment` to false.
35
35
36
36
### Distributed
37
37
38
-
In the distributed architecture you can separate the database server and the application tier. The application tier can further be separated in two by having SAP Central Services on a virtual machine and one or more application servers.
39
-
To configure this topology define the database tier values and define `scs_server_count` = 1, `application_server_count` >= 1
38
+
The distributed architecture has a separate database server and application tier. The application tier can further be separated by having SAP Central Services on a virtual machine and one or more application servers.
39
+
To configure this topology, define the database tier values and define `scs_server_count` = 1, `application_server_count` >= 1
40
40
41
41
### High Availability
42
42
43
43
The Distributed (Highly Available) deployment is similar to the Distributed architecture but either the database or SAP Central Services are both highly available using two virtual machines each with Pacemaker clusters.
44
44
45
-
To configure this topology define the database tier values and set `database_high_availability` to true. Set `scs_server_count = 1` and `scs_high_availability` = true and
45
+
To configure this topology, define the database tier values and set `database_high_availability` to true. Set `scs_server_count = 1` and `scs_high_availability` = true and
46
46
`application_server_count` >= 1
47
47
48
-
## Environment Parameters
48
+
## Environment parameters
49
49
50
50
The table below contains the parameters that define the environment settings and the resource naming.
51
51
@@ -60,7 +60,7 @@ The table below contains the parameters that define the environment settings and
60
60
> | 'name_override_file' | Name override file | Optional |
61
61
62
62
63
-
## Resource Group Parameters
63
+
## Resource group parameters
64
64
65
65
The table below contains the parameters that define the resource group.
66
66
@@ -72,7 +72,7 @@ The table below contains the parameters that define the resource group.
72
72
> |`resource_group_arm_id`| Azure resource identifier for an existing resource group | Optional |
73
73
74
74
75
-
### Database Tier Parameters
75
+
### Database tier parameters
76
76
77
77
The database tier defines the infrastructure for the database tier, supported database backends are:
78
78
@@ -118,7 +118,7 @@ The Virtual Machine and the operating system image is defined using the followin
118
118
}
119
119
```
120
120
121
-
### Common Application Tier Parameters
121
+
### Common application tier parameters
122
122
123
123
The application tier defines the infrastructure for the application tier, which can consist of application servers, central services servers and web dispatch servers
124
124
@@ -134,7 +134,7 @@ The application tier defines the infrastructure for the application tier, which
134
134
> |`app_tier_use_DHCP`| Controls if Azure subnet provided IP addresses should be used (dynamic) | Optional ||
135
135
> |`app_tier_dual_nics`| Defines if the application tier server will have two network interfaces | Optional ||
136
136
137
-
### SAP Central Services Parameters
137
+
### SAP Central services parameters
138
138
139
139
140
140
> [!div class="mx-tdCol2BreakAll "]
@@ -154,7 +154,7 @@ The application tier defines the infrastructure for the application tier, which
154
154
> |`scs_server_no_avset`| Controls scs server availability set placement | Optional ||
155
155
> |`scs_server_tags`| Defines a list of tags to be applied to the scs servers | Optional ||
156
156
157
-
### Application Server Parameters
157
+
### Application server parameters
158
158
159
159
160
160
> [!div class="mx-tdCol2BreakAll "]
@@ -170,7 +170,7 @@ The application tier defines the infrastructure for the application tier, which
170
170
> |`application_server_no_avset`| Controls application server availability set placement | Optional ||
171
171
> |`application_server_tags`| Defines a list of tags to be applied to the application servers | Optional ||
172
172
173
-
### Web Dispatcher Parameters
173
+
### Web dispatcher parameters
174
174
175
175
176
176
> [!div class="mx-tdCol2BreakAll "]
@@ -186,50 +186,50 @@ The application tier defines the infrastructure for the application tier, which
186
186
> |`webdispatcher_server_no_avset`| Defines web dispatcher availability set placement | Optional ||
187
187
> |`webdispatcher_server_tags`| Defines a list of tags to be applied to the web dispatcher servers | Optional ||
188
188
189
-
## Network Parameters
189
+
## Network parameters
190
190
191
191
If the subnets are not deployed using the workload zone deployment, they can be added in the system's tfvars file.
192
192
193
-
The automation framework supports both creating the virtual network and the subnets for new environment deployments (Green field) or using an existing virtual network and existing subnets for existing environment deployments (Brown field) or a combination of for new environment deployments and for existing environment deployments.
194
-
- For the green field scenario, the virtual network address space and the subnet address prefixes must be specified
195
-
- For the brown field scenario, the Azure resource identifier for the virtual network and the subnets must be specified
193
+
The automation framework can either deploy the virtual network and the subnets for new environment deployments (greenfield) or using an existing virtual network and existing subnets for existing environment deployments (brownfield).
194
+
- For the greenfield scenario, the virtual network address space and the subnet address prefixes must be specified
195
+
- For the brownfield scenario, the Azure resource identifier for the virtual network and the subnets must be specified
196
196
197
-
Ensure that the virtual network address space is large enough to host all the resources
197
+
Ensure that the virtual network address space is large enough to host all the resources.
198
198
199
199
The table below contains the networking parameters.
> |`network_logical_name`| The logical name of the network| Required ||
206
-
> |`network_address_space`| The address range for the virtual network| Mandatory | For new environment deployments |
207
-
> |`admin_subnet_name`| The name of the 'admin' subnet| Optional ||
208
-
> |`admin_subnet_address_prefix`| The address range for the 'admin' subnet| Mandatory | For new environment deployments |
209
-
> |`admin_subnet_arm_id`| The Azure resource identifier for the 'admin' subnet| Mandatory | For existing environment deployments |
210
-
> |`admin_subnet_nsg_name`| The name of the 'admin' Network Security Group name| Optional ||
205
+
> |`network_logical_name`| The logical name of the network.| Required ||
206
+
> |`network_address_space`| The address range for the virtual network.| Mandatory | For new environment deployments |
207
+
> |`admin_subnet_name`| The name of the 'admin' subnet.| Optional ||
208
+
> |`admin_subnet_address_prefix`| The address range for the 'admin' subnet.| Mandatory | For new environment deployments |
209
+
> |`admin_subnet_arm_id`| The Azure resource identifier for the 'admin' subnet.| Mandatory | For existing environment deployments |
210
+
> |`admin_subnet_nsg_name`| The name of the 'admin' Network Security Group name.| Optional ||
211
211
> |`admin_subnet_nsg_arm_id`| The Azure resource identifier for the 'admin' Network Security Group | Mandatory | For existing environment deployments |
212
-
> |`db_subnet_name`| The name of the 'db' subnet| Optional ||
213
-
> |`db_subnet_address_prefix`| The address range for the 'db' subnet| Mandatory | For new environment deployments |
214
-
> |`db_subnet_arm_id`| The Azure resource identifier for the 'db' subnet| Mandatory | For existing environment deployments |
215
-
> |`db_subnet_nsg_name`| The name of the 'db' Network Security Group name| Optional ||
216
-
> |`db_subnet_nsg_arm_id`| The Azure resource identifier for the 'db' Network Security Group| Mandatory | For existing environment deployments |
217
-
> |`app_subnet_name`| The name of the 'app' subnet| Optional ||
218
-
> |`app_subnet_address_prefix`| The address range for the 'app' subnet| Mandatory | For new environment deployments |
219
-
> |`app_subnet_arm_id`| The Azure resource identifier for the 'app' subnet| Mandatory | For existing environment deployments |
220
-
> |`app_subnet_nsg_name`| The name of the 'app' Network Security Group name| Optional ||
221
-
> |`app_subnet_nsg_arm_id`| The Azure resource identifier for the 'app' Network Security Group| Mandatory | For existing environment deployments |
222
-
> |`web_subnet_name`| The name of the 'web' subnet| Optional ||
223
-
> |`web_subnet_address_prefix`| The address range for the 'web' subnet| Mandatory | For new environment deployments |
224
-
> |`web_subnet_arm_id`| The Azure resource identifier for the 'web' subnet| Mandatory | For existing environment deployments |
225
-
> |`web_subnet_nsg_name`| The name of the 'web' Network Security Group name| Optional ||
226
-
> |`web_subnet_nsg_arm_id`| The Azure resource identifier for the 'web' Network Security Group| Mandatory | For existing environment deployments |
227
-
228
-
\* = Required for for existing environment deployments deployments
229
-
230
-
### Anchor Virtual Machine Parameters
231
-
232
-
The SAP deployment automation framework supports having an Anchor Virtual Machine. The anchor Virtual machine will be the first virtual machine to be deployed and is used to anchor the proximity placement group.
212
+
> |`db_subnet_name`| The name of the 'db' subnet.| Optional ||
213
+
> |`db_subnet_address_prefix`| The address range for the 'db' subnet.| Mandatory | For new environment deployments |
214
+
> |`db_subnet_arm_id`| The Azure resource identifier for the 'db' subnet.| Mandatory | For existing environment deployments |
215
+
> |`db_subnet_nsg_name`| The name of the 'db' Network Security Group name.| Optional ||
216
+
> |`db_subnet_nsg_arm_id`| The Azure resource identifier for the 'db' Network Security Group.| Mandatory | For existing environment deployments |
217
+
> |`app_subnet_name`| The name of the 'app' subnet.| Optional ||
218
+
> |`app_subnet_address_prefix`| The address range for the 'app' subnet.| Mandatory | For new environment deployments |
219
+
> |`app_subnet_arm_id`| The Azure resource identifier for the 'app' subnet.| Mandatory | For existing environment deployments |
220
+
> |`app_subnet_nsg_name`| The name of the 'app' Network Security Group name.| Optional ||
221
+
> |`app_subnet_nsg_arm_id`| The Azure resource identifier for the 'app' Network Security Group.| Mandatory | For existing environment deployments |
222
+
> |`web_subnet_name`| The name of the 'web' subnet.| Optional ||
223
+
> |`web_subnet_address_prefix`| The address range for the 'web' subnet.| Mandatory | For new environment deployments |
224
+
> |`web_subnet_arm_id`| The Azure resource identifier for the 'web' subnet.| Mandatory | For existing environment deployments |
225
+
> |`web_subnet_nsg_name`| The name of the 'web' Network Security Group name.| Optional ||
226
+
> |`web_subnet_nsg_arm_id`| The Azure resource identifier for the 'web' Network Security Group.| Mandatory | For existing environment deployments |
227
+
228
+
\* = Required for existing environment deployments
229
+
230
+
### Anchor virtual machine parameters
231
+
232
+
The SAP deployment automation framework supports having an Anchor virtual machine. The anchor virtual machine will be the first virtual machine to be deployed and is used to anchor the proximity placement group.
233
233
234
234
The table below contains the parameters related to the anchor virtual machine.
235
235
@@ -256,7 +256,7 @@ version="latest"
256
256
}
257
257
```
258
258
259
-
### Authentication Parameters
259
+
### Authentication parameters
260
260
261
261
By default the SAP System deployment uses the credentials from the SAP Workload zone. If the SAP system needs unique credentials, you can provide them using these parameters.
262
262
@@ -269,7 +269,7 @@ By default the SAP System deployment uses the credentials from the SAP Workload
269
269
> |`automation_path_to_private_key`| Path to existing private key | Optional |
270
270
271
271
272
-
## Other Parameters
272
+
## Other parameters
273
273
274
274
275
275
> [!div class="mx-tdCol2BreakAll "]
@@ -282,23 +282,23 @@ By default the SAP System deployment uses the credentials from the SAP Workload
282
282
> |`use_zonal_markers`| Specifies if zonal Virtual Machines will include a zonal identifier. 'xooscs_z1_00l###' vs 'xooscs00l###'| Default value is true. |
> |`azure_files_storage_account_id`| If provided the Azure resource ID of the storage account for Azure Files | Optional |
300
300
301
-
## Terraform Parameters
301
+
## Terraform parameters
302
302
303
303
The table below contains the Terraform parameters, these parameters need to be entered manually if not using the deployment scripts.
304
304
@@ -316,7 +316,7 @@ The table below contains the Terraform parameters, these parameters need to be
316
316
317
317
The high availability configuration for the database tier and the SCS tier is configured using the `database_high_availability` and `scs_high_availability` flags.
318
318
319
-
High availability configurations use Pacemaker with Azure fencing agents. The fencing agents should be configured to use a unique service principal with permissions to stop and start virtual machines. For more information see [Create Fencing Agent](high-availability-guide-suse-pacemaker.md#create-an-azure-fence-agent-stonith-device)
319
+
High availability configurations use Pacemaker with Azure fencing agents. The fencing agents should be configured to use a unique service principal with permissions to stop and start virtual machines. For more information, see [Create Fencing Agent](high-availability-guide-suse-pacemaker.md#create-an-azure-fence-agent-stonith-device)
320
320
321
321
```azurecli-interactive
322
322
az ad sp create-for-rbac --role="Linux Fence Agent Role" --scopes="/subscriptions/<subscriptionID>" --name="<prefix>-Fencing-Agent"
0 commit comments