Bug 1580128

Summary: [RFE] Need a way to track how many logical volumes consumed in a storage domain and alert when it gets full
Product: Red Hat Enterprise Virtualization Manager Reporter: Greg Scott <gscott>
Component: ovirt-engineAssignee: Tal Nisan <tnisan>
Status: CLOSED ERRATA QA Contact: Evelina Shames <eshames>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.3CC: ebenahar, gscott, lsurette, mtessun, Rhev-m-bugs, sborella, srevivo, tcarlin, tnisan, ykaul
Target Milestone: ovirt-4.3.0Keywords: FutureFeature, Reopened, ZStream
Target Release: 4.3.0Flags: lsvaty: testing_plan_complete-
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.0_alpha Doc Type: If docs needed, set a value
Doc Text:
In the Administration Portal, the General subtab in Storage now displays the number of images on the storage domain with the label of "Images." This number corresponds to the number of logical volumes on a block domain.
Story Points: ---
Clone Of:
: 1587885 (view as bug list) Environment:
Last Closed: 2019-05-08 12:37:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1587885    
Attachments:
Description Flags
Screenshot none

Description Greg Scott 2018-05-20 14:09:37 UTC
We need a clear indicator of how full is a storage domain, and alerts when a storage domain becomes too full (e.g. 90% of max lvs).

The actual limit on number of logical volumes is currently 1947 volumes.
This limit is the size of the leases volume (2GiB), which currently is never
extended. If we add support for extending this volume when needed, we
can support more logical volumes.

We also need a supported way to look up how many LVs are in use, either via a script which is part of engine and maintained by engine developers, or adding this info in the UI.

Here is more detail.

Every snapshot consumes:
- one logical volume for every disk included in the snapshot
- one logical volume for memory snapshot if memory snapshot was enabled
  but the memory volume may be created on another storage domain
- logical volume for configuration data (not sure it is still used)

The limit of 1000 volumes is just an arbitrary number we invented.

We could find the number of LVs in use by cooking up a database query, but accessing the database directly is a bad idea. The query will break when
we change the schema, and we must have the flexibility to change the 
schema whenever we like to.

Comment 12 Tal Nisan 2018-06-05 13:17:33 UTC
Created attachment 1447858 [details]
Screenshot

Comment 13 Tal Nisan 2018-06-05 13:18:06 UTC
Added the number of images for each data domain as seen in the attachment

Comment 15 Evelina Shames 2018-08-16 13:51:21 UTC
Verified.

Version:
Engine - 4.3.0-0.0

Comment 17 errata-xmlrpc 2019-05-08 12:37:35 UTC
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-2019:1085

Comment 18 Franta Kust 2019-05-16 13:05:21 UTC
BZ<2>Jira Resync