openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
53,335 Commits 9 Branches 81 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Stephen Finucane f651ebc0ce Don't set bandwidth limits for vhostuser, hostdev interfaces 
'tc' [1] is used for rate limiting in libvirt. This is suitable for tap
devices but not for the sockets used by vhostuser interface or for
physical devices; rate limiting for these interfaces must be done in the
vSwitch or via the interface itself. For this reason, libvirt explicitly
marks these interfaces, along with some other interfaces types, as not
supporting bandwidth limiting [2]. Given that there is no reason to be
setting the bandwidth-related attributes on vhostuser or hostdev
interfaces, we should stop doing it.

[1] http://man7.org/linux/man-pages/man8/tc.8.html
[2] https://github.com/libvirt/libvirt/blob/568a41722/src/conf/netdev_bandwidth_conf.h#L38

Change-Id: Id57e4c149616fe0896e80fca322ece79ec3bfd69
Closes-Bug: #1814882
 		2019-02-12 16:48:50 +00:00
api-guide/source api-ref: Body verification for the lock action 2019-01-17 04:05:50 +00:00
api-ref/source Merge "API: Remove evacuate/live-migrate 'force' parameter" 2019-02-09 22:55:34 +00:00
devstack Remove the CachingScheduler 2018-10-18 17:55:36 -04:00
doc Merge "doc: link admin/configuration from admin home page" 2019-02-12 08:07:00 +00:00
etc/nova Add osprofiler config options to generated reference 2018-06-16 12:46:19 +00:00
gate Merge "Remove placement perf check" 2018-12-08 04:56:56 +00:00
nova Don't set bandwidth limits for vhostuser, hostdev interfaces 2019-02-12 16:48:50 +00:00
playbooks/legacy Drop nova-multiattach job 2019-02-05 09:13:02 -05:00
releasenotes Merge "API: Remove evacuate/live-migrate 'force' parameter" 2019-02-09 22:55:34 +00:00
tools Make Xen code py3-compatible 2018-08-10 20:04:19 +00:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Remove Placement API reference 2018-11-28 03:38:41 +00:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Merge "Drop nova-multiattach job" 2019-02-09 22:46:34 +00:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Add a hacking rule for deprecated assertion methods 2018-10-25 11:49:10 +09:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Fix broken URLs 2017-09-07 15:42:31 +02:00
README.rst Docs: modernise links 2018-03-24 20:27:11 +08:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt Merge "Bindep does not catch missing libpcre3-dev on Ubuntu" 2018-02-14 07:31:09 +00:00
lower-constraints.txt Fix deprecation warning for threadgroup.add_timer 2019-02-07 09:37:00 -05:00
requirements.txt Fix deprecation warning for threadgroup.add_timer 2019-02-07 09:37:00 -05:00
setup.cfg Update mailinglist from dev to discuss 2018-12-05 09:44:35 +08:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Fix ironic client ironic_url deprecation warning 2018-10-24 17:59:10 +02:00
tox.ini cleanup *.pyc files in docs tox envs 2019-02-06 19:41:15 +00:00

README.rst

Team and repository tags

image

OpenStack Nova

OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.

Use the following resources to learn more.

API

To learn how to use Nova's API, consult the documentation available online at:

For more information on OpenStack APIs, SDKs and CLIs in general, refer to:

Operators

To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:

In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:

Developers

For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.

Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.

Further developer focused documentation is available at:

Other Information

During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: