Bug 1041790

Summary: [RFE][glance]: A framework for contributred storage systems.
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/glance/+spec/framework-for-contributed-storage-systems
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_new
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:57:31 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 19:20:02 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/framework-for-contributed-storage-systems.

Description:

At times contributors wish to add storage drivers to Glance.  No matter how good the code is when it enters there is always a concern of potential bit-rot.  We also must concern ourselves with all of the dependencies related to a new storage driver.

Further, those wishing to use different storage system backends must wait until a patch is reviewed, then approved, then released.

It would benefit the community if we were to have a framework for adding storage drivers, as their own packages, to a glance deploy.  While I beleive that this is possible today, I think that it would be better if we had an contrib section in glance where various storage drivers were added.  These drivers would be part of the glance code base, but not installed by default.  This would serve two purposes, it would thin out a default/basic deploy and it would serve as an example of how to create a storage driver package.

Specification URL (additional information):

None