This sounds like a lot of overlap with the dict extend functions. Why weren't they adequate for the QoS use case? On Mon, Jul 13, 2015 at 7:58 AM, Mike Kolesnik <mkolesni at redhat.com> wrote: > Hi, > > I sent a simple patch to check the possibility to add results to callbacks: > https://review.openstack.org/#/c/201127/ > > This will allow us to decouple the callback logic from the ML2 plugin in > the QoS scenario where we need to update the agents in case the profile_id > on a port/network changes. > It will also allow for a cleaner way to extend resource attributes as > AFTER_READ callbacks can return a dict of fields to add to the original > resource instead of mutating it directly. > > Please let me know what you think of this idea. > > Regards, > Mike > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Kevin Benton -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150713/50a6b466/attachment.html>