Totally Split Data and Control Plane of storage layer

Registered by Shaifali Agrawal on 2015-01-12

Separating data and control layer of storage plane will not only keep the logic separated but also allow users to use different databses for control and data part.

Blueprint information

Status:
Complete
Approver:
Flavio Percoco
Priority:
High
Drafter:
Shaifali Agrawal
Direction:
Needs approval
Assignee:
Shaifali Agrawal
Definition:
Approved
Series goal:
Accepted for kilo
Implementation:
Implemented
Milestone target:
milestone icon 2015.1.0
Started by
Flavio Percoco on 2015-01-12
Completed by
Flavio Percoco on 2015-04-02

Related branches

Sprints

Whiteboard

Following steps are decided to accomplish it:
1. Create separate groups for options: https://git.openstack.org/cgit/openstack/zaqar/tree/zaqar/storage/mongodb/options.py#n93 (see notes here https://etherpad.openstack.org/p/zaqar-scratch )
2. Register control plane options in the new group: https://git.openstack.org/cgit/openstack/zaqar/tree/zaqar/storage/mongodb/driver.py#n183
3. Modify test cases such that all changes made up till now should pass tests properly.
4. Move storage configs of QueueController into Control plane from Data Plane.

Steps 1 to 3 are completed, 4 is on the way.

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

Addressed by: https://review.openstack.org/144340
    Removing QueueController from data to control plane

Gerrit topic: https://review.openstack.org/#q,topic:bp/split-data-and-control-plane,n,z

Addressed by: https://review.openstack.org/168283
    Allow for internal pipelines to be defined

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.