Hide Forgot
This REF is about additional capabilities, entry points, will be described. [CURRENT] There is no entry point for the Manila, file share as a service in the Ceilometer; meaning that the Ceilometer does not have any capability to collect any telemetry metric from the Manila. [MOTIVATION] For sysadmin, it's very useful to get resource usages from the Manila because basically any resource is limited. And it's better to know current load like disk I/O, network I/O. So that sysadmin know how the system is busy, what could happen. [REQUEST] What the capabilities would be required are 1.Disk I/O 2.Disk latency 3.Disk iops 4.Disk capacity 5.Disk usage 6.Network I/O 7.Network I/O ratio etc Since the Manila is expected to provide share spaces to clients, "Disk" would be translated into "Share", "Network" would be specific interface used for "Share".
*** Bug 1351809 has been marked as a duplicate of this bug. ***
There is no customer case.
Manila spec https://review.openstack.org/445441 has been accepted and merged upstream for Pike.
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/RHEA-2017:3462