shenjiatong 90212b12cd Do not block connection between br-int and br-phys on startup ... Block traffic between br-int and br-physical is over kill and will at least 1. interrupt vlan flow during startup, and is particularly so if dvr enabled 2. if let's rabbitmq is not stable, it is possible data plane will be affected and vlan will never work. Using openstack on k8s particularly amplifies the problem because pod could be killed pretty easily by liveness probes. Change-Id: I51050c600ba7090fea71213687d94340bac0674a Closes-Bug: #1869808		2020-06-18 20:50:24 +08:00
..
common	Add accepted egress direct flow	2020-01-10 22:50:02 +08:00
extension_drivers	Add OVS QoS driver cache for minimum bandwidth rules	2020-01-07 14:40:28 +00:00
openflow	Remove some native openflow driver 'deferred' code	2020-04-20 10:55:10 -04:00
__init__.py	Restructure agent code in preparation for decomp	2015-06-26 15:06:49 +00:00
main.py	Drop of_interface option	2019-05-24 10:33:48 +02:00
ovs_agent_extension_api.py	Make "phys_brs" argument in OVSAgentExtensionAPI optional	2019-03-05 15:59:00 +00:00
ovs_capabilities.py	Add agent-side driver scaffolding for trunk functionality	2016-08-18 12:10:22 +00:00
ovs_dvr_neutron_agent.py	Add accepted egress direct flow	2020-01-10 22:50:02 +08:00
ovs_neutron_agent.py	Do not block connection between br-int and br-phys on startup	2020-06-18 20:50:24 +08:00
vlanmanager.py	Change provider network segmentation ID in OVS agent	2019-05-20 18:53:17 +00:00