243ba85130
The time has come. These filters haven't been necessary since Ocata [1] when the filter scheduler started using placement to filter on VCPU, DISK_GB and MEMORY_MB. The only reason to use them with any in-tree scheduler drivers is if using the CachingScheduler which doesn't use placement, but the CachingScheduler itself has been deprecated since Pike [2]. Furthermore, as of change [3] in Stein, the ironic driver no longer reports vcpu/ram/disk inventory for ironic nodes which will make these filters filter out ironic nodes thinking they don't have any inventory. Also, as noted in [4], the DiskFilter does not account for volume-backed instances and may incorrectly filter out a host based on disk inventory when it would otherwise be OK if the instance is not using local disk. The related aggregate filters are left intact for now, see blueprint placement-aggregate-allocation-ratios. [1] Ie12acb76ec5affba536c3c45fbb6de35d64aea1b [2] Ia7ff98ff28b7265058845e46b277317a2bfc96d2 [3] If2b8c1a76d7dbabbac7bb359c9e572cfed510800 [4] I9c2111f7377df65c1fc3c72323f85483b3295989 Change-Id: Id62136d293da55e4bb639635ea5421a33b6c3ea2 Related-Bug: #1787910
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: