ed3c69cb45
Deprecated in Pike: I660e0316b11afcad65c0fe7bd167ddcec9239a8b This filter relies on the flavor.id primary key which will change as (1) flavors were migrated to the API database and (2) when a flavor is changed by deleting and re-creating the flavor. Also, as noted in blueprint put-host-manager-instance-info-on-a-diet, this is one step forward in getting us to a point where the only thing that the in-tree filters care about in the HostState.instances dict is the instance uuid (for the affinity filters). Which means we can eventually stop RPC casting all instance information from all nova-compute services to the scheduler for every instance create, delete, move or periodic sync task - we only would need to send the list of instance UUIDs. That should help with RPC traffic in a large and busy deployment. Change-Id: Icb43fe2ef5252d2838f6f8572c7497840a9797a1
12 lines
613 B
YAML
12 lines
613 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The ``TypeAffinityFilter``, which was deprecated in the 16.0.0 Pike
|
|
release, has been removed. The filter was flawed in that it relied on the
|
|
flavor ``id`` primary key which cannot be relied upon since you cannot
|
|
"edit" a flavor to change its disk, vcpu, etc values. Therefore to change
|
|
a given flavor, it must be deleted and re-created, which means a new ``id``
|
|
value, thus potentially breaking the usefulness of the filter. Also, the
|
|
flavor migration from the ``nova`` database to the ``nova_api`` database
|
|
would also have resulted in different ``id`` values.
|