Feature #45371
closed
mgr/volumes: `protect` and `clone` operation in a single transaction
Added by Humble Chirammal almost 4 years ago.
Updated over 3 years ago.
Category:
Administration/Usability
Backport:
octopus,nautilus
Component(FS):
mgr/volumes
Description
At the moment if we want to make a clone of a snapshot, the caller ( example , ceph CSI) has to make 2 calls to achieve the end result. Two calls per clone operation ( 1. Protect, 2 clone) is inefficient when there are many parallel requests. The request here is internally/implicitly handle `protect` operation on the source volume before initiating the clone itself. This could improve the usability in a great extend.
- Assignee set to Kotresh Hiremath Ravishankar
- Subject changed from Club `protect` and `clone` operation in a sinle transaction to mgr/volumes: `protect` and `clone` operation in a sinle transaction
- Status changed from New to In Progress
- Target version set to v16.0.0
- Component(FS) mgr/volumes added
- Assignee changed from Kotresh Hiremath Ravishankar to Shyamsundar Ranganathan
Based on #note-3 reassigning it to myself.
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 35755
- Status changed from Fix Under Review to In Progress
Moved back to in progress, to handle backward compatibility for non-CSI use cases where protect/unprotect maybe in use (e.g Openstack Manila)
- Subject changed from mgr/volumes: `protect` and `clone` operation in a sinle transaction to mgr/volumes: `protect` and `clone` operation in a single transaction
- Status changed from In Progress to Fix Under Review
- Status changed from Fix Under Review to Pending Backport
- Backport set to octopus,nautilus
- Copied to Backport #46527: nautilus: mgr/volumes: `protect` and `clone` operation in a single transaction added
- Copied to Backport #46528: octopus: mgr/volumes: `protect` and `clone` operation in a single transaction added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF