fa9ad5e358
This fixes a few bugs in recent no-db-messaging commits. There were a few places that I accidentally still used "instance" where I should have used "instance_p", which is the instance converted to primitive types. I noticed the problem looking at smokestack logs. I saw a Qpid traceback that indicated the problem. As an interesting point, systems using Kombu would not have seen this problem. Kombu uses anyjson. Our jsonutils module sets anyjson to go through jsonutils, which will automatically to jsonutils.to_primitive() if needed to serialize an object. Qpid doesn't do json serialization, so it will blow up if it hits a non-primitive type. Yay for testing multiple different configurations to find problems. Part of blueprint no-db-messaging. Change-Id: I3487195110572b7ae9586cfcc618ab7ab28d5017
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 dicussion 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:
Changes to OpenStack Nova should be submitted for review via the Gerrit tool, following the workflow documented at:
-- End of broadcast