Bug 1041725 - [RFE][cinder]: Snapshot Replication
Summary: [RFE][cinder]: Snapshot Replication
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/cind...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 18:50 UTC by RHOS Integration
Modified: 2015-11-20 19:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:34:56 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 18:50:24 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/snapshot-replication.

Description:

Make snapshots a full object which can be replicated between similar storage backends. Definable states would also be documented.

Replication of snapshots can be the most efficient way to implement both volume migration and volume mirroring. Beyond that the same mechanism can be used to build additional features:

* Archiving of snapshots on additional servers to allow a volume to be "restored" by cloning it
   at a new location. Unlike mirroring there is no need to explicitly pair active/passive servers 
   in advance. Snapshot replication can achieve disaster recovery schemes at a lower cost
   than mirroring (albeit with a longer RPO).
* Replication of snapshots can also be used to distirbute master images to poential host
   machines, where a new boot volume can be cloned from the replicated snapshot with
   far less bandwidth being required at provisioning time. This can enable more rapid
   deployment of compute nodes from master images, and allow for updates of master
   images to be less costly.


Specification URL (additional information):

https://wiki.openstack.org/wiki/Snapshot_as_full_objects


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