Bug 1141497 - VM boot scale degradation when using l2population
Summary: VM boot scale degradation when using l2population
Keywords:
Status: CLOSED DUPLICATE of bug 1136969
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Ihar Hrachyshka
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-14 05:08 UTC by Ofer Blaut
Modified: 2016-04-26 14:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-14 14:00:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1337717 0 None None None Never

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 ***
Note You need to log in before you can comment on or make changes to this bug.