fdf27abf7d
Using wsgi_intercept to run the placement API in the PlacementFixture, instead of spawning an eventlet server. This should help with the weird situation where sometimes requests that are supposed to go to compute or placement go to the other. Some combination of six or wsgi-intercept is not happy with the use of socket_options in the keystoneauth1.session.TCPKeepAliveAdapter, so a MonkeyPatch is used to skip over it and use the parent Adapter. The change here continues to monkeypatch the report client so that we don't have to monkey patch keystone's auth and endpoint handling. We don't want that as it will also patch the nova side of things. Change-Id: I03b3abea152d45575ac6dde22ccbe32b6acb4646 Related-Bug: #1705753
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer and OpenStack Ironic.
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.
API
To learn how to use Nova's API, consult the documentation available online at:
https://developer.openstack.org/api-guide/compute/ https://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
https://www.openstack.org/appdev/ https://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
https://docs.openstack.org/developer/nova/feature_classification.html
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.
Further developer focused documentation is available at: