yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1959125@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In LP#1821058, a new parameter was defined for each mechanism driver,
the "connectivity". That provides a way to define what type of driver
is. For example, SRIOV, Linux Bridge, OVS or OVN are "l2" drivers.
Calico is "l3" only. The default value is "legacy".

In [1], a check for ports without IP addresses. Those kind of ports can
only be bound to "l2" drivers.

In [2] I changed the "vif_details" dictionary to populated the two sub-
dicts under "ovs" and "vhostuser". The problem is that check [1] cannot
be done because the "connectivity" parameter in not a key in
"vif_details" anymore.

A more robust way to check the mech driver connectivity must be
implemented, rather that adding it to a dictionary, "vif_details", that
has not a defined structure.

NOTE: this is currently breaking heat-tempest-plugin CI master job.

[1]https://review.opendev.org/c/openstack/neutron/+/678027
[2]https://review.opendev.org/c/openstack/neutron/+/814143

** Affects: neutron
     Importance: Medium
     Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
         Status: New

** Description changed:

  In LP#1821058, a new parameter was defined for each mechanism driver,
  the "connectivity". That provides a way to define what type of driver
  is. For example, SRIOV, Linux Bridge, OVS or OVN are "l2" drivers.
  Calico is "l3" only. The default value is "legacy".
  
  In [1], a check for ports without IP addresses. Those kind of ports can
  only be bound to "l2" drivers.
  
  In [2] I changed the "vif_details" dictionary to populated the two sub-
  dicts under "ovs" and "vhostuser". The problem is that check [1] cannot
  be done because the "connectivity" parameter in not a key in
  "vif_details" anymore.
  
  A more robust way to check the mech driver connectivity must be
  implemented, rather that adding it to a dictionary, "vif_details", that
  has not a defined structure.
  
+ NOTE: this is currently breaking heat-tempest-plugin CI master job.
  
  [1]https://review.opendev.org/c/openstack/neutron/+/678027
  [2]https://review.opendev.org/c/openstack/neutron/+/814143

** Changed in: neutron
   Importance: Undecided => Critical

** Changed in: neutron
   Importance: Critical => Medium

** Changed in: neutron
     Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1959125

Title:
  OVN mech driver failing to check the L2/L3 connectivity

Status in neutron:
  New

Bug description:
  In LP#1821058, a new parameter was defined for each mechanism driver,
  the "connectivity". That provides a way to define what type of driver
  is. For example, SRIOV, Linux Bridge, OVS or OVN are "l2" drivers.
  Calico is "l3" only. The default value is "legacy".

  In [1], a check for ports without IP addresses. Those kind of ports
  can only be bound to "l2" drivers.

  In [2] I changed the "vif_details" dictionary to populated the two
  sub-dicts under "ovs" and "vhostuser". The problem is that check [1]
  cannot be done because the "connectivity" parameter in not a key in
  "vif_details" anymore.

  A more robust way to check the mech driver connectivity must be
  implemented, rather that adding it to a dictionary, "vif_details",
  that has not a defined structure.

  NOTE: this is currently breaking heat-tempest-plugin CI master job.

  [1]https://review.opendev.org/c/openstack/neutron/+/678027
  [2]https://review.opendev.org/c/openstack/neutron/+/814143

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1959125/+subscriptions