CI add timeout for k8s+istio deployment

Issue link:
    https://build.opnfv.org/ci/view/clover/job/clover-daily-deploy-master/13/

Clover daily job often failed, which is caused by bad network at utc 12:OO.
(Heavy ci job running in huawei lab at that time.)

Find another time slot for clover daily job.
    https://gerrit.opnfv.org/gerrit/#/c/54589/

Change-Id: I0a9eb3ba0c63a3c440627a7af5afb302dbdaebb5
Signed-off-by: QiLiang <liangqi1@huawei.com>

diff --git a/ci/deploy.sh b/ci/deploy.sh
index 762dc0a..d1f2961 100755 (executable)
--- a/ci/deploy.sh
+++ b/ci/deploy.sh
@@ -13,6 +13,7 @@ CLOVER_BASE_DIR=`cd ${BASH_SOURCE[0]%/*}/..;pwd`
 CLOVER_WORK_DIR=$CLOVER_BASE_DIR/work
 MASTER_NODE_NAME='master'
 SSH_OPTIONS="-o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no"
+K8S_ISTIO_DEPLOY_TIMEOUT=3600
 
 mkdir -p $CLOVER_WORK_DIR
 cd $CLOVER_WORK_DIR
@@ -25,7 +26,7 @@ git clone https://git.opnfv.org/container4nfv/
 cd container4nfv
 
 # Create kubernetes + istio env
-./src/vagrant/kubeadm_istio/deploy.sh
+timeout $K8S_ISTIO_DEPLOY_TIMEOUT ./src/vagrant/kubeadm_istio/deploy.sh
 
 # Fetch kube-master node info
 cd src/vagrant/kubeadm_istio