Support import/export snapshots in cinder

Registered by ling-yun on 2014-08-22

Currently cinder support import/export volume function.
Import/export snapshots function could be an complement for the function of import/export volume.

Functions:
1.It could provide the ability to import volumes' snapshot from one cinder to another cinder,
and import "non" openstack snapshots already on a backend-device into Openstack/cinder.
2. Additionally, export snapshots works the same way as export volumes.

Benifits:
When import volumes that have snapshots, we need to import snapshots.
1. First we could use the import snapshots as volume templates to create volumes.
2. Import snapshots function could provide an effect mean to manage the import volumes.
    For example, we could not delete the import volume that has snapshots.
    By using import snapshots function to import snapshots, we could first delete the import snapshots,
    and then delete the import volumes.

Blueprint information

Status:
Complete
Approver:
Mike Perez
Priority:
Medium
Drafter:
ling-yun
Direction:
Approved
Assignee:
wanghao
Definition:
Approved
Series goal:
Accepted for liberty
Implementation:
Implemented
Milestone target:
milestone icon 7.0.0
Started by
Mike Perez on 2015-01-05
Completed by
John Griffith on 2015-09-01

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/support-import-export-snapshots,n,z

Addressed by: https://review.openstack.org/116599
    Support import/export snapshots in cinder

Addressed by: https://review.openstack.org/144590
    Implement function of import/export snapshots

<jdg> It appears this is implemented, however may need client additions.
For the record, I still think this is a bad idea and should not have been added. At some point just because you "can" do something, doesn't mean you should. There is no valid reason why this extra maintenance and complication is needed or useful.

<wanghao>Thanks John, client will be added in M. IMO, manage/unmange(volume, snapshot, backup) function is important for user to manage their existing and critical resources via openstack. They have some resources already in their storage, and they also want to use openstack, that's the point why we need this kind of function.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.