networking-ovn

  1. Bug #1605089
  2. Comment #37

Comment 37 for bug 1605089

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to networking-ovn (master)

Reviewed: https://review.openstack.org/464221
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=9d8b07a7b5d5dbe9a76573d611117beede6875f9
Submitter: Jenkins
Branch: master

commit 9d8b07a7b5d5dbe9a76573d611117beede6875f9
Author: Lucas Alvares Gomes <email address hidden>
Date: Wed May 10 14:51:10 2017 +0100

    Add OVNClient for Ports and L3 resources

    Right now we have code doing CRUD operations on ONV resources spread
    around different places (ml2/mech_driver.py, l3/l3_ovn.py), this makes
    things very complicated to implement something like journaling (see
    bug: #1605089) where all resources, L2 and L3, are created from a
    central place (the journal thread, which keeps things in order).

    This patch is adding a new class called OVNClient which centralizes all
    the CRUD operations for the OVN resources in one place.

    For this first iteraction, the Port resource from the mechanism driver
    and the L3 resources (floating ip, routers and routers ports) are being
    moved to this new class, others will come in follow up patches.

    Related-Bug: #1605089
    Change-Id: Ia453a14cdc2ec393037fb813caff8fae23acd7c3