03bc8b6a6b
This patch collects the resource requests from each neutron port involved in a server create request. Converts each request to a RequestGroup object and includes them in the RequestSpec. This way the requests are reaching the scheduler and there they are included in the generation of the allocation_candidates query. This patch only handles the happy path of a server create request. But it adds couple of TODOs to places where the server move operations related code paths need to be implemented. That implementation will be part of subsequent patches. Note that this patch technically makes it possible to boot server with one neutron port that has resource request. But it does not handle multiple such ports or SRIOV ports where two PFs are supporting the same physnet as well as many server lifecycle operations like resize, migrate, live-migrate, unshelve. To avoid possible resource allocation inconsistencies due to the partial support nova rejects any requests that involves such ports. See the previous patches in this patch series for details. Also note that the simple boot cases are verified with functional tests and in those tests we need to mock out the above described logic that reject such requests. See a more background about this approach on the ML [1]. [1] http://lists.openstack.org/pipermail/openstack-discuss/2018-December/001129.html blueprint bandwidth-resource-provider Change-Id: Ica6152ccb97dce805969d964d6ed032bfe22a33f
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, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure 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
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:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: