Bug 1283753 - [RFE][nova] RBD instance snapshots
Summary: [RFE][nova] RBD instance snapshots
Keywords:
Status: CLOSED DUPLICATE of bug 1183796
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: Upstream M3
: 9.0 (Mitaka)
Assignee: Eoghan Glynn
QA Contact: nlevinki
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_mitaka-3 upstream_...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-19 17:59 UTC by Sean Cohen
Modified: 2019-09-09 15:41 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-02 19:22:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 188244 0 None None None Never

Description Sean Cohen 2015-11-19 17:59:32 UTC
Description
=========

Taking a snapshot of your virtual machine that is backed by RBD. The snapshot of the disk is saved in Glance, and it can be used to spawn new instances. 

This feature modifies the way Nova does snapshots, eliminating the need to move a copy from local ephemeral storage to the Ceph cluster, but instead making the copy operation internal to the Ceph cluster. 

old path: RBD-> local->Glance->RBD again.
new path: all data path is internal to Ceph

Currently the snapshot has to be offline (Suspend the Guest), but it cam be made live in the future.

The key user ask is the ability to use compute nodes without local storage, and snapshots are the last remaining function requiring significant local storage.

User Stories
==========
* As an Operator, I want to run my compute nodes without any local storage

Comment 2 Sean Cohen 2015-11-19 18:01:45 UTC
https://review.openstack.org/#/c/188244/ was merged upstream

Comment 3 Stephen Gordon 2016-02-02 19:22:03 UTC

*** This bug has been marked as a duplicate of bug 1183796 ***


Note You need to log in before you can comment on or make changes to this bug.