Skip to content

Commit f3eb0e9

Browse files
prmerger-automator[bot]prmerger-automator[bot]
authored
Merge pull request #235354 from KimForss/main
App tier parameter updates
2 parents 8bb1a87 + 8f1f5a2 commit f3eb0e9

File tree

1 file changed

+37
-36
lines changed

1 file changed

+37
-36
lines changed

‎articles/sap/automation/configure-system.md

Lines changed: 37 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Define the SAP system properties for the SAP on Azure Deployment Au
44
author: kimforss
55
ms.author: kimforss
66
ms.reviewer: kimforss
7-
ms.date: 05/03/2022
7+
ms.date: 04/21/2023
88
ms.topic: conceptual
99
ms.service: sap-on-azure
1010
ms.subservice: sap-automation
@@ -13,7 +13,7 @@ ms.custom: devx-track-terraform
1313

1414
# Configure SAP system parameters
1515

16-
Configuration for the [SAP on Azure Deployment Automation Framework](deployment-framework.md)] happens through parameters files. You provide information about your SAP system properties in a tfvars file, which the automation framework uses for deployment. You can find examples of the variable file in the 'samples/WORKSPACES/SYSTEM' folder.
16+
Configuration for the [SAP on Azure Deployment Automation Framework](deployment-framework.md)] happens through parameters files. You provide information about your SAP system infrastructure in a tfvars file, which the automation framework uses for deployment. You can find examples of the variable file in the 'samples' repository.
1717

1818
The automation supports both creating resources (green field deployment) or using existing resources (brownfield deployment).
1919

@@ -43,7 +43,7 @@ To configure this topology, define the database tier values and define `scs_serv
4343

4444
### High Availability
4545

46-
The Distributed (Highly Available) deployment is similar to the Distributed architecture. In this deployment, the database and/or SAP Central Services can both be configured using a highly available configuration using two virtual machines each with Pacemaker clusters.
46+
The Distributed (Highly Available) deployment is similar to the Distributed architecture. In this deployment, the database and/or SAP Central Services can both be configured using a highly available configuration using two virtual machines each with Pacemaker clusters or in case of Windows with Windows Failover clustering.
4747

4848
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
4949
`application_server_count` >= 1
@@ -116,7 +116,7 @@ The database tier defines the infrastructure for the database tier, supported da
116116
> | `database_vm_image` | Defines the Virtual machine image to use, see below. | Optional | |
117117
> | `database_vm_authentication_type` | Defines the authentication type (key/password). | Optional | |
118118
> | `database_use_avset` | Controls if the database servers are placed in availability sets. | Optional | default is false |
119-
> | `database_use_ppg` | Controls if the database servers will be placed in a proximity placement groups. | Optional | default is true |
119+
> | `database_use_ppg` | Controls if the database servers will be placed in proximity placement groups. | Optional | default is true |
120120
> | `database_vm_avset_arm_ids` | Defines the existing availability sets Azure resource IDs. | Optional | Primarily used with ANF pinning |
121121
> | `hana_dual_nics` | Controls if the HANA database servers will have dual network interfaces. | Optional | default is true |
122122
@@ -154,22 +154,22 @@ The application tier defines the infrastructure for the application tier, which
154154

155155

156156
> [!div class="mx-tdCol2BreakAll "]
157-
> | Variable | Description | Type | Notes |
158-
> | -------------------------------------- | -------------------------------------------------------------------- | ----------| ------ |
159-
> | `scs_server_count` | Defines the number of SCS servers. | Required | |
160-
> | `scs_high_availability` | Defines if the Central Services is highly available. | Optional | See [High availability configuration](configure-system.md#high-availability-configuration) |
161-
> | `scs_instance_number` | The instance number of SCS. | Optional | |
162-
> | `ers_instance_number` | The instance number of ERS. | Optional | |
163-
> | `scs_server_sku` | Defines the Virtual machine SKU to use. | Optional | |
164-
> | `scs_server_image` | Defines the Virtual machine image to use. | Required | |
165-
> | `scs_server_zones` | Defines the availability zones of the SCS servers. | Optional | |
166-
> | `scs_server_app_nic_ips` | List of IP addresses for the SCS servers (app subnet). | Optional | |
167-
> | `scs_server_app_nic_secondary_ips[]` | List of secondary IP addresses for the SCS servers (app subnet). | Optional | |
168-
> | `scs_server_app_admin_nic_ips` | List of IP addresses for the SCS servers (admin subnet). | Optional | |
169-
> | `scs_server_loadbalancer_ips` | List of IP addresses for the scs load balancer (app subnet). | Optional | |
170-
> | `scs_server_no_ppg` | Controls SCS server proximity placement group. | Optional | |
171-
> | `scs_server_no_avset` | Controls SCS server availability set placement. | Optional | |
172-
> | `scs_server_tags` | Defines a list of tags to be applied to the SCS servers. | Optional | |
157+
> | Variable | Description | Type | Notes |
158+
> | -------------------------------------- | ------------------------------------------------------------------------ | ----------| ------ |
159+
> | `scs_server_count` | Defines the number of SCS servers. | Required | |
160+
> | `scs_high_availability` | Defines if the Central Services is highly available. | Optional | See [High availability configuration](configure-system.md#high-availability-configuration) |
161+
> | `scs_instance_number` | The instance number of SCS. | Optional | |
162+
> | `ers_instance_number` | The instance number of ERS. | Optional | |
163+
> | `scs_server_sku` | Defines the Virtual machine SKU to use. | Optional | |
164+
> | `scs_server_image` | Defines the Virtual machine image to use. | Required | |
165+
> | `scs_server_zones` | Defines the availability zones of the SCS servers. | Optional | |
166+
> | `scs_server_app_nic_ips` | List of IP addresses for the SCS servers (app subnet). | Optional | |
167+
> | `scs_server_app_nic_secondary_ips[]` | List of secondary IP addresses for the SCS servers (app subnet). | Optional | |
168+
> | `scs_server_app_admin_nic_ips` | List of IP addresses for the SCS servers (admin subnet). | Optional | |
169+
> | `scs_server_loadbalancer_ips` | List of IP addresses for the scs load balancer (app subnet). | Optional | |
170+
> | `scs_server_use_ppg` | Controls if the SCS servers are placed in availability sets. | Optional | |
171+
> | `scs_server_use_avset` | Controls if the SCS servers will be placed in proximity placement groups.| Optional | |
172+
> | `scs_server_tags` | Defines a list of tags to be applied to the SCS servers. | Optional | |
173173
174174
### Application server parameters
175175

@@ -180,13 +180,13 @@ The application tier defines the infrastructure for the application tier, which
180180
> | `application_server_count` | Defines the number of application servers. | Required | |
181181
> | `application_server_sku` | Defines the Virtual machine SKU to use. | Optional | |
182182
> | `application_server_image` | Defines the Virtual machine image to use. | Required | |
183-
> | `application_server_zones` | Defines the availability zones to which the application servers are deployed. | Optional | |
184-
> | `application_server_app_nic_ips[]` | List of IP addresses for the application servers (app subnet). | Optional | |
185-
> | `application_server_nic_secondary_ips[]` | List of secondary IP addresses for the application servers (app subnet). | Optional | |
186-
> | `application_server_app_admin_nic_ips` | List of IP addresses for the application server (admin subnet). | Optional | |
187-
> | `application_server_no_ppg` | Controls application server proximity placement group. | Optional | |
188-
> | `application_server_no_avset` | Controls application server availability set placement. | Optional | |
189-
> | `application_server_tags` | Defines a list of tags to be applied to the application servers. | Optional | |
183+
> | `application_server_zones` | Defines the availability zones to which the application servers are deployed.| Optional | |
184+
> | `application_server_app_nic_ips[]` | List of IP addresses for the application servers (app subnet). | Optional | |
185+
> | `application_server_nic_secondary_ips[]` | List of secondary IP addresses for the application servers (app subnet). | Optional | |
186+
> | `application_server_app_admin_nic_ips` | List of IP addresses for the application server (admin subnet). | Optional | |
187+
> | `application_server_use_ppg` | Controls if application servers are placed in availability sets. | Optional | |
188+
> | `application_server_use_avset` | Controls if application servers will be placed in proximity placement | Optional | |
189+
> | `application_server_tags` | Defines a list of tags to be applied to the application servers. | Optional | |
190190
191191
### Web dispatcher parameters
192192

@@ -201,8 +201,8 @@ The application tier defines the infrastructure for the application tier, which
201201
> | `webdispatcher_server_app_nic_ips[]` | List of IP addresses for the web dispatcher server (app/web subnet). | Optional | |
202202
> | `webdispatcher_server_nic_secondary_ips[]` | List of secondary IP addresses for the web dispatcher server (app/web subnet). | Optional | |
203203
> | `webdispatcher_server_app_admin_nic_ips` | List of IP addresses for the web dispatcher server (admin subnet). | Optional | |
204-
> | `webdispatcher_server_no_ppg` | Controls web proximity placement group placement. | Optional | |
205-
> | `webdispatcher_server_no_avset` | Defines web dispatcher availability set placement. | Optional | |
204+
> | `webdispatcher_server_use_ppg` | Controls if web dispatchers are placed in availability sets. | Optional | |
205+
> | `webdispatcher_server_use_avset` | Controls if web dispatchers will be placed in proximity placement | Optional | |
206206
> | `webdispatcher_server_tags` | Defines a list of tags to be applied to the web dispatcher servers. | Optional | |
207207
208208
## Network parameters
@@ -222,7 +222,7 @@ The table below contains the networking parameters.
222222
> | Variable | Description | Type | Notes |
223223
> | -------------------------------- | -------------------------------------------------------------------- | --------- | ---------------------------- |
224224
> | `network_logical_name` | The logical name of the network. | Required | |
225-
> | | | Optional | |
225+
> | | | | |
226226
> | `admin_subnet_name` | The name of the 'admin' subnet. | Optional | |
227227
> | `admin_subnet_address_prefix` | The address range for the 'admin' subnet. | Mandatory | For green field deployments. |
228228
> | `admin_subnet_arm_id` * | The Azure resource identifier for the 'admin' subnet. | Mandatory | For brown field deployments. |
@@ -283,12 +283,13 @@ The table below contains the parameters related to the anchor virtual machine.
283283
The Virtual Machine and the operating system image is defined using the following structure:
284284
```python
285285
{
286-
os_type="linux"
287-
source_image_id=""
288-
publisher="SUSE"
289-
offer="sles-sap-15-sp3"
290-
sku="gen2"
291-
version="latest"
286+
os_type = "linux"
287+
type = "marketplace"
288+
source_image_id = ""
289+
publisher = "SUSE"
290+
offer = "sles-sap-15-sp3"
291+
sku = "gen2"
292+
version= " latest"
292293
}
293294
```
294295

0 commit comments

Comments
 (0)