Joe Gordon
f364e8ebe3
get_available_resources is actually used by the scheduler while get_host_stats was previously used, and is still used for host capabilities. This patch makes get_available_resources and get_host_stats use the same logic to clean up the code. As part of making them use the same logic, some of the unused data returned from get_host_stats is changed to be what get_available_resources expects. This is also in preparation for removing the periodic RPC fanout from compute nodes to the scheduler. This patch cleans up libvirt and fake drivers only. This is not needed for other virt backends as this is a cleanup only. Further cleanup of libvirt and other drivers will happen after get_host_stats isn't used for the compute fanout to schedulers. Because this makes a change to the fake driver, several api samples needed to be changed as well. The fake driver is changed so the test_virt_driver tests can continue to be used Part of bp no-compute-fanout-to-scheduler Change-Id: I1eec5c117a1cb0490e9f9c09e731909bc31698a9
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 <http://twitter.com/openstack>`_ on Twitter. To learn how to deploy OpenStack Nova, consult the documentation available online at: http://docs.openstack.org For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki: https://wiki.openstack.org/wiki/HypervisorSupportMatrix 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: http://bugs.launchpad.net/nova 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: http://github.com/openstack/nova 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: http://nova.openstack.org/ For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file. -- End of broadcast