OpenStack Compute (Nova)
Go to file
Sean Dague 5632b8dc55 introduce ``stub_out`` method to base test class
We would like to fully remove mox from the test tree. Even for tests
that don't use mox's validation, many of them are using the symbol
patching with self.stubs.Set. We can do the same thing with the
monkeypatch fixture instead.

This introduces self.stub_out to nova/test.py and an example of what a
stubs => stub_out change would look like.

The teardown function in the converted test was removed at the same
time, as those should no longer be used.

Part of bp:remove-mox

Change-Id: I5afc3a45d9ad9c629072891b52cd5625d28b99fc
2016-01-05 11:30:05 -05:00
api-guide/source Merge "Change some wording on server_concepts.rst" 2015-12-15 06:14:37 +00:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
devstack Merge "Remove skips for resize tests from tempest-dsvm-cells-rc" 2015-12-01 06:33:22 +00:00
doc Merge "Remove cells service from api samples that don't test cells" 2015-12-15 20:52:55 +00:00
etc/nova Merge "Fix the bug of "Error spelling of 'explicitely'"" 2015-12-08 23:51:32 +00:00
nova introduce ``stub_out`` method to base test class 2016-01-05 11:30:05 -05:00
plugins/xenserver Merge "Fix a few typos" 2015-09-15 11:24:36 +00:00
releasenotes Merge "Add project-id and user-id when list server-groups" 2015-12-15 01:41:10 +00:00
tools Simplified boolean variable check 2015-11-18 23:45:28 -08:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:34:39 +00:00
.gitignore Merge "Add reno for release notes management" 2015-11-13 16:24:51 +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
.testr.conf Add tox -e functional 2014-11-12 15:31:06 -05:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst add hacking check for config options location 2015-11-26 19:24:19 +01:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Add a maintainers file 2015-05-23 03:22:07 +10:00
README.rst Update links in README 2014-05-07 16:06:24 -07:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bandit.yaml Add bandit for security static analysis testing 2015-07-02 09:17:48 -07:00
openstack-common.conf Switch to the oslo_utils.fileutils 2015-07-24 14:10:44 +03:00
requirements.txt Block requests 2.9.0 2015-12-15 08:38:17 -08:00
run_tests.sh Fix likely undesired use of redirection 2015-02-02 16:26:31 +01:00
setup.cfg Merge "Remove version from setup.cfg" 2015-12-04 00:33:12 +00:00
setup.py Updated from global requirements 2015-09-17 16:41:48 +00:00
test-requirements.txt Updated from global requirements 2015-12-10 12:45:13 +00:00
tests-py3.txt Fixes Python 3 compatibility for filter results 2015-12-10 13:43:40 +02:00
tox.ini Merge "Add a note about fixing "db type could not be determined" with py34" 2015-12-16 16:15:31 +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

For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:

https://wiki.openstack.org/wiki/HypervisorSupportMatrix

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:

https://git.openstack.org/cgit/openstack/nova

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

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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://docs.openstack.org/developer/nova/

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

-- End of broadcast