Chapter 3. Role-Based Parameters
You can modify the bevavior of specific overcloud composable roles with overcloud role-based parameters. Substitute _ROLE_ with the name of the role. For example, for _ROLE_Count
use ControllerCount
.
Parameter | Description |
---|---|
|
Sets the |
|
Name of the subnet on ctlplane network for this role. The default value is |
|
The number of nodes to deploy in a role. The default value is |
| Role specific additional hiera configuration to inject into the cluster. |
| Optional extra Ansible group vars. |
|
Format for node hostnames. Note that |
|
Sets the |
| OpenStack Orchestration (heat) action when to apply network configuration changes. |
| Optional Role Specific parameters to be provided to service. |
|
List of resources to be removed from the role’s |
|
How to handle change to RemovalPolicies for ROLE ResourceGroup when doing an update. Default mode append will append to the existing blocklist and update would replace the blocklist. The default value is |
| Optional scheduler hints to pass to OpenStack Compute (nova). |
| Role specific ServiceNetMap overrides, the map provided will be merged with the global ServiceNetMap when passing the ServiceNetMap to the ROLE_ServiceChain resource and the _ROLE resource group. For example: _ROLE_ServiceNetMap: NovaLibvirtNetwork: internal_api_leaf2. |
| A list of service resources (configured in the OpenStack Orchestration (heat) resource_registry) which represent nested stacks for each service that should get installed on the ROLE role. |