46ba7e8df5
This deprecates the TypeAffinityFilter. This filter, which is really an anti-affinity filter for flavors, attempts to ensure that no two flavors show up on the same host. However, to do this it relies on the flavors.id primary key, which is subject to "change" if/when the admin deletes and recreates a flavor (this is how Horizon allows you to 'edit' a flavor). When you do that, you have a new flavor with a new id primary key and the filter will not know the difference. So you could really end up with more than one m1.large instance on the same host, which defeats the purpose of the filter. This filter is also problematic for blueprint put-host-manager-instance-info-on-a-diet because in that blueprint we want to stop sending full instance objects over RPC from all compute services to the scheduler just to track affinity and anti-affinity. All we really need for the ServerGroupAffinityFilter and ServerGroupAntiAffinityFilter is the list of instance uuids on a host, not the full object. If we can get rid of TypeAffinityFilter, we can change the compute<>scheduler RPC calls to just pass the list of instance uuids for update_instance_info rather than sending an InstanceList. Change-Id: I660e0316b11afcad65c0fe7bd167ddcec9239a8b
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: