yahoo-eng-team team mailing list archive

[OpenStack Infra <2019217@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/884323
Committed: https://opendev.org/openstack/neutron/commit/413044f253b6d434164e8a94dbeccec7b1b79ebe
Submitter: "Zuul (22348)"
Branch:    master

commit 413044f253b6d434164e8a94dbeccec7b1b79ebe
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Wed May 24 07:15:35 2023 +0200

    [OVN] The L3 scheduler does not use all chassis by default
    
    Any OVN scheduler, inheriting from ``OVNGatewayScheduler``, calls
    ``_schedule_gateway`` to make the decision of in what chassis the
    router gatweway should be located. Before this patch, if the list
    of candidates was empty, the scheduler used all available chassis
    as candidate list. This patch is removing this default behaviour.
    In a deployment, only those chassis marked explicitly with
    "ovn-cms-options=enable-chassis-as-gw" can be used as gateway
    chassis.
    
    After enabling this patch, any existing router gateway port will
    preserve the assigned chassis; any new router gateway will be
    scheduled only on the chassis configured as gateways.
    
    If a router gateway port cannot find any chassis to be scheduled,
    the "neutron-ovn-invalid-chassis" will be used instead and a
    warning message will be printed in the logs.
    
    Closes-Bug: #2019217
    Change-Id: If0f843463edfd7edc5c897cc098de31444f9d81b


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  [OVN] L3 port scheduler, defaults to use all chassis; stop this
  behaviour

Status in neutron:
  Fix Released

Bug description:
  The OVN L3 port scheduler assigns the chassis for the router ports. It
  retrieves the chassis list that are configured as gateway nodes
  (external_ids:ovn-cms-options=enable-chassis-as-gw). This list could
  be also filtered by availability zones; the scheduler will filter out
  those chassis without the requested AZ.

  In case of not returning any chassis ("candidates") [1], the scheduler
  assumes that "any hypervisor/chassis can host a router gateway port"
  (from the patch [2] introducing this functionality).

  The scope of this patch is to revert this default behaviour. If there
  are no candidates available, the L3 scheduler will fail and report the
  issue. The OVN router port won't be scheduled in any chassis. This
  error will be written in the logs.

  [1]https://opendev.org/openstack/neutron/src/commit/47d4ec4e99d5aae62656c88206eb6a77f70d4a8b/neutron/scheduler/l3_ovn_scheduler.py#L63
  [2]https://review.opendev.org/c/openstack/networking-ovn/+/332434

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