Decouple cfg handling out of oslo.messaging
The goal of this blueprint is to be able to use oslo.messaging without using a configuration file/object, while keeping its usage possible and not breaking compatibility with OpenStack applications.
Blueprint information
- Status:
- Started
- Approver:
- Mark McLoughlin
- Priority:
- Undefined
- Drafter:
- Julien Danjou
- Direction:
- Needs approval
- Assignee:
- Julien Danjou
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
- Started
- Milestone target:
- None
- Started by
- Julien Danjou
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Mailing list thread here - http://
I'm removing this from the icehouse series for the moment - I think from the various discussions in reviews and such, we've a ways to go before there's a clear plan for this -- @markmc
Gerrit topic: https:/
Addressed by: https:/
Avoid storing configuration in notifier
Addressed by: https:/
Remove configuration usage from executors
--
See my thoughts posted here: http://
Summary is that the goal of being able to use oslo.messaging with just a dict of options makes a tonne of sense to me, but we can do that quite easily without fundamentally changing how oslo.messaging uses oslo.config.
-- @markmc