Project

General

Profile

Feature #45371

mgr/volumes: `protect` and `clone` operation in a single transaction

Added by Humble Chirammal 9 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Shyamsundar Ranganathan
Category:
Administration/Usability
Target version:
Ceph - v16.0.0
% Done:

0%

Source:
Community (dev)
Tags:
ceph-csi
Backport:
octopus,nautilus
Reviewed:
Affected Versions:
Component(FS):
mgr/volumes
Labels (FS):
Pull request ID:
35755

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.

Related issues

Copied to CephFS - Backport #46527: nautilus: mgr/volumes: `protect` and `clone` operation in a single transaction Resolved
Copied to CephFS - Backport #46528: octopus: mgr/volumes: `protect` and `clone` operation in a single transaction Resolved

History

#1 Updated by Kotresh Hiremath Ravishankar 9 months ago

  • Assignee set to Kotresh Hiremath Ravishankar

#2 Updated by Patrick Donnelly 9 months ago

  • 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

#3 Updated by Kotresh Hiremath Ravishankar 7 months ago

With subvolume and snapshot decoupling feature1, snapshot protect and unprotect would no longer be required.

[1] https://tracker.ceph.com/issues/45729

#4 Updated by Shyamsundar Ranganathan 7 months ago

  • Assignee changed from Kotresh Hiremath Ravishankar to Shyamsundar Ranganathan

Based on #note-3 reassigning it to myself.

#5 Updated by Shyamsundar Ranganathan 7 months ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 35755

#6 Updated by Shyamsundar Ranganathan 7 months ago

  • 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)

#7 Updated by Shyamsundar Ranganathan 7 months ago

  • 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

#8 Updated by Patrick Donnelly 7 months ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to octopus,nautilus

#9 Updated by Nathan Cutler 7 months ago

  • Copied to Backport #46527: nautilus: mgr/volumes: `protect` and `clone` operation in a single transaction added

#10 Updated by Nathan Cutler 7 months ago

  • Copied to Backport #46528: octopus: mgr/volumes: `protect` and `clone` operation in a single transaction added

#11 Updated by Nathan Cutler 5 months ago

  • 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