ae96eccfbd
Make compute_capabilities_filter directly use the data in host_state and not the data capabilities data that is currently broadcast from the schedulers over RPC, as this will be removed since it doesn't scale. The filter name, compute_capabilities_filter, is kept the same to keep backwards compatibility. This is a second attempt at this patch the first one broke the ability to filter an arbitrary key value pairs, this time that is supported via host_state.stats, along with tests to confirm Once all the capabilities usage in scheduler filters is removed, the capabilities RPC broadcast can be removed. Part of bp no-compute-fanout-to-scheduler. Change-Id: I0b9b05a25a8c1841093913c4a2fb19b48aff2ae1
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:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
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:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
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