Provide an option to backup only root volume while snapshotting a volume backed instance

Registered by Souvik Basu on 2013-07-22

Currently, creating a snapshot of an instance which is volume-backed will backup the root volume as well as all the other volumes attached to it.

This feature is to provide the user with the option to backup only the root volume excluding any other volume attached to it. Introduce a query param, backup_only_root_volume, which when set to true, backs up only the root volume, if false, all the volumes will be backed up. This will be a feature for volume-backed instances only.

Blueprint information

Status:
Started
Approver:
Russell Bryant
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Aditi Raveesh
Definition:
Drafting
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Aditi Raveesh on 2013-12-23

Related branches

Sprints

Whiteboard

Deferred to icehouse-3 as the blueprint was not approved by the icehouse-2 blueprint approval deadline. --russellb

Gerrit topic: https://review.openstack.org/#q,topic:bp/exclude-cbs-in-snapshot,n,z

Addressed by: https://review.openstack.org/40187
    Give an option to exclude CBS from snapshots

[alaski] I want to make sure I understand the full scope of this. Based on the bp description I thought this was only about image based instances with volumes attached, but the review above is about volume backed instances. Can you clarify if this is about volumes attached to instances or volume backed instances? To me it seems like this should just be volumes attached to image based instances. Also this needs a milestone target set.

[aditi] We will not be able to take a snapshot of a running VM with volumes attached. In this case, we have to detach the volume, and use the volume snapshot feature. This review deals with the other case, where we take a snapshot of volume backed instances. We can provide the option to either snapshot all the volumes, or just the root volume alone. Do you see any issue with this approach?

[alaski] I don't see an issue with the approach, but could you update the blueprint description to reflect that. The title and description make it seem that it will be possible to exclude attached volumes from volume or image backed instances.

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

[aditi] Blueprint updated.

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguyDeferred to icehouse-3 as the blueprint was not approved by the icehouse-2 blueprint approval deadline. --russellb

Gerrit topic: https://review.openstack.org/#q,topic:bp/exclude-cbs-in-snapshot,n,z

Addressed by: https://review.openstack.org/40187
    Give an option to exclude CBS from snapshots

[alaski] I want to make sure I understand the full scope of this. Based on the bp description I thought this was only about image based instances with volumes attached, but the review above is about volume backed instances. Can you clarify if this is about volumes attached to instances or volume backed instances? To me it seems like this should just be volumes attached to image based instances. Also this needs a milestone target set.

[aditi] We will not be able to take a snapshot of a running VM with volumes attached. In this case, we have to detach the volume, and use the volume snapshot feature. This review deals with the other case, where we take a snapshot of volume backed instances. We can provide the option to either snapshot all the volumes, or just the root volume alone. Do you see any issue with this approach?

[alaski] I don't see an issue with the approach, but could you update the blueprint description to reflect that. The title and description make it seem that it will be possible to exclude attached volumes from volume or image backed instances.

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

[aditi] Blueprint updated.

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy

Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

Gerrit topic: https://review.openstack.org/#q,topic:bp/to,n,z

Addressed by: https://review.openstack.org/84972
    Proposed blueprint to allow only root voume backup.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.