48268c73e3
This patch replaces the scheduler's use of GET /resource_providers?resources=XXX with GET /allocation_candidates?resources=XXX. In doing so, we move the interaction with the placement API out of the scheduler driver interface and up into the scheduler manager. This allows us to make fewer changes to the underlying HostManager and SchedulerDriver interfaces and isolate communication with the placement API in a single place. The provider_summaries part of the response from GET /allocation_candidates is used to generate the UUIDs that winnow the number of compute nodes retrieved by the filter scheduler during scheduling. Following patches will add in support for actually doing the claim from the scheduler against one or more resources providers by examining the allocation_requests part of the HTTP response and picking one that contains the host the scheduler picked during its _schedule() loop. Change-Id: I1c0bd2987dcbc38f23b71db2bc8e3267f85168c8 blueprint: placement-allocation-requests
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:
https://developer.openstack.org/api-guide/compute/ https://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
https://www.openstack.org/appdev/ https://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:
https://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: