Bug 1464957
Summary: | [RFE] Simplified RBD client key creation | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | John Spray <john.spray> |
Component: | RBD | Assignee: | Jason Dillaman <jdillama> |
Status: | CLOSED ERRATA | QA Contact: | Parikshith <pbyregow> |
Severity: | urgent | Docs Contact: | Bara Ancincova <bancinco> |
Priority: | urgent | ||
Version: | 3.0 | CC: | anharris, ceph-eng-bugs, edonnell, hnallurv, jdillama |
Target Milestone: | rc | Keywords: | FutureFeature |
Target Release: | 3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-12.1.2-1.el7cp Ubuntu: ceph_12.1.2-2redhat1xenial | Doc Type: | Enhancement |
Doc Text: |
.Granting access to Ceph Block Device images has been simplified
The `ceph auth get-or-create` command now supports two profiles, `rbd` and `rbd-read-only`. When using these profiles, `cephx` capabilities are created automatically without the need to specify them directly. For example, to create a `client.1` user with required capabilities for Monitors and OSDs:
----
ceph auth get-or-create client.1 mon 'profile rbd' osd 'profile rbd [pool=<pool>]'
----
OSDs support the `rbd` and `rbd-read-only` profiles. Monitors support only the `rbd` profile.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-05 23:34:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1494421 |
Description
John Spray
2017-06-26 09:55:11 UTC
In-progress as part of the Luminous release. RBD clients can now be defined using a simplified syntax: ceph auth get-or-create client.<ID> mon 'profile rbd' osd 'profile rbd[ pool=<pool>][, profile ...]' The OSD has two possible profiles: rbd and rbd-read-only The MON has a single possible profile: rbd Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3387 |