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

Bug 1285397

Summary:	Backport Neutron L3 performance fixes
Product:	Red Hat OpenStack	Reporter:	Brent Eagles <beagles>
Component:	openstack-neutron	Assignee:	Brent Eagles <beagles>
Status:	CLOSED ERRATA	QA Contact:	Ofer Blaut <oblaut>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.0 (Kilo)	CC:	amuller, beagles, chrisw, dcadzow, mlopes, nyechiel, sclewis, tfreger, yeylon
Target Milestone:	z4	Keywords:	FeatureBackport, ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-2015.1.2-7.el7ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-18 16:09:38 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 Brent Eagles 2015-11-25 14:20:12 UTC

Description of problem:

Several backportable improvements have been made to neutron in the Liberty cycle that remove extra overhead during normal operation.

As this is an intrinsic performance issue, it is in a sense 100% reproducible. However, there is no direct mechanism of quantifying the problem without invasive instrumentation of the code. Steps to reproduce might look like:

1. Configure a reasonable yet large number of routers
2. Monitor CPU usage of neutron server and responsiveness of operations

The actual results might be that the neutron server spikes to a sustained 100% CPU usage and loses responsiveness, while the expected result is that it fluctuates according to user activity and the agent update cycle.

Comment 2 Ofer Blaut 2016-01-24 09:52:31 UTC

code verified in openstack-neutron-2015.1.2-7.el7ost.noarch

Comment 6 errata-xmlrpc 2016-02-18 16:09:38 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://rhn.redhat.com/errata/RHBA-2016-0260.html