openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
19,042 Commits 10 Branches 94 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
0a93b563e9
Go to file
Rick Harris 0a93b563e9 Harmonize PEP8 checking between tox and run_tests.sh 
Tox and run_tests.sh were running PEP8 checks against different
file-sets. This patch refactors the logic to determine which files to
run PEP8 checks on into `tools/run_pep8.sh` where it can be called by
both tox and `run_tests.sh`.

Additional fixes:

Some of our Python XenAPI Dom0 plugins don't end in *.py but should
still be checked by PEP8. This patches fixes the hacking.py violations
in the files and adds them back to the srcfiles list.

Merged tools/unused_imports.sh into tools/run_pep8.sh

Change-Id: Id5edd1acb644ab938beffc3473494a179d9d8cda
2013-02-15 00:39:58 +00:00
bin Merge "maint: remove unused imports from bin/nova-*" 2013-02-14 04:25:42 +00:00
contrib Enable N302: Import modules only 2013-01-25 12:11:54 -05:00
doc API extension for accessing instance_actions 2013-02-13 14:53:43 -05:00
etc/nova API extension for accessing instance_actions 2013-02-13 14:53:43 -05:00
nova Merge "Allow aggregate create to have None as the az" 2013-02-14 06:03:28 +00:00
plugins/xenserver Harmonize PEP8 checking between tox and run_tests.sh 2013-02-15 00:39:58 +00:00
smoketests Removed print stmts in test cases 2013-01-29 12:55:14 -05:00
tools Harmonize PEP8 checking between tox and run_tests.sh 2013-02-15 00:39:58 +00:00
.coveragerc Update .coveragerc 2013-02-06 16:47:06 +02: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 Module import style checking changes 2013-02-13 17:05:09 +01: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 Update to simplified common oslo version code. 2013-02-10 04:05:15 -06: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 Harmonize PEP8 checking between tox and run_tests.sh 2013-02-15 00:39:58 +00:00
setup.cfg Use testr to run nova unittests. 2012-12-14 14:22:20 -08:00
setup.py Update to simplified common oslo version code. 2013-02-10 04:05:15 -06:00
tox.ini Harmonize PEP8 checking between tox and run_tests.sh 2013-02-15 00:39:58 +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