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/sap/automation/configure-system.md
+27-10Lines changed: 27 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Define the SAP system properties for SAP Deployment Automation Fram
4
4
author: kimforss
5
5
ms.author: kimforss
6
6
ms.reviewer: kimforss
7
-
ms.date: 10/31/2023
7
+
ms.date: 02/16/2025
8
8
ms.topic: conceptual
9
9
ms.service: sap-on-azure
10
10
ms.subservice: sap-automation
@@ -46,20 +46,31 @@ The distributed (highly available) deployment is similar to the distributed arch
46
46
47
47
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 `application_server_count` >= 1.
48
48
49
+
### HANA Scale-Out
50
+
51
+
The supported configurations for HANA Scale-Out are:
52
+
53
+
- Scale out with Standby node. Requires that HANA shared (single volume), HANA Data and HANA log to be deployed on Azure Netapp Files.
54
+
- Scale out with two sites replicated using HANA System Replication and managed by Pacemaker.
55
+
-
56
+
To configure this topology, define the database tier values and set `database_HANA_use_scaleout_scenario` to true. Set `stand_by_node_count` = to the desired number of standby notes or disable it by setting `database_HANA_no_standby_role` = false.
57
+
58
+
49
59
## Environment parameters
50
60
51
61
This section contains the parameters that define the environment settings.
> |`environment`| Identifier for the workload zone (max five characters) | Mandatory | For example, `PROD` for a production environment and `NP` for a nonproduction environment. |
57
-
> |`location`| The Azure region in which to deploy | Required ||
58
-
> |`custom_prefix`| Specifies the custom prefix used in the resource naming | Optional ||
59
-
> |`use_prefix`| Controls if the resource naming includes the prefix | Optional | DEV-WEEU-SAP01-X00_xxxx |
60
-
> |`name_override_file`| Name override file | Optional | See [Custom naming](naming-module.md). |
61
-
> |`save_naming_information`| Creates a sample naming JSON file | Optional | See [Custom naming](naming-module.md). |
62
-
> |`tags`| A dictionary of tags to associate with all resources. | Optional ||
> |`environment`| Identifier for the workload zone (max five characters) | Mandatory | For example, `PROD` for a production environment and `NP` for a nonproduction environment. |
67
+
> |`location`| The Azure region in which to deploy | Required ||
68
+
> |`custom_prefix`| Specifies the custom prefix used in the resource naming | Optional ||
69
+
> |`use_prefix`| Controls if the resource naming includes the prefix | Optional | DEV-WEEU-SAP01-X00_xxxx |
70
+
> |`name_override_file`| Name override file | Optional | See [Custom naming](naming-module.md). |
71
+
> |`save_naming_information`| Creates a sample naming JSON file | Optional | See [Custom naming](naming-module.md). |
72
+
> |`tags`| A dictionary of tags to associate with all resources. | Optional ||
73
+
> |`prevent_deletion_if_contains_resources`| Controls resource groups deletion. | Optional | Terraform does not by default delete resource groups which contain resources. |
63
74
64
75
## Resource group parameters
65
76
@@ -90,13 +101,19 @@ This section contains the parameters related to the Azure infrastructure.
90
101
> |`use_random_id_for_storageaccounts`| If defined will append a random string to the storage account name | Optional |
91
102
> |`use_scalesets_for_deployment`| Use Flexible Virtual Machine Scale Sets for the deployment | Optional |
92
103
> |`scaleset_id`| Azure resource identifier for the virtual machine scale set | Optional |
104
+
> ||| Optional |
93
105
> |`proximityplacementgroup_arm_ids`| Specifies the Azure resource identifiers of existing proximity placement groups. ||
94
106
> |`proximityplacementgroup_names`| Specifies the names of the proximity placement groups. ||
95
107
> |`use_app_proximityplacementgroups`| Controls if the app tier virtual machines are placed in a different ppg from the database. | Optional |
96
108
> |`app_proximityplacementgroup_arm_ids`| Specifies the Azure resource identifiers of existing proximity placement groups for the app tier. ||
97
109
> |`app_proximityplacementgroup_names`| Specifies the names of the proximity placement groups for the app tier. ||
110
+
> ||| Optional |
98
111
> |`use_spn`| If defined the deployment will be performed using a Service Principal, otherwise an MSI | Optional |
99
112
> |`use_private_endpoint`| Use private endpoints. | Optional |
113
+
> ||| Optional |
114
+
> |`shared_access_key_enabled`| Indicates the storage account authorization type, Shared Access Key or Entra Id | Optional |
115
+
> |`shared_access_key_enabled_nfs`| Indicates the File Share storage account authorization type, Shared Access Key or Entra Id | Optional |
116
+
> |`data_plane_available`| Boolean value indicating if storage account access is via data plane | Optional |
100
117
101
118
102
119
The `resource_offset` parameter controls the naming of resources. For example, if you set the `resource_offset` to 1, the first disk will be named `disk1`. The default value is 0.
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments