Bug 1275182
Summary: | [RFE]Email notification when the number of LVs in SD are reaching/more than 300 | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Alexandros Gkesos <agkesos> | |
Component: | RFEs | Assignee: | Idan Shaby <ishaby> | |
Status: | CLOSED ERRATA | QA Contact: | Natalie Gavrielov <ngavrilo> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 3.5.4 | CC: | acanan, amureini, gklein, ishaby, lsurette, martin.hovmoller, masayag, melewis, ppostler, rbalakri, srevivo, tnisan, ykaul, ylavi | |
Target Milestone: | ovirt-4.0.0-rc | Keywords: | EasyFix, FutureFeature | |
Target Release: | 4.0.0 | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | ovirt 4.0.0 alpha1 | Doc Type: | Enhancement | |
Doc Text: |
Previously, when the number of logical volumes in a storage domain reached the recommended maximum it was logged and a message was shown in the events pane. Now, a user can register to the event notifier and receive an email when the number of logical volumes in a storage domain reached the recommended maximum.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1317468 (view as bug list) | Environment: | ||
Last Closed: | 2016-08-23 20:30:16 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1317468 | |||
Bug Blocks: |
Description
Alexandros Gkesos
2015-10-26 08:45:08 UTC
(In reply to Alexandros Gkesos from comment #0) > Description of problem: > > - We have the Logical Volumes limitation in a Storage Domain in our official > Documentation > > https://access.redhat.com/documentation/en-US/ > Red_Hat_Enterprise_Virtualization/3.5/html/Technical_Guide/ > Storage_domain_limitations.html > > - We have the warning at the RHEV-M events > > "The number of LVs on the domain XXX exceeded 300, you are approaching the > limit where performance may degrade." > > But many customers do not access frequently the admin portal and do not get > notified regarding that. Oved - don't we have a notifier mechanism that can send an email based on an event? There is the engine-notifier, but there is no option yet for that event. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.3/html-single/Administration_Guide/index.html#chap-Event_Notifications There is a mechanism. It should be simple to add this event there. Once you assign someone for that, have him sit with Moti, and he will give a proper example. (In reply to Oved Ourfali from comment #6) > There is a mechanism. > It should be simple to add this event there. > > Once you assign someone for that, have him sit with Moti, and he will give a > proper example. Thanks Oved! I was under the [wrong] impression that there's a generic connection between AuditLogs and notifications, and the customer just needs to set up the email details. Once we start handling 4.0 features, I'll send someone your way. Thanks again! Hi Idan, Is the 350 value hardcoded? If not where can it be changed (DB / XML)? Hi Natalie, Sorry for the delay, I was on PTO the past week. The default number is 300 and it can be found on the DB: engine=> SELECT * from vdc_options WHERE option_name = 'AlertOnNumberOfLVs'; option_id | option_name | option_value | version -----------+--------------------+--------------+--------- 368 | AlertOnNumberOfLVs | 300 | general (In reply to Idan Shaby from comment #12) > Hi Natalie, > > Sorry for the delay, I was on PTO the past week. > The default number is 300 and it can be found on the DB: > > engine=> SELECT * from vdc_options WHERE option_name = 'AlertOnNumberOfLVs'; > option_id | option_name | option_value | version > -----------+--------------------+--------------+--------- > 368 | AlertOnNumberOfLVs | 300 | general We can add this as a config value to engine-config.sh. It's a trivial patch - but I wonder whether we want to make this visible to our customers. Yaniv D - your two cents? (In reply to Allon Mureinik from comment #13) > (In reply to Idan Shaby from comment #12) > > Hi Natalie, > > > > Sorry for the delay, I was on PTO the past week. > > The default number is 300 and it can be found on the DB: > > > > engine=> SELECT * from vdc_options WHERE option_name = 'AlertOnNumberOfLVs'; > > option_id | option_name | option_value | version > > -----------+--------------------+--------------+--------- > > 368 | AlertOnNumberOfLVs | 300 | general > > We can add this as a config value to engine-config.sh. It's a trivial patch > - but I wonder whether we want to make this visible to our customers. Yaniv > D - your two cents? We should since for some storage we can have more and for some less. It's also a matter of how conservative the customer is. Users would like to change this. (In reply to Yaniv Dary from comment #14) > (In reply to Allon Mureinik from comment #13) > > (In reply to Idan Shaby from comment #12) > > > Hi Natalie, > > > > > > Sorry for the delay, I was on PTO the past week. > > > The default number is 300 and it can be found on the DB: > > > > > > engine=> SELECT * from vdc_options WHERE option_name = 'AlertOnNumberOfLVs'; > > > option_id | option_name | option_value | version > > > -----------+--------------------+--------------+--------- > > > 368 | AlertOnNumberOfLVs | 300 | general > > > > We can add this as a config value to engine-config.sh. It's a trivial patch > > - but I wonder whether we want to make this visible to our customers. Yaniv > > D - your two cents? > > We should since for some storage we can have more and for some less. It's > also a matter of how conservative the customer is. Users would like to > change this. Ack. I opened bug 1338545 to track this requirement. QA: Note that for the context of THIS bug, having it available via engine-config.sh is just a nicety. THIS bug can be verified by querying (or even updating) the database directly. Moving target release to RC to include the latest fix. Verified, rhevm-4.0.0.5-0.1.el7ev.noarch One issue found (in one of the earlier builds) : https://bugzilla.redhat.com/show_bug.cgi?id=1340209 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://rhn.redhat.com/errata/RHEA-2016-1743.html |