On 06/19/2013 05:18 AM, Thierry Carrez wrote: > Mark McLoughlin wrote: >> On Wed, 2013-06-19 at 10:20 +0200, Thierry Carrez wrote: >>> I'd suggest to be a bit careful with that... It's a bit hard to tell >>> whether it's being used, since some parties may take advantage of this >>> plugin framework and we don't really know about them. >>> >>> Maybe ask about anyone using those on the general ML ? Can it be >>> "deprecated" in Havana instead of removed ? >> >> Well, the implication of that would be oslo.messaging supporting an API >> that we won't need in future. >> >> It's not totally clear what our level of support is for external plugins >> like this is. Certainly the API extensions hooks in Nova aren't >> something we've committed to maintaining API stability around. >> >> Which means that this interface is unstable. If you were using it in >> Folsom or Grizzly, you have to be prepared for it to change in Havana. >> >> And the change isn't actually as big a deal as it sounds even for people >> who may we using it - you just register your API extensions via the >> osapi_compute_extension config option and your notification driver via >> the notification_driver config option. There's a very clear migration >> path. > > Fair enough. I would still give a heads-up on the general list to give a > chance to our massive plugin community to show up and complain... but I > agree that it sounds like a good idea. >
All sounds good to me. I'm good with removing it. We can easily add it back if someone speaks up with something we've missed. I've also left a placeholder on the release notes page [1] to make sure we document the change in the upgrade notes. [1] https://wiki.openstack.org/wiki/ReleaseNotes/Havana#Upgrade_Notes -- Russell Bryant _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev