f8a238cdee
Updates the Nova test runner so that it enables
'fatal_exception_format_errors' for testing.
Fixes a slew of issues in the tests including:
-adds a whole bunch of missing kwarg's to exception constructors
-removing an extra print statement in ec2/test_cloud
(this was causing failures...)
-removing a duplicate (and misnamed) flavor test case:
test_remove_tenant_access_with_bad_access
-removing an odd test case which tested throwing an exception with
and without kwargs explicitly (the part testing without kwargs was
removed)
-explicitly update test/test_misc.py's test_exceptions_raise to disable
formatting checks for now. This allows it to continue to pass.
Change-Id: Ibb5083c93f1a5de6edadb1b613292ff9eb26ddf0
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:
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:
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