2dc5d9f863
This removes the run_tests.sh script, replacing it with documentation on how to use tox itself for testing nova things, as well as links to learn more about both that, and how to not use tox at all if you really care. Why should we do this? New people coming to the project see a file called run_tests.sh and use it, because why would you have a file like that in the top of your directory if that wasn't what you were supposed to use. However it's not what we want anyone using for upstream contributions. One of the critical differences between it and tox is that it lacks ``python hashseed randomization``. This runs every test run with a different forced hashseed, that exposes bugs in tests early. Test contributors need to be running that on their tests before submission to shake out these errors early. In addition, because we have multiple ways in tree to run tests, helping people debug their test failures means we have to start at a step -1 of "how are you running tests". This adds load for helping new folks. What about people that want to run tests with specific system or virtual env python setups for pre deployment testing? Good news! Our tests comply to python standard testing interfaces, so are runnable by any test runner (we recommend ``testr`` because that's what tox calls under the covers). You can just run ``testr run`` at the top level from your virtuenv or system of choice. And life is good. The constraints we need / want for inbound tests don't apply in these cases. This removes a bit of confusion for new contributors, ensures that new test contributions receive correct local testing before they are run in our gate, and only require a very minor change in behavior for downstream test environments. Change-Id: I05d85a15c0db2a573abb82cb2f7dc3eeaeac0b41
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:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
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 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:
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:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast