+NOTE: You don't have to be connected to mininet (or another openflow network,
+for that matter) to use this script. If ODL is connected to an openflow
+network, flow_config_blaster will evenly distribute flows across the network.
+If ODL is not connected to a network, flows are only stored in the config
+data store (i.e. nodes that may connect at some point in the future are in
+effect "preconfigured"). The not-connected mode can be used to test the
+performance of the data store and the REST subsystems. The 'nodes' parameter determines how many nodes are used in the non-connected mode.
+
+Examples:
+---------
+To put 5000 flows into ODL running on the same node as the script type:
+ > ./flow_config_blaster.py --flows=5000 --auth --no-delete
+
+To use 5 threads to put 5000 flows into ODL running on the same node as
+the script type:
+ > ./flow_config_blaster.py --threads=5 --flows=1000 --auth --no-delete
+
+ NOTE: each thread will put 1000 flows, and all 5 threads will work
+ simultaneously.
+
+To first put and then delete 5000 flows into ODL running on the same node
+as the script type:
+ > ./flow_config_blaster.py --flows=5000 --auth
+
+To use 5 threads to first put and then delete 5000 flows into ODL running
+on the same node as the script type:
+ > ./flow_config_blaster.py --threads=5 --flows=1000 --auth
+
+ NOTE: 5 threads are used to both add and delete flows
+
+To use 5 threads to first put and then delete 5000 flows into ODL in 10
+add/delete cycles type:
+ > ./flow_config_blaster.py --threads=5 --flows=100 --cycles=10 --auth
+
+ NOTE: 5 threads are used to both add and delete flows.
+
+ NOTE: Both Add and Delete are performed in 10 cycles. 5 worker threads
+ are started in each cycle and the cycle ends when all threads finish.
+ Another cycle is started when the previous cycle finished. Cycles are
+ useful to determine performance degradation with increasing number of
+ flows in the datastore and in the network.
+
+