Modified onos-cluster.sh to output deployment log into files.
Added functionality of executing command on cluster nodes to onos-cluster.sh.
A few cosmetic changes in onos.sh and onos-cluster.sh.
Change-Id: Ie83774d54ebcd6a9443e767ba298516f68f5f33f
diff --git a/onos.sh b/onos.sh
index 9bc7a3d..b54acc3 100755
--- a/onos.sh
+++ b/onos.sh
@@ -139,9 +139,10 @@
############# Common functions #############
function print_usage {
+ local scriptname=`basename $0`
local filename=`basename ${ONOS_CONF}`
local usage="Usage: setup/start/stop ONOS on this server.
- \$ $0 setup [-f]
+ \$ ${scriptname} setup [-f]
Set up ONOS node using ${ONOS_CONF} .
- generate and replace config file of ZooKeeper.
- create myid in ZooKeeper datadir.
@@ -149,20 +150,20 @@
- generate and replace config file for RAMCloud.
- generate and replace logback.${ONOS_HOST_NAME}.xml
If -f option is used, all existing files will be overwritten without confirmation.
- \$ $0 start [single-node|coord-node|server-node|coord-and-server-node]
+ \$ ${scriptname} start [single-node|coord-node|server-node|coord-and-server-node]
Start ONOS node with specific RAMCloud entities
- single-node: start ONOS with stand-alone RAMCloud
- coord-node : start ONOS with RAMCloud coordinator
- server-node: start ONOS with RAMCloud server
- coord-and-server-node: start ONOS with RAMCloud coordinator and server
* Default behavior can be defined by ${filename}
- \$ $0 stop
+ \$ ${scriptname} stop
Stop all ONOS-related processes
- \$ $0 restart
+ \$ ${scriptname} restart
Stop and start currently running ONOS-related processes
- \$$0 status
+ \$ ${scriptname} status
Show status of ONOS-related processes
- \$ $0 {zk|rc-coord|rc-server|core} {start|stop|restart|status}
+ \$ ${scriptname} {zk|rc-coord|rc-server|core} {start|stop|restart|status}
Control specific ONOS-related process"
echo "${usage}"