Bug 1356758

Summary: [RFE] add capacity information to the heketi-cli
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Paul Cuzner <pcuzner>
Component: heketiAssignee: Michael Adam <madam>
Status: CLOSED WONTFIX QA Contact: Jonathan Holloway <jholloway>
Severity: low Docs Contact:
Priority: low    
Version: rhgs-3.1CC: annair, hchiramm, jmulligan, pprakash, rtalur
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-23 19:11:20 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: 1641915    

Description Paul Cuzner 2016-07-15 01:39:06 UTC
Description of problem:
Managing one or multiple clusters with heketi would benefit from more information presented to the admin from the cli. Understanding the environment is a obviously a key deliverable of the solution, and providing a basic awareness of the capacity under the control of heketi would be a great start.

This RFE requests the following data is exposed

1. Each cluster should provide a roll-up summary consisting of the following fields;
- number of nodes in the cluster
- number of disks managed
- raw capacity managed
- raw capacity used
- raw %used
- number of volumes allocated


2. The topology view dumps all clusters, so a rollup of the cluster numbers would give a deployment wide view of the site
- total number of clusters managed
- total nodes
- total raw
- total raw used %
- total number of volumes allocated

By making this information available the admin will be able to
a) understand capacity utilisation
b) plan for more clusters or upgrades in timely manner (instead of encountering allocation failures and impacting the service offered to the business)

I would suggest that this information is added to the topology subcommand. From a usability perspective, I would also suggest that the topology info command is updated to include 
a) --cluster ... to limit topology and summary data to the specified cluster
b) --summary ... to limit the topology output to only the rollup data


Additional info:

Comment 2 Luis Pabón 2016-10-17 20:40:29 UTC
*** Bug 1355697 has been marked as a duplicate of this bug. ***