openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
18,792 Commits 10 Branches 95 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
1b65fb08f2
Go to file
Dan Smith 1b65fb08f2 Refactor instance usage notifications for compute manager 
This patch makes compute manager call notify_usage_exists() via the
conductor instead of directly, avoiding the direct database access
required to fetch bandwidth information. I initially just added
a notify_bw_usage() method to conductor, which just handled the
bandwidth part (which is the database hit). However, the metadata
payload part may be depended upon by custom stuff for periodic
notifications, so copying all that stuff as well made it a bunch
of duplicated stuff. Thus, I decided to just make it a direct proxy
for the compute_utils method.

Note that this is a bit of a departure from the previous pattern of
just proxying db interfaces in conductor, but I think the simplicity
gain is worth it.

Related to blueprint no-db-compute

Change-Id: I09f2652d4903f4d6036c6e3d74db063952341856
2013-02-06 01:27:49 +00:00
bin Merge "fix nova-baremetal-manage version printing" 2013-02-02 14:56:03 +00:00
contrib Enable N302: Import modules only 2013-01-25 12:11:54 -05:00
doc Add REST API to show availability_zone of instance. 2013-02-03 08:57:20 +00:00
etc/nova Add REST API to show availability_zone of instance. 2013-02-03 08:57:20 +00:00
nova Refactor instance usage notifications for compute manager 2013-02-06 01:27:49 +00:00
plugins/xenserver fix misspellings in logs, comments and tests 2013-01-21 23:14:13 +00:00
smoketests Removed print stmts in test cases 2013-01-29 12:55:14 -05:00
tools Fix import for install_venv.py 2013-02-04 10:14:32 -05:00
.coveragerc Use testrepository setuptools support. 2013-01-14 23:17:12 -08:00
.gitignore Ignore auto-generated files by lintstack 2013-01-17 17:27:09 -05:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04:00
.mailmap Add the missing replacement text in devref doc. 2012-12-14 09:47:32 +08:00
.testr.conf Invert test stream capture logic for debugging. 2013-01-07 11:03:30 -08:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
CONTRIBUTING.rst Add a CONTRIBUTING file. 2012-11-21 17:04:48 -05:00
HACKING.rst Update HACKING.rst per recent changes 2013-02-04 11:12:25 +08:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MANIFEST.in Finish AUTHORS transition. 2012-07-05 09:11:37 -05:00
openstack-common.conf import tools/flakes from oslo 2013-01-31 12:29:14 -08:00
pylintrc Don't warn about C0111 (No docstrings) 2011-03-16 15:28:09 -07:00
README.rst Add a CONTRIBUTING file. 2012-11-21 17:04:48 -05:00
run_tests.sh Pass testropts in to setup.py in run_tests.sh 2013-01-30 11:43:43 +11:00
setup.cfg Use testr to run nova unittests. 2012-12-14 14:22:20 -08:00
setup.py Add nova-spicehtml5proxy helper 2013-01-16 10:19:37 +00:00
tox.ini Make sure there are no unused import 2013-01-28 21:37:32 +00:00

README.rst

OpenStack Nova README

OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMWare, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.

OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.

Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.

To keep updated with new developments in the OpenStack project follow @openstack on Twitter.

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

http://docs.openstack.org

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:

http://bugs.launchpad.net/nova

Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:

http://github.com/openstack/nova

Developers should also join the discussion on the mailing list, at:

https://lists.launchpad.net/openstack/

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:

http://nova.openstack.org/

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

-- End of broadcast