Project

General

Profile

Actions

Feature #38851

closed

mount.ceph.fuse: support secretfile option

Added by Oliver Falk about 5 years ago. Updated over 4 years ago.

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

0%

Source:
Community (user)
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
ceph-fuse
Labels (FS):
task(easy)
Pull request ID:

Description

Hi!

As far as I can see, secretfile doesn't work with mount.ceph.fuse; Is this by intention? It would be nice to have this also supported in the fuse mount, not only in the "normal" mount.ceph.

Kind regards,
Oliver

Actions #1

Updated by Patrick Donnelly about 5 years ago

  • Project changed from Ceph to CephFS
  • Subject changed from Support secretfile with mount.ceph.fuse to mount.ceph.fuse: support secretfile option
  • Category deleted (common)
  • Start date deleted (03/22/2019)
  • Source set to Community (user)
  • Component(FS) ceph-fuse added
  • Labels (FS) task(easy) added
Actions #2

Updated by Jeff Layton over 4 years ago

Yes. I think this is intentional.

The secretfile thing was really for the kernel client, which had a very primitive mount helper that couldn't understand ceph keyring files. We recently fixed mount.ceph to be able to get credentials out of standard ceph keyring files so I sort of consider the secret= and secretfile= mount options in mount.ceph to be effectively deprecated at this point.

Realistically we'll likely never be able to remove those options from mount.ceph, but I see no reason to propagate their use to ceph-fuse.

Actions #3

Updated by Patrick Donnelly over 4 years ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF