Bug 1858826 - mgr/volumes: Remove 'protect' and 'unprotect' requirements to clone a subvolume snapshot
Summary: mgr/volumes: Remove 'protect' and 'unprotect' requirements to clone a subvolu...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: CephFS
Version: 5.0
Hardware: All
OS: All
high
high
Target Milestone: ---
: 5.0
Assignee: Shyamsundar
QA Contact: subhash
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-20 13:50 UTC by Shyamsundar
Modified: 2020-12-14 16:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1857827
Environment:
Last Closed: 2020-07-31 21:58:20 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 46528 0 None None None 2020-07-20 16:22:30 UTC

Description Shyamsundar 2020-07-20 13:50:28 UTC 
+++ This bug was initially created as a clone of Bug #1857827 +++

Subvolume snapshots required to be protected, prior to cloning the same.

Also, protected snapshots were not allowed to be unprotected or removed, if there were in-flight clones, whose source was the snapshot being removed.

The protection of snapshots explicitly is not required, as these can be prevented from being removed based only on the in-flight clones checks.

These calls should hence be deprecated, and this allows a clone to be a simpler implementation for consumers like ceph-csi.

In addition to deprecating the above, add support to query a subvolume for supported features, via the subvolume info command, to assist with a Ceph version based  decision on when to use these calls prior to cloning the subvolume.
Note You need to log in before you can comment on or make changes to this bug.