Bug 1041677

Summary: [RFE][cinder]: Ability to create a volume already present in the storage backend
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/cinder/+spec/ability-to-create-a-volume-already-present-in-the-storage-backend
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:53:34 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:36:42 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/ability-to-create-a-volume-already-present-in-the-storage-backend.

Description:

It would be nice to have the possibility to 'add' a volume instead of creating it, the latest implies a block creation. The purpose of this new command and API implementation is close the glance image-create. With glance, it will go like this:

$ glance image-create --size 2147483648 --name foo --store rbd --disk-format raw --container-format ovf --location rbd://ubuntu-raw

Basically:

As an administrator, I would like to be able to import existing volumes from a storage backend without having to extract them and then re-import them.

From a DB perspective, the operation is just a registration of a new volume nothing less nothing more.

Specification URL (additional information):

None