Regarding bug 1426046 (see below) -- Is this just a matter of making the
classes public or are you thinking the driver interface needs more
thought + solidifying before making something extendable?
Perhaps I can donate a cycle to 2 to help get this in.
On 2/26/15 10:33 AM, Doug Hellmann wrote:
On Thu, Feb 26, 2015, at 07:24 AM, Boden Russell wrote:
What's the suggested approach for implementing a custom oslo messaging
driver given the existing impl [1] is private?
e.g. I want to provide my own notification messaging driver which adds
functionality atop the existing driver [1].
I don't have a public repo -- have been PoCing using a private gitlab to
date... I figured any interest in the driver impl would come out of this
email discussion.
More than happy to provide my PoC code publicly (after a little
clean-up) if there's an interest.
On 2/26/15 12:01 PM, Sandy Walsh
Sent: Thursday, February 26, 2015 2:41 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [oslo.messaging] extending notification
MessagingDriver
Thanks for filing the bug report...
My driver implementation effectively allows you to filter
Thanks for filing the bug report...
My driver implementation effectively allows you to filter on
notification events and multicast matches to a given list of topics.
I've been calling it an messaging multicast notification driver and thus
the plugin stevedore entry point I've called
On Thu, Feb 26, 2015, at 01:41 PM, Boden Russell wrote:
Thanks for filing the bug report...
My driver implementation effectively allows you to filter on
notification events and multicast matches to a given list of topics.
I've been calling it an messaging multicast notification driver
What's the suggested approach for implementing a custom oslo messaging
driver given the existing impl [1] is private?
e.g. I want to provide my own notification messaging driver which adds
functionality atop the existing driver [1]. This can obviously be done
by extending the
