Bug 1041643

Summary:	[RFE][cinder]: Create conductor service for cinder like nova-conductor
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/cinder/+spec/no-db-volume
Whiteboard:	upstream_milestone_next upstream_status_unknown upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:21:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 18:27:35 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/no-db-volume.

Description:

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

Specification URL (additional information):

None