Volume back up service per backend

Registered by Navneet on 2014-06-03

The current design for volume backup does not take full advantage of the messaging infrastructure and will site issues going forward in scalability, maintenance and enhancement. New features will be very difficult to be implemented if requires a support in volume backup. The service and manager level functionality is not properly isolated and so manager seems to be handling request routing part which is not required. All the request handling part related to a particular backend is done in the back up manager which ideally should be routed by using the messaging infrastructure. This needs a change in back up manager, service level components to support proper message handling. This spec targets the needed changes.

The cinder spec contains details about problem and approaches to solve it.

Blueprint information

Status:
Complete
Approver:
John Griffith
Priority:
Undefined
Drafter:
Navneet
Direction:
Needs approval
Assignee:
Navneet
Definition:
Superseded
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Navneet on 2014-06-03
Completed by
Sean McGinnis on 2016-03-10

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.