schedule gateway router ports on chassis having external connectivity

Bug #1705246 reported by venkata anil
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-ovn
Fix Released
Undecided
venkata anil

Bug Description

Currently ovn schedules gateway router ports on all chassis. Instead we need to check which chassis has external connectivity and schedule them only on these chassis. Chassis which has ovn-bridge-mappings properly configured in OVN_Southbound database will be treated as having external connectivity.

Revision history for this message
venkata anil (anil-venkata) wrote :
Changed in networking-ovn:
assignee: nobody → venkata anil (anil-venkata)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (master)

Reviewed: https://review.openstack.org/485176
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=14d8e70cfae41fed5e9515dddda714b54a3c67bf
Submitter: Jenkins
Branch: master

commit 14d8e70cfae41fed5e9515dddda714b54a3c67bf
Author: venkata anil <email address hidden>
Date: Wed Aug 9 17:58:47 2017 +0000

    schedule gateway on chassis with external connectivity

    Currently ovn schedules gateway router ports on all chassis.
    Instead we need to check which chassis has external connectivity
    and schedule them only on these chassis.

    Chassis which has ovn-bridge-mappings properly configured(i.e
    physnet same as gateway network physnet) in OVN_Southbound
    database will be treated as having external connectivity.
    Some network types(for example, geneve) may not use bridge
    mappings. Currently, external networks of type VLAN and FLAT
    use bridge mappings. So for these networks, we return chassis
    with proper bridge mappings and for other networks we return
    all chassis.

    Closes-bug: #1705246
    Change-Id: I73970aef6d84019032e3c68a6a785d7626ae2afc

Changed in networking-ovn:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 4.0.0.0b1

This issue was fixed in the openstack/networking-ovn 4.0.0.0b1 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-ovn (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/526475

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (stable/pike)

Reviewed: https://review.openstack.org/526475
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=8ea2203e3ff592c521748dff5ded9eca864b48d8
Submitter: Zuul
Branch: stable/pike

commit 8ea2203e3ff592c521748dff5ded9eca864b48d8
Author: Daniel Alvarez <email address hidden>
Date: Sat Dec 9 12:25:08 2017 +0000

    schedule gateway on chassis with external connectivity

    Currently ovn schedules gateway router ports on all chassis.
    Instead we need to check which chassis has external connectivity
    and schedule them only on these chassis.

    Chassis which has ovn-bridge-mappings properly configured(i.e
    physnet same as gateway network physnet) in OVN_Southbound
    database will be treated as having external connectivity.
    Some network types(for example, geneve) may not use bridge
    mappings. Currently, external networks of type VLAN and FLAT
    use bridge mappings. So for these networks, we return chassis
    with proper bridge mappings and for other networks we return
    all chassis.

    Conflicts:
        networking_ovn/common/ovn_client.py
        networking_ovn/l3/l3_ovn.py
        networking_ovn/ovsdb/impl_idl_ovn.py
        networking_ovn/tests/functional/test_router.py

    Closes-bug: #1705246
    Change-Id: I73970aef6d84019032e3c68a6a785d7626ae2afc
    (cherry picked from commit 14d8e70cfae41fed5e9515dddda714b54a3c67bf)

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 3.0.1

This issue was fixed in the openstack/networking-ovn 3.0.1 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.