Cinder

Allow per-driver utils configs specification

Registered by Ann Taraday

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.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Ann Taraday
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Sean McGinnis

Related branches

Sprints

Whiteboard

(smcginnis): Marking obsolete as this has been sitting out there for a long time. If this is still needed, please submit a new bp.

Gerrit topic: https://review.openstack.org/#q,topic:bp/per-driver-config-for-utils-functions,n,z

Addressed by: https://review.openstack.org/50917
    Pass per-driver config to copy_volume

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.