Manage volume pools for backends

Registered by Sang Tran

Problem statement:
In case of one volume driver backend can have many volume pools. Openstack cinder has lack option for managing how the volume will be placed on which pool. Currently, cinder will determine cinder pool mostly relying on the stats of each pool (eg. utilization, oversubscription)

Proposal:
Can set properties for the cinder pool and cinder will use these options in the volume-creating progress.
 E.g.
- Can set priority pool
- Can enable/disable pool
...

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Sang Tran
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.