Public bug reported: The NB BGP driver for the ovn-bgp-agent project [0] is a driver that only connects to the OVN Northbound database and get hosting information for ports using the "requested-chassis" option that is set by Neutron.
For virtual ports, this is not populated upon the port creation because the virtual ports are bound by ovn-controller when an ARP packet with the VIP is seeing in the br-int bridge. Upon seeing the ARP ovn- controller will create a Port_Binding entry in the SB DB which will be seeing by Neutron that will call the set_port_stauts_up() etc..., but, the "requested-chassis" does not get populated at that point either because it's only done during port creation or update. It may be later populated by the maintenance task if the Neutron port gets out of sync tho. We have two problems here: 1. First is that "requested-chassis" should not be populated by Neutron if the port is of type "virtual" because it will be ignored. 2. If not populating it in the "requested-chassis" the NB BGP driver does not have any means to get the hosting information for that port. This LP would suggest that we stop populating the "requested-chassis" options if the port is virtual and instead add the hosting chassis information to the LSP external_ids in case of the virtual ports. [0] https://docs.openstack.org/ovn-bgp- agent/latest/contributor/bgp_supportability_matrix.html#bgp-driver-nb ** Affects: neutron Importance: Medium Assignee: Lucas Alvares Gomes (lucasagomes) Status: Confirmed ** Tags: ovn ** Changed in: neutron Importance: Undecided => Medium ** Changed in: neutron Assignee: (unassigned) => Lucas Alvares Gomes (lucasagomes) ** Changed in: neutron Status: New => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2020058 Title: [OVN][OVN-BGP-AGENT] Expose port hosting information for virtual ports Status in neutron: Confirmed Bug description: The NB BGP driver for the ovn-bgp-agent project [0] is a driver that only connects to the OVN Northbound database and get hosting information for ports using the "requested-chassis" option that is set by Neutron. For virtual ports, this is not populated upon the port creation because the virtual ports are bound by ovn-controller when an ARP packet with the VIP is seeing in the br-int bridge. Upon seeing the ARP ovn-controller will create a Port_Binding entry in the SB DB which will be seeing by Neutron that will call the set_port_stauts_up() etc..., but, the "requested-chassis" does not get populated at that point either because it's only done during port creation or update. It may be later populated by the maintenance task if the Neutron port gets out of sync tho. We have two problems here: 1. First is that "requested-chassis" should not be populated by Neutron if the port is of type "virtual" because it will be ignored. 2. If not populating it in the "requested-chassis" the NB BGP driver does not have any means to get the hosting information for that port. This LP would suggest that we stop populating the "requested-chassis" options if the port is virtual and instead add the hosting chassis information to the LSP external_ids in case of the virtual ports. [0] https://docs.openstack.org/ovn-bgp- agent/latest/contributor/bgp_supportability_matrix.html#bgp-driver-nb To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2020058/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
