Project

General

Profile

Actions
Copy link

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.

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 2 (0 open — 2 closed)

Copied to CephFS - Backport #46527: nautilus: mgr/volumes: `protect` and `clone` operation in a single transactionResolvedShyamsundar RanganathanActions
Copied to CephFS - Backport #46528: octopus: mgr/volumes: `protect` and `clone` operation in a single transactionResolvedShyamsundar RanganathanActions
Actions
Copy link
 #1

Updated by Kotresh Hiremath Ravishankar almost 4 years ago

  • Assignee set to Kotresh Hiremath Ravishankar
Actions
Copy link
 #2

Updated by Patrick Donnelly almost 4 years 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
Actions
Copy link
 #3

Updated by Kotresh Hiremath Ravishankar almost 4 years ago

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

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

Actions
Copy link
 #4

Updated by Shyamsundar Ranganathan almost 4 years ago

  • Assignee changed from Kotresh Hiremath Ravishankar to Shyamsundar Ranganathan

Based on #note-3 reassigning it to myself.

Actions
Copy link
 #5

Updated by Shyamsundar Ranganathan almost 4 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 35755
Actions
Copy link
 #6

Updated by Shyamsundar Ranganathan almost 4 years 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)

Actions
Copy link
 #7

Updated by Shyamsundar Ranganathan almost 4 years 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
Actions
Copy link
 #8

Updated by Patrick Donnelly almost 4 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to octopus,nautilus
Actions
Copy link
 #9

Updated by Nathan Cutler almost 4 years ago

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

Updated by Nathan Cutler almost 4 years ago

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

Updated by Nathan Cutler over 3 years 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".

Actions
Copy link

Also available in: Atom PDF