1a9518119c
We note here that although this operation is implemented in the Ceph backend, the Ceph docs indicate that it is inefficient and the preferred method of returning to a known previous state is to clone from a snapshot. However, this is properly a backend operation, and it does not make sense to try to do it better in the driver than it can be done on the backend. Co-authored-by: Brian Rosmaita <rosmaita.fossdev@gmail.com> Implements: bp rbd-revert-to-snapshot Change-Id: If8a5eb3a03e18f9043ff29f7648234c9b46376a0
37 lines
1.4 KiB
YAML
37 lines
1.4 KiB
YAML
---
|
|
features:
|
|
- |
|
|
RBD driver: support added for reverting a volume to the most recent
|
|
snapshot taken.
|
|
|
|
Please be aware of the following known issues with this operation
|
|
and the Ceph storage backend:
|
|
|
|
* Rolling back a volume to a snapshot overwrites the current volume
|
|
with the data from the snapshot, and the time it takes to complete
|
|
this operation increases with the size of the volume.
|
|
|
|
It is faster to create a new volume from a snapshot. You may
|
|
wish to recommend this option to your users whose use cases do not
|
|
strictly require revert-to-snapshot.
|
|
|
|
* The efficiency of revert-to-snapshot is also dependent upon the
|
|
Ceph storage backend in use, namely, whether or not BlueStore is
|
|
being used in your Ceph installation.
|
|
|
|
Please consult the Ceph documentation for details.
|
|
issues:
|
|
- |
|
|
RBD driver: There are some known issues concerning the revert-to-snapshot
|
|
support added in this release.
|
|
|
|
* The time it takes to complete the revert-to-snapshot operation increases
|
|
with the size of the volume. It is faster to create a new volume from
|
|
a snapshot.
|
|
|
|
* The efficiency of revert-to-snapshot depends upon the Ceph storage
|
|
backend in use, particularly whether or not BlueStore is being used
|
|
in your Ceph installation.
|
|
|
|
Please consult the Ceph documentation for details.
|