Description of problem:
In case when on one compute node there is many ports which are using same security group and this security group uses rule to allow traffic from ports with given SG adding new port to host is very slow.
We tested it on compute with 170 trunk supports and it took about 5 minutes for new port to become ACTIVE.

In environment with OpenShift deployed on top of OpenStack 170 subports isn't a lot. It has to scale for much higher numbers.


How reproducible:
Always


Steps to Reproduce:
1. Create a lot of ports/trunk subports which uses same SG on one compute node
2. Add new port/subport to this compute after some time

Actual results:
New port will become active after couple of minutes as all existing ports will be "updated" due to changes in SG


Expected results:
Port should be ACTIVE almost immediately.

Additional info: