Bug 1041715 - [RFE][cinder]: Allow per-driver utils configs specification
Summary: [RFE][cinder]: Allow per-driver utils configs specification
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/cind...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 18:47 UTC by RHOS Integration
Modified: 2015-11-20 19:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 16:57:55 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 18:47:19 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/per-driver-config-for-utils-functions.

Description:

If we use multi-backend each of backend has its own configuration. In utils functions general configuration is currently used, not the backend one.
We should allow config option to be configurable on a per-driver basis. Drivers should pass config arguments from their own config to utils methods.
For example, we have two backends and these are parameters in the config:

[DEFAULT]
enabled_backends=lvm_big,lvm_small

[lvm_big]
volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver
volume_dd_size=100M

[lvm_small]
volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver
volume_dd_size=1M

So, we have two volume groups, one of them can be cleaned  more effectively using 100M fragments and the second one can be cleaned  more effectively using 1M fragments. After implemenation of this blueprint we will be able to set this parameter for each backend separately and let drivers work more effective.

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.