-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Conflicts: src/osd/OSDCap.cc src/test/osd/osdcap.cc Reviewed-by: Sage Weil <[email protected]>
- Loading branch information
Showing
19 changed files
with
494 additions
and
194 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
v0.54 | ||
----- | ||
|
||
* The osd capabilities associated with a rados user have changed | ||
syntax since 0.48 argonaut. The new format is mostly backwards | ||
compatible, but there are two backwards-incompatible changes: | ||
|
||
* specifying a list of pools in one grant, i.e. | ||
'allow r pool=foo,bar' is now done in separate grants, i.e. | ||
'allow r pool=foo, allow r pool=bar'. | ||
|
||
* restricting pool access by pool owner ('allow r uid=foo') is | ||
removed. This feature was not very useful and unused in practice. | ||
|
||
The new format is documented in the ceph-authtool man page. | ||
|
||
* Bug fixes to the new osd capability format parsing properly validate | ||
the allowed operations. If an existing rados user gets permissions | ||
errors after upgrading, its capabilities were probably | ||
misconfigured. See the ceph-authtool man page for details on osd | ||
capabilities. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.