On 12/17/2015 05:07 PM, Ihar Hrachyshka wrote:
We may probably think of passing agent uuid into extensions to allow it to be used as a cookie for their flows, and make sure extensions are triggered before we reset obsolete flows in the agent. It may work. I would only want to see it as a temporary solution. One thing that I would like to tackle with the proposal is keeping our main flow tables clean from extension specific flows, if anything, for easier debugging.
I agree with you here. Let's pass the uuid as a temporary solution. This will buy us some time to iterate on the extensions flow tables proposal and get it working. In the meanwhile the subprojects that install flows won't be blocked.
cheers, Rossella __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
