Create conductor service for cinder like nova-conductor
In Grizzly nova-conductor has been implemented in nova. It'll be great to implement something like this in cinder.
Problem:
Cinder-volume has direct access to cinder-db
Solution:
Move all db requests out from cinder-volume
Steps of implementation:
*Create conductor-manager to handle db requests
*Create conductor-api and conductor-rpcapi
*Rewrite cinder-api to use new conductor service
Blueprint information
- Status:
- Complete
- Approver:
- John Griffith
- Priority:
- Low
- Drafter:
- Nikolay Starodubtsev
- Direction:
- Approved
- Assignee:
- Nikolay Starodubtsev
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
-
next
- Started by
- Completed by
- Sean McGinnis
Related branches
Related bugs
Sprints
Whiteboard
(smcginnis): Marking obsolete as this has been sitting out there for a long time. If this is still needed, please submit a new bp.
<jdg>:
My apologies Nikolay, it would seem I was moving too quickly when cleaning out the proposals.
I'm interested of course in hearing more about what problem you're trying to solve and what your plans thoughts are here. Also how you intend for this to tie in with things like states and task-flow.
Sorry again if you took this as "not interested" etc, in the future feel free to contact me via IRC email or updating notes on the whiteboard here. None of us are perfect and things can get lost from time time.
<jdg>:
It looks like this hasn't been active, I've removed it from H3 target however if there's actually work being done and this is ready I'm happy to add it back in, but as I've received no updates and haven't heard anything about it I'm assuming that it may not be in scope for Havana.
<ns>:
Sorry, John. I was switched to another project before I did something that I can show. I forgot to notice it here. I will return to this work as soon as my other project will end.
<thingee>:
What does this solve by moving it out of cinder-volume?
