Seperate Publish-Subscribe Module for DB Changes

Registered by Gal Sagie

The idea is to allow separate publish-subscribe mechanism then the DB framework used.
The controller would sync and read the DB, but receive update notifications and DB changes using the pub-sub mechanism.

This will allow implementing pub-sub even for DB's that dont support it and also be able to optimize this process
for scale and performance unrelated to the backend DB solution

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
Gal Sagie
Direction:
Approved
Assignee:
Eran Gampel
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Omer Anson
Completed by
Omer Anson

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/pubsub-module,n,z

Addressed by: https://review.openstack.org/260573
    Add publish subscribe module installation

Addressed by: https://review.openstack.org/260971
    Add pub-sub abstraction to Dragonflow

Addressed by: https://review.openstack.org/263733
    Add publish-subscribe abstraction spec

Gerrit topic: https://review.openstack.org/#q,topic:pub-sub,n,z

Addressed by: https://review.openstack.org/263322
    Add support for DF built-in pub/sub

Gerrit topic: https://review.openstack.org/#q,topic:pubsub,n,z

Gerrit topic: https://review.openstack.org/#q,topic:pub/sub,n,z

Gerrit topic: https://review.openstack.org/#q,topic:pubsub_spec,n,z

Addressed by: https://review.openstack.org/278884
    Add support for DF built-in Pluggable pub/sub

Gerrit topic: https://review.openstack.org/#q,topic:pub-sub-spec,n,z

Gerrit topic: https://review.openstack.org/#q,topic:pub_sub_spec,n,z

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.