5bf4365c6f
Right now, we always join metadata and system_metadata when we query for instances. This inflates the number of rows returned by a factor of ten at a minimum, and over 30 in some situations. This patch avoids the direct join of these tables in favor of a "manual join" which performs additional queries to fill the needed data. Latency may be increased, but with the gain of a potentially significant amount of reduction in data transfer. This also provides the ability for the queries which utilize it to selectively decide whether either or both of these additional fills are performed, paving the way for future high-level optimizations. Related to bug 1164737 Change-Id: I0610fb16ccce2ee95c318589c8abcc30613a3fe9
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 discussion 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:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast