wujun 1471eba89d Modify an order between iptables and conntrack when update firewall ... When update a firewall, we should update the iptables firstly, and then remove the conntrack record, just like the function create_firewall() and create_firewall_group(). Otherwise, the contrack record could be reproduced. It will be occurred more easily in scenario of large flow, because removing conntrack and updating firewall will take some time, and in this interval the subsequent flow could be came to reproduced the same conntrack record. Change-Id: I7bd36964199c6ce7c146f3ef06a693e9c6fe5353 Closes-bug: #1696093		2017-06-08 01:34:42 +00:00
..
common	FWaaS v2 utilize L3 Agent Extension framework	2016-09-01 17:34:08 +00:00
db	Merge "Optimize _make_firewall_group_dict_with_rules" into stable/newton	2017-03-10 06:46:12 +00:00
extensions	FWaaS v2 utilize L3 Agent Extension framework	2016-09-01 17:34:08 +00:00
services	Modify an order between iptables and conntrack when update firewall	2017-06-08 01:34:42 +00:00
tests	tempest: Switch to local copy of tempset/scenario/manager.py	2017-03-14 16:10:46 +09:00
__init__.py	py34: Fix usage of gettext.install	2015-07-28 16:29:59 +00:00
_i18n.py	Update translation setup	2016-01-29 07:09:03 +09:00
opts.py	FWaaS quota registration	2016-02-13 19:17:43 -08:00
version.py	After the services split, get neutron-fwaas Jenkins jobs passing	2014-12-09 00:00:29 -07:00