Add user defined extra capabilities
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Low
|
Tom Fifield | ||
openstack-manuals |
Fix Released
|
Low
|
Unassigned |
Bug Description
https:/
commit 9bcd7285b575cdc
Author: Ollie Leahy <email address hidden>
Date: Thu Jan 9 15:14:11 2014 +0000
Add user defined extra capabilities
Provide a mechanism that will allow sys admins who are managing cinder
installations with multiple backends to assign key/value pairs to
backends. The key/value pairs can be used by the capabilities scheduler
to select between backends when requests specify volume types.
For example a sysadmin could specify the key 'service_level' with the
values 'high', 'medium' and 'low' for different backends. The sys admin
specifies the 'service_level' for each backend in cinder.conf as a json
string, for example:
extra_
or
extra_
DocImpact
Implements: blueprint admin-defined-
Change-Id: I1ee9dcb22b3f09
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in openstack-manuals: | |
assignee: | nobody → Stephen Gordon (sgordon) |
Changed in openstack-manuals: | |
assignee: | Stephen Gordon (sgordon) → nobody |
Changed in cinder: | |
importance: | Undecided → Low |
Changed in cinder: | |
milestone: | none → kilo-2 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | kilo-2 → 2015.1.0 |
Changed in openstack-manuals: | |
milestone: | kilo → liberty |
Changed in openstack-manuals: | |
milestone: | liberty → mitaka |
Changed in openstack-manuals: | |
status: | Triaged → Fix Released |
The config option itself is documented in doc/common/ tables/ cinder- api.xml, do we need further documentation or is this enough?