My only concern is how tightly coupled the FwaaS code is with the L3 agent. We have a bug already filed because the L3 agent inheriting the FwaaS code causes circular dependencies, but it also be the reason why FwaaS co-gates with the main Neutron repo. Let's try and fix the tight coupling of the L3 agent with the FwaaS code so we can get FwaaS to just gate by itself. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151020/f6655329/attachment.html>