Shared backend config stanza
We don't have a nice way for backends to share common config parameters. Infact... we have a somewhat confusing model right now. As an example consider something like:
[DEFAULT]
enabled_backends = backend1, backend2
...
my_driver_param = foo
...
[backend1]
...
my_driver_param = bar
[backend2]
..
(not specifying the param)
Generally this is confused as thinking that backend1 will get 'bar' and backend2 will get 'foo' since its in the default section, unfortunately that 'foo' setting is completely ignored and backend2 gets whatever the default setting was for the driver.
The idea then is to be able to do something like:
[DEFAULT]
...
[common-
my_driver_param = foo
[backend1]
...
my_driver_param = bar
[backend2]
..
(not specifying the param)
[backend3]
...
(also not specifying, maybe even a different volume driver... doesn't matter)
And the result being that backend2 and backend3 get 'foo', and backend1 gets its 'bar' value where it overwrote the shared one.
Blueprint information
- Status:
- Complete
- Approver:
- Sean McGinnis
- Priority:
- Medium
- Drafter:
- Patrick East
- Direction:
- Approved
- Assignee:
- Patrick East
- Definition:
- Approved
- Series goal:
- Accepted for pike
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Eric Harney
- Completed by
- Eric Harney
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Shared backend config stanza
Addressed by: https:/
Deprecate defining c-vol backends in DEFAULT
Addressed by: https:/
Add support for shared "backend_defaults" config
Addressed by: https:/
Don't merge - demo showing DEFAULT as a shared conf