In this use case, 100k flows are programmed into a simulated network (mininet) with 15 nodes. Then, all 100k flows are deleting by clearing out the confi space. 20-30k flows are left in the network.

To reproduce, use the following steps:

1. Start mininet using the following command:

"sudo mn --controller=remote,ip=192.168.162.1:6633 --topo tree,4 --switch ovsk,protocols=OpenFlow13"

Let mininet connect to the controller

2. From another shell, use the flow_config_blaster script (located in the integration test project under 'test/tools/odl-mdsal-clustering-tests/clustering-performance-test') to program 100k flows into the controller:

./flow_config_blaster.py --threads 8 --flows 12500 --auth --no-delete --fpr 200

3. In the mininet test VM, use a script to make sure that all 100k flows have been programmed into the network:

/bin/get-total-found.sh

(or something similar); make sure all 100k flows have been injected into mininet. You may also check the controller's REST API, but collecting all the 100k flows takes a long time (> 10 minutes).

4. Use the config_cleanup script (alos located in 'test/tools/odl-mdsal-clustering-tests/clustering-performance-test') to delete all 100k flows at once:

./config_cleanup.py --auth

5. In the mininet test VM, use a script to check whether all flows have been deleted from the switches:

/bin/get-total-found.sh

The flow counts should now be 0 on all switches. Dangling flows can found, however.