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
> |`database_platform`| Defines the database back end | Required ||
167
+
> |`database_vm_image`| Defines the virtual machine image to use | Optional ||
168
+
> |`database_vm_sku`| Defines the virtual machine SKU to use | Optional ||
169
+
> |`database_server_count`| Defines the number of database servers | Optional ||
170
+
> |`database_high_availability`| Defines if the database tier is deployed highly available | Optional ||
171
+
> |`database_vm_zones`| Defines the availability zones for the database servers | Optional ||
172
+
> |`db_sizing_dictionary_key`| Defines the database sizing information | Required | See [Custom sizing](configure-extra-disks.md). |
173
+
> |`database_vm_use_DHCP`| Controls if Azure subnet-provided IP addresses should be used | Optional ||
174
+
> |`database_vm_db_nic_ips`| Defines the IP addresses for the database servers (database subnet) | Optional ||
175
+
> |`database_vm_db_nic_secondary_ips`| Defines the secondary IP addresses for the database servers (database subnet) | Optional ||
176
+
> |`database_vm_admin_nic_ips`| Defines the IP addresses for the database servers (admin subnet) | Optional ||
177
+
> |`database_loadbalancer_ips`| List of IP addresses for the database load balancer (db subnet) | Optional ||
178
+
> |`database_vm_authentication_type`| Defines the authentication type (key/password) | Optional ||
179
+
> |`database_use_avset`| Controls if the database servers are placed in availability sets | Optional ||
180
+
> |`database_use_ppg`| Controls if the database servers are placed in proximity placement groups | Optional ||
181
+
> |`database_vm_avset_arm_ids`| Defines the existing availability sets Azure resource IDs | Optional | Primarily used with Azure NetApp Files pinning. |
182
+
> |`database_use_premium_v2_storage`| Controls if the database tier will use premium storage v2 (HANA) | Optional ||
183
+
> |`database_dual_nics`| Controls if the HANA database servers will have dual network interfaces | Optional ||
184
+
> |`database_tags`| Defines a list of tags to be applied to the database servers | Optional ||
185
+
> |`use_sles_saphanasr_angi`| Defines if SAP HANA SR cluster will be configured with SAP HANA SR - An Next Generation Interface | Optional | Only applicable for SUSE |
185
186
186
187
187
188
@@ -501,6 +502,21 @@ This section contains the Terraform parameters. These parameters need to be ent
501
502
502
503
\* = Required for manual deployments
503
504
505
+
## Scale Out configuration
506
+
507
+
This section contains The configuration setting for the HANA Scale Out configuration
> |`database_HANA_use_scaleout_scenario`| Defines if the HANA database is configured using a Scale Out configuration | Optional |
514
+
> |`database_HANA_no_standby_role`| Defines that the Scale Out tier will not have a standby node | Optional |
515
+
> |`stand_by_node_count`| The number of standby nodes | Optional |
516
+
> |`hanashared_id`| The Azure Resource Identifier for the pre-created HANA Shared resource | Optional |
517
+
> |`hanashared_private_endpoint_id`| The Azure Resource Identifier for the pre-created Private Endpoint | Optional |
518
+
519
+
504
520
## High-availability configuration
505
521
506
522
The high-availability configuration for the database tier and the SCS tier is configured by using the `database_high_availability` and `scs_high_availability` flags. Red Hat and SUSE should use the appropriate HA version of the virtual machine images (RHEL-SAP-HA, sles-sap-15-sp?).
0 commit comments