Skip to content

Commit bea7ca2

Browse files
paulth1paulth1
committed
edit pass: sap-automation-batch1
1 parent 8403a51 commit bea7ca2

File tree

1 file changed

+37
-37
lines changed

1 file changed

+37
-37
lines changed

‎articles/sap/automation/configure-control-plane.md

Lines changed: 37 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -44,8 +44,8 @@ This table shows the parameters that define the resource naming.
4444
> | ------------------------------- | ------------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------- |
4545
> | `environment` | Identifier for the control plane (maximum of five characters). | Mandatory | For example, `PROD` for a production environment and `NP` for a nonproduction environment. |
4646
> | `location` | Azure region in which to deploy. | Required | Use lowercase. |
47-
> | 'name_override_file' | Name override file. | Optional | See [Custom naming](naming-module.md). |
48-
> | 'place_delete_lock_on_resources | Place a delete lock on the key resources. | Optional |
47+
> | `name_override_file` | Name override file. | Optional | See [Custom naming](naming-module.md). |
48+
> | `place_delete_lock_on_resources` | Place a delete lock on the key resources. | Optional |
4949
5050
### Resource group
5151

@@ -60,10 +60,10 @@ This table shows the parameters that define the resource group.
6060
6161
### Network parameters
6262

63-
The automation framework supports both creating the virtual network and the subnets (green field) or using an existing virtual network and existing subnets (brown field) or a combination of green field and brown field.
63+
The automation framework supports both creating the virtual network and the subnets (green field) or using an existing virtual network and existing subnets (brown field) or a combination of green field and brown field:
6464

65-
- For the green-field scenario, the virtual network address space and the subnet address prefixes must be specified.
66-
- For the brown-field scenario, the Azure resource identifier for the virtual network and the subnets must be specified.
65+
- **Green-field scenario**: The virtual network address space and the subnet address prefixes must be specified.
66+
- **Brown-field scenario**: The Azure resource identifier for the virtual network and the subnets must be specified.
6767

6868
The recommended CIDR of the virtual network address space is /27, which allows space for 32 IP addresses. A CIDR value of /28 only allows 16 IP addresses. If you want to include Azure Firewall, use a CIDR value of /25, because Azure Firewall requires a range of /26.
6969

@@ -75,26 +75,26 @@ This table shows the networking parameters.
7575
> [!div class="mx-tdCol2BreakAll "]
7676
> | Variable | Description | Type | Notes |
7777
> | ------------------------------------------ | ---------------------------------------------------------------- | ---------- | ------ |
78-
> | `management_network_name` | The name of the virtual network into which the deployer will be deployed. | Optional | For green-field deployments |
79-
> | `management_network_logical_name` | The logical name of the network (DEV-WEEU-MGMT01-INFRASTRUCTURE). | Required | |
80-
> | `management_network_arm_id` | The Azure resource identifier for the virtual network. | Optional | For brown-field deployments |
81-
> | `management_network_address_space` | The address range for the virtual network. | Mandatory | For green-field deployments |
78+
> | `management_network_name` | The name of the virtual network into which the deployer will be deployed | Optional | For green-field deployments |
79+
> | `management_network_logical_name` | The logical name of the network (DEV-WEEU-MGMT01-INFRASTRUCTURE) | Required | |
80+
> | `management_network_arm_id` | The Azure resource identifier for the virtual network | Optional | For brown-field deployments |
81+
> | `management_network_address_space` | The address range for the virtual network | Mandatory | For green-field deployments |
8282
> | | | | |
83-
> | `management_subnet_name` | The name of the subnet. | Optional | |
84-
> | `management_subnet_address_prefix` | The address range for the subnet. | Mandatory | For green-field deployments |
85-
> | `management_subnet_arm_id` | The Azure resource identifier for the subnet. | Mandatory | For brown-field deployments |
86-
> | `management_subnet_nsg_name` | The name of the network security group. | Optional | |
87-
> | `management_subnet_nsg_arm_id` | The Azure resource identifier for the network security group. | Mandatory | For brown-field deployments |
88-
> | `management_subnet_nsg_allowed_ips` | Range of allowed IP addresses to add to Azure Firewall. | Optional | |
83+
> | `management_subnet_name` | The name of the subnet | Optional | |
84+
> | `management_subnet_address_prefix` | The address range for the subnet | Mandatory | For green-field deployments |
85+
> | `management_subnet_arm_id` | The Azure resource identifier for the subnet | Mandatory | For brown-field deployments |
86+
> | `management_subnet_nsg_name` | The name of the network security group | Optional | |
87+
> | `management_subnet_nsg_arm_id` | The Azure resource identifier for the network security group | Mandatory | For brown-field deployments |
88+
> | `management_subnet_nsg_allowed_ips` | Range of allowed IP addresses to add to Azure Firewall | Optional | |
8989
> | | | | |
90-
> | `management_firewall_subnet_arm_id` | The Azure resource identifier for the Azure Firewall subnet. | Mandatory | For brown-field deployments |
91-
> | `management_firewall_subnet_address_prefix` | The address range for the subnet. | Mandatory | For green-field deployments |
90+
> | `management_firewall_subnet_arm_id` | The Azure resource identifier for the Azure Firewall subnet | Mandatory | For brown-field deployments |
91+
> | `management_firewall_subnet_address_prefix` | The address range for the subnet | Mandatory | For green-field deployments |
9292
> | | | | |
93-
> | `management_bastion_subnet_arm_id` | The Azure resource identifier for the Azure Bastion subnet. | Mandatory | For brown-field deployments |
94-
> | `management_bastion_subnet_address_prefix` | The address range for the subnet. | Mandatory | For green-field deployments |
93+
> | `management_bastion_subnet_arm_id` | The Azure resource identifier for the Azure Bastion subnet | Mandatory | For brown-field deployments |
94+
> | `management_bastion_subnet_address_prefix` | The address range for the subnet | Mandatory | For green-field deployments |
9595
> | | | | |
96-
> | `webapp_subnet_arm_id` | The Azure resource identifier for the web app subnet. | Mandatory | For brown-field deployments by using the web app |
97-
> | `webapp_subnet_address_prefix` | The address range for the subnet. | Mandatory | For green-field deployments by using the web app |
96+
> | `webapp_subnet_arm_id` | The Azure resource identifier for the web app subnet | Mandatory | For brown-field deployments by using the web app |
97+
> | `webapp_subnet_address_prefix` | The address range for the subnet | Mandatory | For green-field deployments by using the web app |
9898
9999
> [!NOTE]
100100
> When you use an existing subnet for the web app, the subnet must be empty, in the same region as the resource group being deployed, and delegated to Microsoft.Web/serverFarms.
@@ -106,16 +106,16 @@ This table shows the parameters related to the deployer VM.
106106
> [!div class="mx-tdCol2BreakAll "]
107107
> | Variable | Description | Type |
108108
> | ------------------------------- | -------------------------------------------------------------------------------------- | ---------- |
109-
> | `deployer_size` | Defines the VM SKU to use, for example, Standard_D4s_v3. | Optional |
110-
> | `deployer_count` | Defines the number of deployers. | Optional |
111-
> | `deployer_image` | Defines the VM image to use. | Optional |
112-
> | `plan` | Defines the plan associated to the VM image. | Optional |
113-
> | `deployer_disk_type` | Defines the disk type, for example, Premium_LRS. | Optional |
114-
> | `deployer_use_DHCP` | Controls if the Azure subnet-provided IP addresses should be used (dynamic) true. | Optional |
115-
> | `deployer_private_ip_address` | Defines the private IP address to use. | Optional |
116-
> | `deployer_enable_public_ip` | Defines if the deployer has a public IP. | Optional |
117-
> | `auto_configure_deployer` | Defines if the deployer is configured with the required software (Terraform and Ansible). | Optional |
118-
> | `add_system_assigned_identity` | Defines if the deployer is assigned a system identity. | Optional |
109+
> | `deployer_size` | Defines the VM SKU to use, for example, Standard_D4s_v3 | Optional |
110+
> | `deployer_count` | Defines the number of deployers | Optional |
111+
> | `deployer_image` | Defines the VM image to use | Optional |
112+
> | `plan` | Defines the plan associated to the VM image | Optional |
113+
> | `deployer_disk_type` | Defines the disk type, for example, Premium_LRS | Optional |
114+
> | `deployer_use_DHCP` | Controls if the Azure subnet-provided IP addresses should be used (dynamic) true | Optional |
115+
> | `deployer_private_ip_address` | Defines the private IP address to use | Optional |
116+
> | `deployer_enable_public_ip` | Defines if the deployer has a public IP | Optional |
117+
> | `auto_configure_deployer` | Defines if the deployer is configured with the required software (Terraform and Ansible) | Optional |
118+
> | `add_system_assigned_identity` | Defines if the deployer is assigned a system identity | Optional |
119119
120120
The VM image is defined by using the following structure:
121121

@@ -142,11 +142,11 @@ This section defines the parameters used for defining the VM authentication.
142142
> [!div class="mx-tdCol2BreakAll "]
143143
> | Variable | Description | Type |
144144
> | ------------------------------------------------ | --------------------------------------------------- | --------- |
145-
> | `deployer_vm_authentication_type` | Defines the default authentication for the deployer. | Optional |
146-
> | `deployer_authentication_username` | Administrator account name. | Optional |
147-
> | `deployer_authentication_password` | Administrator password. | Optional |
148-
> | `deployer_authentication_path_to_public_key` | Path to the public key used for authentication. | Optional |
149-
> | `deployer_authentication_path_to_private_key` | Path to the private key used for authentication. | Optional |
145+
> | `deployer_vm_authentication_type` | Defines the default authentication for the deployer | Optional |
146+
> | `deployer_authentication_username` | Administrator account name | Optional |
147+
> | `deployer_authentication_password` | Administrator password | Optional |
148+
> | `deployer_authentication_path_to_public_key` | Path to the public key used for authentication | Optional |
149+
> | `deployer_authentication_path_to_private_key` | Path to the private key used for authentication | Optional |
150150
151151
### Key vault parameters
152152

@@ -240,7 +240,7 @@ This table shows the parameters that define the resource naming.
240240
> | ----------------------- | ------------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------- |
241241
> | `environment` | Identifier for the control plane (maximum of five characters) | Mandatory | For example, `PROD` for a production environment and `NP` for a nonproduction environment. |
242242
> | `location` | Azure region in which to deploy | Required | Use lowercase. |
243-
> | 'name_override_file' | Name override file | Optional | See [Custom naming](naming-module.md). |
243+
> | `name_override_file` | Name override file | Optional | See [Custom naming](naming-module.md). |
244244
245245
### Resource group
246246

0 commit comments

Comments
 (0)