yahoo-eng-team team mailing list archive

[Rodolfo Alonso <2018529@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Related bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2190348

Since [1], all ports used as virtual IP ports, as marked as virtual in the OVN NB:
  LSP.type=virtual

A virtual port is used to reserve an IP address in a network. When this
IP address is assigned as "allowed address" to another port, the ML2/OVN
mech driver detects that the virtual port has parents [2] and sets the
port type.

These ports cannot be used as VM ports because of this: these are
virtual ports from OVN point of view. These ports cannot be bound and
are just a representation of this VIP. The OVN SB "Port_Binding"
register (that reflects the type=virtual mark), is assigned to a chassis
by the ovn-controller, when an ARP packet with the VIP crosses a compute
integration bridge. In other words: if many VM ports have this "allowed
address" VIP (as a floating VIP between several ports), the port
transmitting with this IP (can be only one) will claim the chassis.

[1]https://review.opendev.org/c/openstack/neutron/+/842297
[2]https://review.opendev.org/c/openstack/neutron/+/842297/2/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py#251

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

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

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

** Description changed:

+ Related bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2190348
+ 
  Since [1], all ports used as virtual IP ports, as marked as virtual in the OVN NB:
-   LSP.type=virtual
+   LSP.type=virtual
  
  A virtual port is used to reserve an IP address in a network. When this
  IP address is assigned as "allowed address" to another port, the ML2/OVN
  mech driver detects that the virtual port has parents [2] and sets the
  port type.
  
  These ports cannot be used as VM ports because of this: these are
  virtual ports from OVN point of view. These ports cannot be bound and
  are just a representation of this VIP. The OVN SB "Port_Binding"
  register (that reflects the type=virtual mark), is assigned to a chassis
  by the ovn-controller, when an ARP packet with the VIP crosses a compute
  integration bridge. In other words: if many VM ports have this "allowed
  address" VIP (as a floating VIP between several ports), the port
  transmitting with this IP (can be only one) will claim the chassis.
  
  [1]https://review.opendev.org/c/openstack/neutron/+/842297
  [2]https://review.opendev.org/c/openstack/neutron/+/842297/2/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py#251

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

Title:
  [OVN] Virtual ports cannot be used as VM ports

Status in neutron:
  New

Bug description:
  Related bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2190348

  Since [1], all ports used as virtual IP ports, as marked as virtual in the OVN NB:
    LSP.type=virtual

  A virtual port is used to reserve an IP address in a network. When
  this IP address is assigned as "allowed address" to another port, the
  ML2/OVN mech driver detects that the virtual port has parents [2] and
  sets the port type.

  These ports cannot be used as VM ports because of this: these are
  virtual ports from OVN point of view. These ports cannot be bound and
  are just a representation of this VIP. The OVN SB "Port_Binding"
  register (that reflects the type=virtual mark), is assigned to a
  chassis by the ovn-controller, when an ARP packet with the VIP crosses
  a compute integration bridge. In other words: if many VM ports have
  this "allowed address" VIP (as a floating VIP between several ports),
  the port transmitting with this IP (can be only one) will claim the
  chassis.

  [1]https://review.opendev.org/c/openstack/neutron/+/842297
  [2]https://review.opendev.org/c/openstack/neutron/+/842297/2/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py#251

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