Open Stack

On Tue, 2012-11-06 at 08:23 -0500, Russell Bryant wrote:
> On 11/06/2012 07:38 AM, Mark McLoughlin wrote:
> > On Tue, 2012-11-06 at 09:47 +0200, Gary Kotton wrote:
> >> Hi,
> >> The change is cool and understood. My concern here is that if someone 
> >> has deployed Folsom, when they upgrade to Grizzly then the code will be 
> >> broken. In the original configuration the the entry was:
> >> notification_driver =quantum.openstack.common.notifier.rabbit_notifier
> >> This has now been changed to:
> >> notification_driver =quantum.openstack.common.notifier.rpc_notifier
> >> Is this something that needs to be taken care of internally by Quantum 
> >> or something across OpenStack?
> > 
> > Yeah, it would be nice if we had support for the Folsom configuration
> > 
> > If we used entry points for loading these drivers, we could set up an
> > alias like in this proposed patch:
> > 
> >   https://review.openstack.org/15030
> 
> What am I missing here?  The patch that went in still supports
> specifying rabbit_notifier.  There is a rabbit_notifier module that just
> acts as a pass-through to the rpc_notifier.
> 
> https://review.openstack.org/#/c/15441/

Ah, it's me missing something. That's fine, my bad :)

Thanks,
Mark.