yahoo-eng-team team mailing list archive

[Rodolfo Alonso <2125569@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The method ``sync_ha_chassis_group_network`` [1] is used to create a
"HA_Chassis_Group" for an external port. If the OVN cluster has chassis
with the "other_config:ovn-cms-options:enable-chassis-as-extport-host"
flag, these chassis are used first to bind the external port. In this
case, the method excludes the local chassis where the VM with the
external port (SR-IOV) is located.

However, if the cluster doesn't have these chassis and only has
"regular" external chassis (those with "other_config:ovn-cms-
options:enable-chassis-as-gw" flag), the method does not exclude the
chassis where the VM is located.

This assumption works almost always because the "regular" external
chassis are networker or controller nodes, not compute nodes. However,
in some scenarios (mostly testing), the same node that hosts the VM with
the external port can also be an external gateway chassis.

This bug proposed to always exclude the local chassis regardless of the
GW chassis list built.

[1]https://github.com/openstack/neutron/blob/e0ca9a0d68fbbcb98820f488accf2f84fb8c9639/neutron/common/ovn/utils.py#L1203-L1233

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

** Changed in: neutron
   Importance: Undecided => 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/2125569

Title:
  [OVN] The method to sync the HA_Chassis_Group should always update the
  "ignore_chassis" variable

Status in neutron:
  New

Bug description:
  The method ``sync_ha_chassis_group_network`` [1] is used to create a
  "HA_Chassis_Group" for an external port. If the OVN cluster has
  chassis with the "other_config:ovn-cms-options:enable-chassis-as-
  extport-host" flag, these chassis are used first to bind the external
  port. In this case, the method excludes the local chassis where the VM
  with the external port (SR-IOV) is located.

  However, if the cluster doesn't have these chassis and only has
  "regular" external chassis (those with "other_config:ovn-cms-
  options:enable-chassis-as-gw" flag), the method does not exclude the
  chassis where the VM is located.

  This assumption works almost always because the "regular" external
  chassis are networker or controller nodes, not compute nodes. However,
  in some scenarios (mostly testing), the same node that hosts the VM
  with the external port can also be an external gateway chassis.

  This bug proposed to always exclude the local chassis regardless of
  the GW chassis list built.

  [1]https://github.com/openstack/neutron/blob/e0ca9a0d68fbbcb98820f488accf2f84fb8c9639/neutron/common/ovn/utils.py#L1203-L1233

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