Need DB sync mechanism between DB and Neutron DB

Bug #1527234 reported by Gal Sagie on 2015-12-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gal Sagie

Bug Description

We need to define a mechanism to sync between Neutron DB and our Dragonflow pluggable DB.
Some DB's dont support persistent saving of data (like RAMCloud) and hence wont work after a restart (unless a cluster is used)

This needs to be documented at least or solved completely with a sync process.

For etcd we need to keep the data on a disk file and not in RAM

Gal Sagie (gal-sagie) on 2015-12-17
Changed in dragonflow:
assignee: nobody → Gal Sagie (gal-sagie)
Gal Sagie (gal-sagie) on 2015-12-29
Changed in dragonflow:
importance: Undecided → Medium

Submitter: Jenkins
Branch: master

commit 3b92dc8eac33ad96b6cd40ad80427c9951444d99
Author: Li Ma <email address hidden>
Date: Thu Feb 18 10:30:42 2016 +0800

    Implement DB consistency

    It is a distributed lock based on SQL. Each lock is
    associated with a Neutron project(tenant) and a given
    API session. It ensures that a lock is acquired and
    released in the same API context.

    The detailed description is in the spec review.

    Closes-Bug: #1529812
    Closes-Bug: #1529326
    Closes-Bug: #1497676
    Related-Bug: #1527234
    Implements: blueprint bp/keep-db-consistency

    Change-Id: Iff916481282f2d60df66c0e916f3045f9944531e

Yuli (stremovsky) wrote :

DB consistency fixed this issue.

Changed in dragonflow:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers