Project

General

Profile

Actions

Feature #15406

closed

Add versioning to CephFSVolumeClient interface

Added by John Spray about 8 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
jewel
Reviewed:
Affected Versions:
Component(FS):
Labels (FS):
Manila
Pull request ID:

Description

As we add features and change things in CephFSVolumeClient, we will need to add a mechanism for users of the module to declare what version they expect to see, and query whether this module can support that.

I don't think we necessarily need everything to be exhaustively backwards compatible, the key thing is that it should raise an error when an incompatible version is in play, rather than having some unexpected behaviour.

There are three entities with potentially three different versions: the Ceph cluster, the CephFSVolumeClient module, and the user (i.e. Manila). What I'm talking about versioning in this ticket is the CephFSVolumeClient<->Manila part.


Related issues 1 (0 open1 closed)

Copied to CephFS - Backport #16831: jewel: Add versioning to CephFSVolumeClient interfaceResolvedRamana RajaActions
Actions #1

Updated by Ramana Raja about 8 years ago

  • Category set to 87
Actions #2

Updated by Ramana Raja almost 8 years ago

  • Status changed from New to In Progress
  • Assignee set to Ramana Raja
Actions #4

Updated by Ramana Raja over 7 years ago

  • Copied to Backport #16831: jewel: Add versioning to CephFSVolumeClient interface added
Actions #5

Updated by Ramana Raja over 7 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #6

Updated by Nathan Cutler over 7 years ago

  • Backport set to jewel
Actions #7

Updated by Loïc Dachary over 7 years ago

  • Status changed from Pending Backport to Resolved
Actions #8

Updated by Patrick Donnelly about 5 years ago

  • Category deleted (87)
  • Labels (FS) Manila added
Actions

Also available in: Atom PDF