Project

General

Profile

Feature #15406

Add versioning to CephFSVolumeClient interface

Added by John Spray over 3 years ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
04/06/2016
Due date:
% 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

Copied to fs - Backport #16831: jewel: Add versioning to CephFSVolumeClient interface Resolved

History

#1 Updated by Ramana Raja over 3 years ago

  • Category set to 87

#2 Updated by Ramana Raja about 3 years ago

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

#4 Updated by Ramana Raja about 3 years ago

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

#5 Updated by Ramana Raja about 3 years ago

  • Status changed from Need Review to Pending Backport

#6 Updated by Nathan Cutler about 3 years ago

  • Backport set to jewel

#7 Updated by Loic Dachary about 3 years ago

  • Status changed from Pending Backport to Resolved

#8 Updated by Patrick Donnelly 6 months ago

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

Also available in: Atom PDF