which was the point with uing make in the first place
so that maximum degree of parallelism can be reached
+**********************************************************
+Note: to get the greatest speedup from make -j you should also enable
+connection reuse in your ssh setup, e.g., by having the following lines
+in your .ssh/config:
+host *
+ ControlMaster auto
+ ControlPath ~/.ssh/ssh_mux_%h_%p_%r
+ ControlPersist 4h
+
+Please note, however, that maximum concurrent per-node reuse is usually
+set to something low (typically 10), and this is a problem if some node
+in your topology has many links. In this case you should raise that limit
+on the slivers, or limit makefile concurrency (e.g., by using make -j10).
+**********************************************************
+
==================== usual target
make [init+all]
shortcut for 'make init all'
make controllers
configure the various switches so they use the configured controllers
+make del-controllers
+ reset the switches to run in standalone mode
==================== devel
make update
push a new version of sliver-ovs into the slivers
make status
list status of db and switch processes in all slivers
====================
+make gprobes
+ Uses GMAP_SERVER and GMAP_PROBES to run probes in selected slivers
+ that can update a googlemap server for animating link speeds
+ This of course is mostly a demo thing, based on a one-host ndnmap deployment for now
+====================