cinder/releasenotes/notes/add-operation-to-request-spec-7yt6ub75uy1284as.yaml
TommyLike e1ec4b4c2e Support filter backend based on operation type
During Rocky PTG, we discussed the concept of
'sold out'. In order to fully utilize
current codes, we decided to achieve this via
scheduler filters, cloud vendors can write their own
scheduler filter plugin to disable new resource
creation actions on sold out pools. Therefore, the
only change on cinder framework side is to delivery
'operation' when asking scheduler to filter hosts.

For this first stage, the initial operations are:
1. create_group
2. manage_existing
3. extend_volume
4. create_volume
5. create_snapshot
6. migrate_volume
7. retype_volume
8. manage_existing_snapshot

Partial-Implements: bp support-mark-pool-sold-out
Change-Id: I4f0a14444675ebd0fe6397a5ff2ef9dca62b4453
2018-05-07 17:58:36 +08:00

16 lines
453 B
YAML

---
features:
- |
Now scheduler plugins are aware of operation type via ``operation`` attribute in
RequestSpec dictionary, plugins can support backend filtering according to backend
status as well as operation type. Current possible values for ``operation`` are:
- create_volume
- extend_volume
- create_snapshot
- retype_volume
- migrate_volume
- manage_existing
- manage_existing_snapshot
- create_group