Bug 1570162 - Adding Ceph-mgr Dashboard section to RHCS 3.0 Release Notes
Summary: Adding Ceph-mgr Dashboard section to RHCS 3.0 Release Notes
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Documentation
Version: 3.0
Hardware: Unspecified
OS: Linux
Target Milestone: rc
: 3.2
Assignee: ceph-docs@redhat.com
QA Contact: ceph-qe-bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-20 18:59 UTC by mamccoma
Modified: 2018-11-20 09:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-11-20 09:12:53 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description mamccoma 2018-04-20 18:59:34 UTC
There is a new feature in Ceph 3 where a customer can install the ceph-mgr dashboard and should be reflected in the RHCS 3 Release notes. This feature is not documented yet in Red Hat documentation so I have created doc Bug 1570074
to add this to the RHCS administration guide.  In addition, I have created this doc bug to illustrate this new feature in the RHCS ceph 3 release notes and link it to the admin guide (so probably this doc bug should be completed after Bug 1570074 is completed).

The RHCS 3 Release notes can be found at.

I think it is most appropriate to be located in the end of Chapter 3 "Major Updates" after the section on "Support for the Restful plug-in" section with the write-up as below:


Support for the Ceph Manager Dashboard Plugin

With the addition of the new ceph-mgr daemon, administrators can configure the clusters active ceph-mgr daemon to display a dashboard for a fast visual of the clusters state.  The ceph-mgr dashboard can be accessed from a web browser for a basic visual representation of cluster information pertaining to health, usage, and the status of various Ceph components in the cluster.

For details, see the Red Hat Ceph Storage 3 Administration Guide.


"Red Hat Ceph Storage 3 Administration Guide" mentioned above should be a link to this document: 


Note You need to log in before you can comment on or make changes to this bug.