d3bf010d3d
We plan to allow PUT requests to create/update both custom traits and custom resource classes, without bodies. Prior to this change, the code would not all a PUT, POST or PATCH to not have a body. This was added in I6e7dffb5dc5f0cdc78a57e8df3ae9952c55163ae which was fixing an issue with how webob handles exceptions. This change does two things: * It address the problem from bug #1623517, fixed in the change id'd above, in a more narrow fashion, making sure the data source that causes the KeyError is non-empty right before it is used. This allows simplifying the following change. * If a request has a content-length (indicating the presence of a body), verify that there is also a content-type. If not, raise a 400. basic-http.yaml has been change to modify one gabbi test to check a response body is correct and to add another test to confirm that the code that is doing the content-length check is passed through. Change-Id: Ifb7446fd02ba3e54bbe2676dfd38e5dfecd15f98 Closes-Bug: #1674392 Related-Bug: #1623517
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:
http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
http://www.openstack.org/appdev/ http://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:
http://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: