770914f98d
This patch introduces a new configuration for OVN CMS Options called "enable-chassis-as-extport-host". This configuration can be used by ML2/OVN to identify nodes that are eligible for scheduling OVN's external ports. Prior to this patch, external ports were always scheduled on centralized networked nodes tagged with the "enable-chassis-as-gw" flag in the OVN CMS Options but, when it comes to deploying OpenStack on OpenShift requiring services such as the OVN Metadata Agent or DHCP Agent to serve those external ports and running them on control plane nodes are not ideal. This is where this patch comes handy allowing these ports to have more flexibility in where they are scheduled. The patch is also backward compatible and if the new configuration is not present on the OVN CMS Options, ML2/OVN will continue to schedule the external ports on nodes configured with the previous configuration like always. Documentation will be updated on a follow up patch. Closes-Bug: 2037294 Change-Id: Ic46d847e3aebfe543d5a7ab49d18d1f1abf1342e Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
15 lines
732 B
YAML
15 lines
732 B
YAML
---
|
|
features:
|
|
- |
|
|
A new ovn-cms-options option called ``enable-chassis-as-extport-host``
|
|
is now recognized by ML2/OVN and is used to identify nodes that are
|
|
eligible for scheduling OVN's external ports. This feature is backward
|
|
compatible and if no nodes contain this new option the external
|
|
ports will continue to be scheduled using the ``enable-chassis-as-gw``
|
|
option as before.
|
|
This change also introduces a limit to the number of members for each
|
|
HA Chassis Group to 5, matching the limit of gateway router port
|
|
replicas. This is because OVN uses BFD to monitor the connectivity
|
|
of each member and having an unlimited number of members could
|
|
potentially put a lot of stress in OVN.
|