Project

General

Profile

Feature #3167

auth: separate read/write capabilities for classes

Added by Josh Durgin over 11 years ago. Updated over 11 years ago.

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

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Currently class operations can only be allowed in an all-or-nothing manner, with the x capability.

It would be useful (for example for rbd layering) to allow access only to read class methods, since class methods are required to read the rbd header.
Reads vs writes is a generally useful distinction that does not require more cumbersome management like #2472.

Associated revisions

Revision 135c85a4 (diff)
Added by Josh Durgin over 11 years ago

OSDCap: add separate caps for class read and class write

These are useful for rbd layering, since reading an rbd image
requires read-only class methods.

Fixes: #3167
Signed-off-by: Josh Durgin <>

History

#1 Updated by Josh Durgin over 11 years ago

  • translation missing: en.field_position set to 1

#2 Updated by Josh Durgin over 11 years ago

  • Category set to OSD
  • Status changed from New to In Progress
  • Assignee set to Josh Durgin
  • Target version set to v0.54a

#3 Updated by Sage Weil over 11 years ago

  • Target version changed from v0.54a to v0.54b
  • translation missing: en.field_position deleted (21)
  • translation missing: en.field_position set to 1

#4 Updated by Sage Weil over 11 years ago

  • translation missing: en.field_story_points set to 5
  • translation missing: en.field_position deleted (7)
  • translation missing: en.field_position set to 7

#5 Updated by Josh Durgin over 11 years ago

  • Status changed from In Progress to Fix Under Review

#6 Updated by Sage Weil over 11 years ago

  • Status changed from Fix Under Review to Resolved
  • translation missing: en.field_position deleted (8)
  • translation missing: en.field_position set to 8

Also available in: Atom PDF