20f34fc556
Allow Neutron to be configured for use of AZs w/o additional t-h-t services introduced. Limitations for the used NeutronMechanismDrivers: * Right now OVN doesn't support AZ aware routing scheduling (later in Train cycle OVN ml2 driver will be extended to support it). * Nor there is Neutron agents deployed normally for OVN. * We do allow the L3 agent taking AZ configs disregard of the used NeutronMechanismDrivers. * But we take the safe path for the DHCP agent and prohibit AZ configuration for it in the OVN case. So there is effectively nothing applies there for Neutron AZs and OVN as it takes a little to no sense to do that yet. Related blueprint split-controlplane-templates Change-Id: I0d97b004c4f162fdefc97a7b603c0136686fa21c Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
25 lines
1.1 KiB
YAML
25 lines
1.1 KiB
YAML
---
|
|
features:
|
|
- |
|
|
Neutron can be configured for using avaialabiity zones (AZs).
|
|
|
|
.. note:: OVN does not normally run Neutron agents and also has yet support
|
|
for AZ-aware routing scheduling. Therefore, no effective AZ configurations
|
|
can be applied for the network services for the
|
|
``NeutronMechanismDrivers: ovn`` case.
|
|
|
|
`NeutronDefaultAvailabilityZones`, `NeutronDhcpAgentAvailabilityZone`,
|
|
`NeutronL3AgentAvailabilityZone`, `NeutronDhcpAgentsPerNetwork`,
|
|
`NeutronNetworkSchedulerDriver`, `NeutronRouterSchedulerDriver` and
|
|
`NeutronDhcpLoadType` can be used to configure various AZ configurations.
|
|
|
|
By default, `Neutron*AvailabilityZone(s)` takes an empty value, which
|
|
defines no AZs associated with the associated Neutron network service.
|
|
|
|
.. note:: The empty AZ name cannot be re-defined via
|
|
`Neutron*AvailabilityZone(s)` because of the empty value has been
|
|
reserved for another purposes in t-h-t.
|
|
|
|
For details, see
|
|
`Official Documentaion <https://docs.openstack.org/neutron/latest/admin/config-az.html>`_.
|