[ovs-dev] [PATCH ovn v6] Expose distributed gateway port information in NB DB

From: Lucas Alvares Gomes In order for the CMS to know which Chassis a distributed gateway port is bond to, this patch updates the ovn-northd daemon to populate the Logical_Router_Port table with that information. A new column called "status" has been added to the Logical_Router_Port table and

[ovs-dev] [PATCH ovn v5] Expose distributed gateway port information in NB DB

From: Lucas Alvares Gomes In order for the CMS to know which Chassis a distributed gateway port is bond to, this patch updates the ovn-northd daemon to populate the Logical_Router_Port table with that information. To avoid changing the database schema, ovn-northd is setting a new key called

[ovs-dev] [PATCH ovn v4] Expose distributed gateway port information in NB DB

From: Lucas Alvares Gomes In order for the CMS to know which Chassis a distributed gateway port is bond to, this patch updates the ovn-northd daemon to populate the Logical_Router_Port table with that information. To avoid changing the database schema, ovn-northd is setting a new key called

[ovs-dev] [PATCH ovn v3] Expose distributed gateway port information in NB DB

From: Lucas Alvares Gomes In order for the CMS to know which Chassis a distributed gateway port is bond to, this patch updates the ovn-northd daemon to populate the Logical_Router_Port table with that information. To avoid changing the database schema, ovn-northd is setting a new key called

[ovs-dev] [PATCH ovn v2] Expose distributed gateway port information in NB DB

From: Lucas Alvares Gomes In order for the CMS to know which Chassis a distributed gateway port is bond to, this patch updates the ovn-northd daemon to populate the Logical_Router_Port table with that information. To avoid changing the database schema, ovn-northd is setting a new key called

[ovs-dev] [PATCH ovn] Expose distributed gateway port information in NB DB

From: Lucas Alvares Gomes In order for the CMS to know which Chassis a distributed gateway port is bond to, this patch updates the ovn-northd daemon to populate the Logical_Router_Port table with that information. To avoid changing the database schema, ovn-northd is setting a new key called

[ovs-dev] [PATCH ovn] Allow for setting the Next server IP in the DHCP header

From: Lucas Alvares Gomes In order to PXE boot a baremetal server using the OVN DHCP server we need to allow users to set the "next-server" (siaddr) [0] field in the DHCP header. While investigating this issue by comparing the DHCPOFFER and DHCPACK packets sent my dnsmasq and OVN we saw that

[ovs-dev] [PATCH ovn] Add support for DHCP options 28 (Broadcast Address)

From: Lucas Alvares Gomes This patch adds support for the DHCP option 28 (Broadcast Address). This options is part of the RFC 2132: https://tools.ietf.org/html/rfc2132 and can be specified by OpenStack users. Signed-off-by: Lucas Alvares Gomes --- lib/ovn-l7.h| 3 +++

[ovs-dev] [PATCH ovn] northd: Add the new chassis's "other_config" column to RBAC

From: Lucas Alvares Gomes This patch is fixing a left-over from commit 74d90c2223d0a8c123823fb849b4c2de58c296e4, we need to add the new "other_config" column from the Chassis table to the rbac_chassis_update list for northd. Co-Authored-by: Numan Siddique Signed-off-by: Numan Siddique

[ovs-dev] [PATCH ovn v3] ovn-controller to no longer monitor Chassis' external_ids

From: Lucas Alvares Gomes Prior to this patch, the external_ids column from the Chassis table were being used for two purposes: 1. Holding configuration for the OVN (copied by ovn-controller from the local OVS database) 2. Holding information from external systems (the main purpose of the

[ovs-dev] [PATCH ovn v2] ovn-controller to no longer monitor Chassis' external_ids

From: Lucas Alvares Gomes Prior to this patch, the external_ids column from the Chassis table were being used for two purposes: 1. Holding configuration for the OVN (copied by ovn-controller from the local OVS database) 2. Holding information from external systems (the main purpose of the

[ovs-dev] [PATCH ovn] ovn-controller to no longer monitor Chassis' external_ids

From: Lucas Alvares Gomes Prior to this patch, the external_ids column from the Chassis table were being used for two purposes: 1. Holding configuration for the OVN (copied by ovn-controller from the local OVS database) 2. Holding information from external systems (the main purpose of the

[ovs-dev] [PATCH ovn v2] Add support for DHCP options 35 and 38

From: Lucas Alvares Gomes This patch is adding support for two new DHCP options: * Option 35, ARP timeout: http://www.networksorcery.com/enp/protocol/bootp/option035.htm * Option 38, TCP Keepalive interval: http://www.networksorcery.com/enp/protocol/bootp/option038.htm I noticed that these

[ovs-dev] [PATCH ovn] Add support for DHCP options 35 and 38

From: Lucas Alvares Gomes This patch is adding support for two new DHCP options: * Option 35, ARP timeout: http://www.networksorcery.com/enp/protocol/bootp/option035.htm * Option 38, TCP Keepalive interval: http://www.networksorcery.com/enp/protocol/bootp/option038.htm I noticed that these

[ovs-dev] [PATCH ovn v2] Avoid nb_cfg update notification flooding

From: Lucas Alvares Gomes nb_cfg as a mechanism to "ping" OVN control plane is very useful in many ways. However, the current implementation will trigger update notifications flooding in the whole control plane. Each HV updates to SB the nb_cfg number and all these updates are notified to all

[ovs-dev] [PATCH ovn] [OVN] Avoid nb_cfg update notification flooding

From: Lucas Alvares Gomes nb_cfg as a mechanism to "ping" OVN control plane is very useful in many ways. However, the current implementation will trigger update notifications flooding in the whole control plane. Each HV updates to SB the nb_cfg number and all these updates are notified to all

[ovs-dev] [PATCH ovn] [RFC] Add chassis liveness monitoring mechanism

From: Lucas Alvares Gomes NOTE: SENDING THIS PATCH AS A RFC TO SEE WHAT OTHERS MIGHT THINK ABOUT THE IDEA PRIOR TO WRITTING TESTS TO IT. CMSes integrating with OVN often uses the nb_cfg mechanism as a way to check the health status of the ovn-controller process but, the current implementation

[ovs-dev] [ovn] OVN split: Remove make "modules_install" target

From: Lucas Alvares Gomes This patch is removing the make "modules_install" target for the new OVN repository. The target is not be needed for OVN (and is currently broken) becasue the kernel modules should be compiled and installed using the OVS repository. Signed-off-by: Lucas Alvares Gomes

[ovs-dev] [[ovn]] OVN split: Fix modules_install

From: Lucas Alvares Gomes The Makefile for modules_install should point to the ovs subrepository to be able to compile the ovs kernel modules (otherwise the compilation fails). Signed-off-by: Lucas Alvares Gomes --- Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[ovs-dev] [PATCH v2] OVN: Enhance ovndb-servers.ocf to handle inactive_probe_interval updates

From: Lucas Alvares Gomes This patch is enhacing the ovndb-servers.ocf script to handle updates to the inactive_probe_interval via pacemaker. For example, one could run: $ sudo crm_resource --resource ovndb_servers --set-parameter inactive_probe_interval --parameter-value To set a new

[ovs-dev] [PATCH] OVN: Enhance ovndb-servers.ocf to handle inactive_probe_interval updates

From: Lucas Alvares Gomes This patch is enhacing the ovndb-servers.ocf script to handle updates to the inactive_probe_interval via pacemaker. For example, one could run: $ sudo crm_resource --resource ovndb_servers --set-parameter inactive_probe_interval --parameter-value To set a new

[ovs-dev] [PATCH] OVN: Clarify docs about the default transport zone

From: Lucas Alvares Gomes This patch is extending the documentation about the new transport zones feature to clarify that if no transport zones are set, the chassis will belong to a default group. Signed-off-by: Lucas Alvares Gomes --- ovn/controller/ovn-controller.8.xml | 16 +++-

[ovs-dev] [PATCH v6] OVN: Add support for Transport Zones

From: Lucas Alvares Gomes This patch is adding support for Transport Zones. Transport zones (a.k.a TZs) is way to enable users of OVN to separate Chassis into different logical groups that will only form tunnels between members of the same groups. Each Chassis can belong to one or more Transport

[ovs-dev] [PATCH v5] OVN: Add support for Transport Zones

From: Lucas Alvares Gomes This patch is adding support for Transport Zones. Transport zones (a.k.a TZs) is way to enable users of OVN to separate Chassis into different logical groups that will only form tunnels between members of the same groups. Each Chassis can belong to one or more Transport

[ovs-dev] [PATCH v4] OVN: Add support for Transport Zones

From: Lucas Alvares Gomes This patch is adding support for Transport Zones. Transport zones (a.k.a TZs) is way to enable users of OVN to separate Chassis into different logical groups that will only form tunnels between members of the same groups. Each Chassis can belong to one or more Transport

[ovs-dev] [PATCH v3] OVN: Add support for Transport Zones

From: Lucas Alvares Gomes This patch is adding support for Transport Zones. Transport zones (a.k.a TZs) is way to enable users of OVN to separate Chassis into different logical groups that will form tunnels only between members of the same group(s). Each Chassis can belong to one or more

[ovs-dev] [PATCH v2] OVN: Add support for Transport Zones

From: Lucas Alvares Gomes This patch is adding support for Transport Zones. Transport zones (a.k.a TZs) is way to enable users of OVN to separate Chassis into different logical groups that will form tunnels only between members of the same group(s). Each Chassis can belong to one or more

[ovs-dev] [PATCH] OVN: Add support for Transport Zones

From: Lucas Alvares Gomes This patch is adding support for Transport Zones. Transport zones (a.k.a TZs) is way to enable users of OVN to separate Chassis into different logical groups that will form tunnels only between members of the same group(s). Each Chassis can belong to one or more

[ovs-dev] [PATCH 2/2] OVN: Add support for DHCP option 150 - TFTP server address

From: Lucas Alvares Gomes OpenStack Ironic relies on a few DHCP options [0] that were not supported in OVN yet. This patch is adding the last one which is the option 150 (TFTP server address, RFC5859 [1]). Note that this option is Cisco proprietary, the IEEE standard that matches with this

[ovs-dev] [PATCH 1/2] OVN: Add support for DHCP option 210 - path prefix

From: Lucas Alvares Gomes OpenStack Ironic relies on few DHCP options [0] that are not yet supported in OVN, one of them is the 210 (PATH PREFIX, RFC5071 [1]). [0] https://github.com/openstack/ironic/blob/3f6d4c6a789b12512d6cc67cdbc93ba5fbf29848/ironic/common/pxe_utils.py#L44-L54 [1]

[ovs-dev] [PATCH branch-2.8 v1] OVN: Add external_ids to NAT and Logical_Router_Static_Route tables.

From: Lucas Alvares Gomes The external_ids column is missing from the NAT and Logical_Router_Static_Route tables. As discussed at [0] the change to the schema for this backport should leave the version number unmodified. [0]

[ovs-dev] [PATCH v1] OVN: Add external_ids to NAT and Logical_Router_Static_Route tables.

From: Lucas Alvares Gomes The external_ids column is missing from the NAT and Logical_Router_Static_Route tables. Signed-off-by: Lucas Alvares Gomes --- ovn/ovn-nb.ovsschema | 14 ++ ovn/ovn-nb.xml | 14 ++ 2 files