Project

General

Profile

Actions

Feature #47266

closed

add a subcommand to change caps in a simpler and clear way

Added by Rishabh Dave over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Administration/Usability
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
MDSMonitor
Labels (FS):
Pull request ID:

Description

I am not sure if there's a better way to do it but AFAIS changing permission flag or path within the cap isn't very convenient right now -

$ ./bin/ceph auth get client.foo
exported keyring for client.foo
[client.foo]
    key = AQA3Xk9fOfdhNBAAWBvLYWnBOlDXoRpXMaDfPA==
    caps mds = "allow rw fsname=a, allow rw fsname=cephfs2" 
    caps mon = "allow r" 
    caps osd = "allow rw tag cephfs data=a, allow rw tag cephfs data=cephfs2" 
$ ./bin/ceph auth caps client.foo mds 'allow rw fsname=a, allow r fsname=cephfs2'
updated caps for client.foo
$ ./bin/ceph auth get client.foo
exported keyring for client.foo
[client.foo]
    key = AQA3Xk9fOfdhNBAAWBvLYWnBOlDXoRpXMaDfPA==
    caps mds = "allow rw fsname=a, allow r fsname=cephfs2" 
$ 

It would be better if there's a simpler and cleaner way to change rw to r for cephfs2 above.

What about adding another subcommand, say "reauthorize" for now, for this? It would take same arguments as "fs authorize" but instead of assigning new caps, it would modify, without disturbing the caps for other FSs, if the cap is present for the FS already. Alternatively, we can also add --modify flag to "fs authorize" to get the same thing done.

Actions #1

Updated by Rishabh Dave over 3 years ago

Closing this ticket based on conversation with Patrick.

Actions #2

Updated by Rishabh Dave over 3 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF