Adding thin_pools (or) thin_pool_list , thick_pools (or) thick_pool_list in cinder.conf
I would like to learn from other members, the problem which I faced and was trying to address; it might be helpful for others as well. Please review and suggest!
To segregate or provide the option for configuring the pools which is to be used for thin or thick
Use Case:
To segregate or provide the option for configuring the pools which is to be used for thin or thick
Description:
When the Storage driver wants to support multiple pools, when reported using the get_volume_stats() using the
thin_provisioni
thick_provision
And capabilities in the extra specs having two volume types for thin and thick
I think there should be an optional parameter to configure which pool should support thin and thick respectively (or one can be default).
Proposed Solution:
To have a parameter(s) in the cinder.conf
Example:
thin_pool_list (or) thin_pools
thick_pool_list (or) thick_pools
If needed both (or) any one of it (where other will be obvious)
Impact:
• Since optional parameter whoever has the limitation (from storage API) or use case only they will make use of this
• If provided driver with help of check_setup_error can validate weather pool exists, if not it’s a discretion of driver to handle weather to create a new or throw error.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Dilip S M
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Sean McGinnis
Whiteboard
This is not something we want to add to cinder.conf.