Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1325720 - [RFE][manila] Collect Telemetry Metrics from Manila
[RFE][manila] Collect Telemetry Metrics from Manila
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-manila (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
medium Severity low
: Upstream M2
: 12.0 (Pike)
Assigned To: Victoria Martinez de la Cruz
Raissa Sarmento
Don Domingo
: FutureFeature, Triaged
: 1351809 (view as bug list)
Depends On:
Blocks: 1442136 1469184
  Show dependency treegraph
 
Reported: 2016-04-10 20:44 EDT by Shinobu KINJO
Modified: 2018-02-05 14:02 EST (History)
16 users (show)

See Also:
Fixed In Version: openstack-manila-5.0.0-0.20170707130043.8fddbe2.el7ost
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1469184 (view as bug list)
Environment:
Last Closed: 2017-12-13 15:40:44 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 445441 None None None 2017-04-25 11:13 EDT
OpenStack gerrit 466586 None None None 2017-06-13 02:17 EDT
Red Hat Product Errata RHEA-2017:3462 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-15 20:43:25 EST

  None (edit)
Description Shinobu KINJO 2016-04-10 20:44:46 EDT
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".
Comment 7 Sean Cohen 2016-10-21 11:51:25 EDT
*** Bug 1351809 has been marked as a duplicate of this bug. ***
Comment 8 jliberma@redhat.com 2016-12-19 09:54:11 EST
There is no customer case.
Comment 10 Tom Barron 2017-04-25 11:14:51 EDT
Manila spec https://review.openstack.org/445441 has been accepted and merged upstream for Pike.
Comment 21 errata-xmlrpc 2017-12-13 15:40:44 EST
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

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