Decouple cfg handling out of oslo.messaging

Registered by Julien Danjou on 2013-11-18

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 on 2013-11-18

Related branches

Sprints

Whiteboard

Mailing list thread here - http://lists.openstack.org/pipermail/openstack-dev/2013-November/thread.html#19535

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://review.openstack.org/#q,topic:bp/messaging-decouple-cfg,n,z

Addressed by: https://review.openstack.org/59216
    Avoid storing configuration in notifier

Addressed by: https://review.openstack.org/59728
    Remove configuration usage from executors

--

See my thoughts posted here: http://lists.openstack.org/pipermail/openstack-dev/2013-December/021420.html

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

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.