Bug 1081001 – Need to allow disabling of bandwidth polling periodic task

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1081001 - Need to allow disabling of bandwidth polling periodic task

Summary:	Need to allow disabling of bandwidth polling periodic task

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-nova (Show other bugs)
Sub Component:
Version:	4.0
Hardware:	Unspecified Unspecified

Priority	medium Severity low
Target Milestone:	z4
Target Release:	4.0
Assigned To:	Vladan Popovic
QA Contact:	Vladan Popovic
Docs Contact:

URL:
Whiteboard:
Keywords:	OtherQA, ZStream

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2014-03-26 09:21 EDT by Russell Bryant
Modified:	2016-04-26 16:38 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	openstack-nova-2013.2.3-4.el6ost
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2014-05-29 16:35:36 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
OpenStack gerrit	60641	None	None	None	Never
Red Hat Product Errata	RHSA-2014:0578	normal	SHIPPED_LIVE	Moderate: openstack-nova security, bug fix, and enhancement update	2014-05-29 20:27:05 EDT

Groups: None (edit)

Description Russell Bryant 2014-03-26 09:21:47 EDT

In RHOS 5.0, the periodic task related to the bandwidth_poll_interval configuration option is automatically turned into a no-op when the underlying driver does not support it.  In RHOS 4.0, this task will do unnecessary work every time it runs.  This includes querying the details of all running instances on the compute host from the conductor service.  This adds unnecessary load on the database, conductor, message bus, and the compute host.

This task is only relevant for the xenapi driver so we should backport the patch that turns off the task automatically.


commit 4f82543ac7427638fec7e286bbb84fd7b3e3e9f3
Author: Phil Day <philip.day@hp.com>
Date:   Fri Dec 6 23:54:43 2013 +0000

    Make it possible to disable polling for bandwidth usage
    
    Bandwidth usage is only supported by some hypervisor drivers, but
    the period task always runs and asks conductor for a list of
    instances before it gets a NotImplementedError from the virt driver.
    
    This change allows this to be disabled by setting bandwidth_poll_interval
    to 0 which is consistent with other periodic task interval settings,
    avoiding the wasted conductor call.
    
    It also will automatically disable bandwidth polling if the driver raises
    NotImplemented.
    
    Change-Id: I2ac9c967c5ceafffc39a0a372146c762891a08b8

Comment 4 Vladan Popovic 2014-05-28 11:36:21 EDT

Without the patch (by setting the periodic task to 1min):
2014-05-28 11:30:39.372 15114 INFO nova.compute.manager [req-560be7dc-1c0c-454e-9100-acfaf9a533b4 None None] Updating bandwidth usage cache
...
2014-05-28 11:31:39.776 15114 INFO nova.compute.manager [-] Updating bandwidth usage cache
...
2014-05-28 11:32:40.232 15114 INFO nova.compute.manager [-] Updating bandwidth usage cache


With the patch that only happens once:

2014-05-28 11:34:06.097 15304 INFO nova.compute.manager [-] Updating bandwidth usage cache
2014-05-28 11:34:06.126 15304 WARNING nova.compute.manager [-] Bandwidth usage not supported by hypervisor.
2014-05-28 11:35:06.156 15304 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources

Comment 6 errata-xmlrpc 2014-05-29 16:35:36 EDT

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.

http://rhn.redhat.com/errata/RHSA-2014-0578.html

Note You need to log in before you can comment on or make changes to this bug.