tree 53cf419a348058a547782a9d7577875de727bd83
parent 2af9eaaf219ceb606ea0d192a3ce947b3007fead
author Yuta HIGUCHI <y-higuchi@ak.jp.nec.com> 1486077732 -0800
committer Yuta HIGUCHI <y-higuchi@onlab.us> 1486516772 +0000

Option to use rsync pushing bits

Use rsync to push bits (ONOS tar contents), when
environment variable USE_RSYNC is set to true.
This enables sending only changed .jar, now whole ONOS tar ball.

+ Minor optimization to reuse build machine to remote host ssh session

push bits:
 1) unpackage ONOS tar to tmp stage dir
 2) rsync local stage to remote stage /tmp/$ONOS_BITS
 3) package ONOS tar equivalent at remote node

push bits via proxy:
 1) rsync: build <=> proxy
 2)  scp :           proxy => cell nodes (tar packaged at proxy)
 3) rsync: build <==========> cell nodes (almost no-op)

Known limitation:
- rsync at Step 3 is triggered since
  repackaging same content remotely result in
  tar ball with different hash value.
  (Probably due to directory timestamp/uid difference)
- automatically installing rsync
  only supported for debian/ubuntu

Change-Id: Ibc9013b973c312798d2c36e7d25f5274f085b39f