Brian Haley 65a81623fc Process conntrack updates in worker threads
With a large number of instances and/or security group rules,
conntrack updates when ports are removed or rules are changed
can take a long time to process.  By enqueuing these to a set
or worker threads, the agent can continue with other work while
they are processed in the background.

This is a change in behavior in the agent since it could
program a new set of security group rules before all existing
conntrack entries are deleted, but since the iptables or OVSfw
NAT rules will have been removed, it should not pose a
security issue.

Change-Id: Ibf858c7fdf7a822a30e4a0c4722d70fd272741b6
Closes-bug: #1745468
2018-02-06 12:25:59 -05:00
2016-06-28 22:46:19 +02:00
2016-10-17 17:06:19 +05:30
2014-05-16 13:40:04 -04:00
2018-01-31 22:54:45 -08:00
2017-06-13 19:26:49 +00:00
2017-08-31 16:44:51 +02:00
2017-08-03 09:47:25 +08:00
2018-01-09 09:26:40 +07:00
2017-03-04 11:19:58 +00:00

Team and repository tags

image

Welcome!

To learn more about neutron:

Get in touch via email. Use [Neutron] in your subject.

To learn how to contribute:

CONTRIBUTING.rst

Description
OpenStack Networking (Neutron)
Readme 1,018 MiB
Languages
Python 99.7%
Shell 0.3%