7e7ec7337c
This patch implements hard affinity and anti-affinity filter for
manila scheduler. Users can specify affinity/anti-affinity share
ids to the field "share.scheduler_hints.same_host" or
"share.scheduler_hints.different_host" in the request payload
when creating a manila share. The scheduler_hints are stored as
share metadata. The filter properties are populated from this
metadata during share migration and so filters will be applied
for share migration as well.
Both fields can be a single share UUID or multiple uuids
separated by comma. For example,
`{
"share": {
"scheduler_hints": {
"same_host": "share_uuid_1,share_uuid_2",
"different_host": "share_uuid_3"
}
}
}`
Implements: bp/affinity-antiaffinity-filter
Change-Id: Ic42d8a0c1d22e77ae64e0ca014607b28fd336467
Co-authored-by: Maurice Escher <maurice.escher@sap.com>
15 lines
744 B
YAML
15 lines
744 B
YAML
---
|
|
features:
|
|
- Add AffinityFilter and AntiAffinityFilter to manila's scheduler.
|
|
These hard affinity and anti-affinity filter needs user to specify
|
|
affinity/anti-affinity share ids to the field
|
|
"share.scheduler_hints.same_host" or
|
|
"share.scheduler_hints.different_host" in the request payload when
|
|
creating a manila share. The hints are stored as share metadata. The
|
|
filter properties are populated from this metadata during share
|
|
migration and so filters will be applied when migrating a manila share.
|
|
upgrade:
|
|
- To add AffinityFilter and AntiAffinityFilter to an active deployment,
|
|
their references must be added to the manila.scheduler.filters section in
|
|
setup.cfg and must be enabled in manila.conf.
|