Open Stack

----- Original Message -----
> From: "Gary Kotton" <gkotton at redhat.com>
> To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org>
> Sent: Tuesday, November 6, 2012 2:47:29 AM
> Subject: [openstack-dev] [Common] Rename rabbit_notifier to rpc_notifier.
> 
> 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?

In the patches to openstack-common and Quantum we actually kept the rabbit_notifier driver file and made it use the new generic rpc_driver (while also logging a deprecation message). See:

https://review.openstack.org/#/c/15441/2/openstack/common/notifier/rabbit_notifier.py

Once we cut Grizzly I think the old rabbit driver can be safely dropped. So long as other projects take care to include both drivers (rpc and rabbit) I think the upgrade path should be smooth.


> Thanks
> Gary
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>