352c9809b4
Currently updates to security group rules or membership are handled by immediately triggering a call to refresh_firewall. This call is quite expensive, and it is often executed with a very high frequency. With this patch, the notification handler simply adds devices for which the firewall should be refreshed to a set, which will then be processed in another routine. The latter is supposed to be called in the main agent loop. This patch for 'provider updates' simply sets a flag for refreshing the firewall for all devices. In order to avoid breaking other agents leveraging the security group RPC mixin, the reactive behaviour is still available, and is still the default way of handling security group updates. Partial-Bug: #1253993 Partially implements blueprint: neutron-tempest-parallel Change-Id: I1574544734865506ff5383404516cc9349c16ec4 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_agent_scheduler.py | ||
| test_openvswitch_plugin.py | ||
| test_ovs_db.py | ||
| test_ovs_defaults.py | ||
| test_ovs_lib.py | ||
| test_ovs_neutron_agent.py | ||
| test_ovs_rpcapi.py | ||
| test_ovs_security_group.py | ||
| test_ovs_tunnel.py | ||