Bug 1141497

Summary:	VM boot scale degradation when using l2population
Product:	Red Hat OpenStack	Reporter:	Ofer Blaut <oblaut>
Component:	openstack-neutron	Assignee:	Ihar Hrachyshka <ihrachys>
Status:	CLOSED DUPLICATE	QA Contact:	Ofer Blaut <oblaut>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 7)	CC:	chrisw, nyechiel, oblaut, yeylon
Target Milestone:	---	Keywords:	ZStream
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-14 14:00:39 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:

Description Ofer Blaut 2014-09-14 05:08:30 UTC

Description of problem:

Working on small scale ( 1 controller ,1 networker and 2 computes ) and it seems

1.  ML2 +L2 pop i can only reach about 60 VMs (cirrus/nano), any known bug ?
2.  ML2 +L2 pop disabled  reach 120 VMs ( with/without multi neutron workers )

With L2Population disabled I was able to achieve more guest launches in parallel.




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

How reproducible:


Steps to Reproduce:
1.See above
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Ihar Hrachyshka 2014-09-16 11:10:44 UTC

Ofer, any details on what issues you saw when launching lots of instances with l2pop enabled? As per Joe findings, there is some bug due to SIGTERM sent to OVS agent as in: https://bugzilla.redhat.com/show_bug.cgi?id=1136969 Any other specific issues you have in mind?

Comment 5 Ihar Hrachyshka 2015-01-14 14:00:39 UTC

OK, I assume the bug is a duplicate and will be fixed in the bext async release that will receive upstream rebase that includes the fix.

*** This bug has been marked as a duplicate of bug 1136969 ***