Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1436161

Summary:	[RFE][scale]Increase LVs per VG alert limit
Product:	[oVirt] ovirt-engine	Reporter:	Tal Nisan <tnisan>
Component:	BLL.Storage	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	guy chen <guchen>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.1.6	CC:	bugs, eheftman, lveyde
Target Milestone:	ovirt-4.1.2	Keywords:	FutureFeature, Performance
Target Release:	4.1.2	Flags:	rule-engine: ovirt-4.1? rule-engine: planning_ack? rule-engine: devel_ack+ rule-engine: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Release Note
Doc Text:	The recommended number of logical volumes per storage domain was increased from 300 to 1000. The alert that is issued when exceeding this number was changed to reflect that. Note that the limit will only change to 1000 if it was set to 300. If the customer manually configured the limit, the original configuration will not be overridden.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-23 08:13:48 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:

Description Tal Nisan 2017-03-27 11:04:20 UTC

Description of problem:
RFE 1015186 added a limit to a number of LVs per VG (basically amount of volumes per storage domain) after which an alert will be logged after addition of another LV to the VG, the original RFE set the limit to 300 as that was the recommended limit in 3.5, currently the recommendation is a limit of 1000 per VG so the limit needs to be updated

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 guy chen 2017-05-15 10:22:40 UTC

Tested, created 500 VMS with 2 disks each on a single SD, on 501 VM creation got the expected alert.