This move is needed so that we can define a per service default for monkey patching. And yes, the single line with both noqa and autopep8 decorators are needed to convince autopep8 that this code is OK to be at the start of the file. After moving the monkey_patching earlier in the wsgi entrypoint I needed to move the functional test monkey_patching call earlier too to keep the early enough for the test where the wsgi entry point is not directly imported Change-Id: Idedd2a440adc1cde1e8ffe6636854d5a891e66d2 Signed-off-by: Balazs Gibizer <gibi@redhat.com>
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), VMware and OpenStack Ironic.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure 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
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
To understand better the processes that the team is using, please refer to the Process document.
Further developer focused documentation is available at:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: