From 26c77feddc1d393f21b8030e718d680a84584245 Mon Sep 17 00:00:00 2001
From: Carmela Rubinos <carmela.rubinos@gmail.com>
Date: Tue, 12 Jan 2016 13:03:00 +0100
Subject: [PATCH] Increased timeout value for custom tasks

It happens that depending on the hardware used for deployment,
sometimes it fails because the process reaches the timeout for
midonet-install-api and midonet-install agent custom tasks.

This patch increases this value to avoid it to fail when the physical
resources are slower.

Change-Id: I640a0cf34a68efde6bf1194ac961d6cec8a42c30
---
 tasks.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tasks.yaml b/tasks.yaml
index a856ae8..feefe15 100644
--- a/tasks.yaml
+++ b/tasks.yaml
@@ -97,7 +97,7 @@
   parameters:
     puppet_manifest: puppet/manifests/midonet-install-api.pp
     puppet_modules: puppet/modules:/etc/puppet/modules/
-    timeout: 720
+    timeout: 1440
 
 # Install, configure and run MidoNet agent and remove any other
 # openvswitch package which is not the Kernel module
@@ -108,7 +108,7 @@
   parameters:
     puppet_manifest: puppet/manifests/midonet-install-agent.pp
     puppet_modules: "puppet/modules/:/etc/puppet/modules/"
-    timeout: 720
+    timeout: 1440
 
 # During deployment, openvswitch has created a datapath called `ovs-services`.
 # Stop MidoNet agent, and clean the datapath, and run MidoNet agent again