![ghanshyam](/assets/img/avatar_default.png)
This includes 2 classes of fixes (and 1 skip) for mock. The first is the change in allowed values for assert_has_calls - https://github.com/testing-cabal/mock/issues/263 The second is a yet unsolved bug around the use of autospec https://github.com/testing-cabal/mock/issues/264 The skip is because something has changed with mock.open that is causing the vhduils test to fail. We don't know why, but it's one test to skip. This also includes a brute force fix for tox -e docs, because pip is no longer respecting the sphinx pin in test requirements. This has to be landed with the other changes because they won't work without it. Change-Id: Id835d080a1ada52cbd3f24dad9bab5eeb2f29a54 Partial-Bug: 1473401
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