Project

General

Profile

Feature #15066

multifs: Allow filesystems to be assigned RADOS namespace as well as pool for metadata and data

Added by John Spray about 8 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
High
Category:
-
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
Client, Common/Protocol, MDS, MDSMonitor, kceph
Labels (FS):
multifs
Pull request ID:

Description

Everywhere we accept a pool argument currently (e.g. in "ceph fs new"), we should additionally accept a RADOS namespace.

This will enable multiple-filesystem users to have their filesystems sharing RADOS pools, rather than having to have a pool per filesystem.

We should probably have a simple syntax like "mypool:mynamespace" for these arguments, such that existing pool-only arguments will continue to work and use the default namespace.


Related issues

Blocks CephFS - Feature #21709: ceph fs authorize should detect the correct data namespace New 10/06/2017
Blocks CephFS - Feature #22477: multifs: remove multifs experimental warnings Resolved
Blocked by CephFS - Feature #5520: osdc: should handle namespaces Rejected

History

#1 Updated by John Spray almost 8 years ago

Note: once we do this, we have to start using two separate messengers in the MDS for rados client vs. cephfs server (or some other solution that gives unique entity ids but still presents the rank as the ID to old clients).

It's so that we don't have multiple daemons with the same rank (but different filesystem IDs) touching the same pool (doesn't happen at moment but will happen when using namespaces) the incarnation logic works to preserve operation order on crashes.

#2 Updated by Greg Farnum almost 8 years ago

  • Category changed from 47 to 93

#3 Updated by John Spray over 7 years ago

Just in case I lose it, the draft code for splitting messengers was here: https://github.com/jcsp/ceph/tree/wip-15399-twomsg

#4 Updated by Douglas Fuller over 6 years ago

  • Blocks Feature #21709: ceph fs authorize should detect the correct data namespace added

#5 Updated by Douglas Fuller over 6 years ago

we should default to using a namespace named after the filesystem unless otherwise specified.

#6 Updated by Patrick Donnelly over 6 years ago

  • Blocks Feature #22477: multifs: remove multifs experimental warnings added

#7 Updated by Patrick Donnelly over 6 years ago

  • Blocks deleted (Feature #22477: multifs: remove multifs experimental warnings)

#8 Updated by Patrick Donnelly over 6 years ago

  • Blocks Feature #22477: multifs: remove multifs experimental warnings added

#9 Updated by Patrick Donnelly about 6 years ago

  • Target version set to 552

#10 Updated by Patrick Donnelly almost 6 years ago

  • Target version changed from 552 to v14.0.0

#11 Updated by Patrick Donnelly almost 6 years ago

  • Category deleted (93)
  • Tags set to multifs

#12 Updated by Patrick Donnelly almost 6 years ago

  • Assignee set to Patrick Donnelly
  • Priority changed from Normal to Urgent
  • Source changed from other to Development
  • Tags deleted (multifs)
  • Labels (FS) multifs added

#13 Updated by Patrick Donnelly over 5 years ago

  • Assignee changed from Patrick Donnelly to Venky Shankar
  • Component(FS) Client, Common/Protocol, MDS, MDSMonitor, kceph added

#14 Updated by Patrick Donnelly about 5 years ago

  • Status changed from New to In Progress
  • Assignee changed from Venky Shankar to Patrick Donnelly
  • Priority changed from Urgent to High
  • Start date deleted (03/11/2016)

#15 Updated by Patrick Donnelly about 5 years ago

  • Target version changed from v14.0.0 to v15.0.0

#16 Updated by Patrick Donnelly almost 5 years ago

#17 Updated by Patrick Donnelly almost 5 years ago

  • Assignee deleted (Patrick Donnelly)

Needs the ability to delete a RADOS namespace. See also: https://www.spinics.net/lists/ceph-devel/msg36695.html

#18 Updated by Patrick Donnelly almost 5 years ago

  • Assignee set to Patrick Donnelly

#19 Updated by Patrick Donnelly over 4 years ago

  • Status changed from In Progress to Rejected

Now that pg_autoscaler exists with pg merging, this feature is not compelling. Using separate pools for multifs has always been more attractive from an accounting perspective. Now pools are cheap to make and use so let's just do that.

Also available in: Atom PDF