From 5b7934654b15bae9c18e440f4e72ddee95917bb4 Mon Sep 17 00:00:00 2001
From: Sean Dague <sean.dague@samsung.com>
Date: Fri, 7 Mar 2014 06:29:44 -0500
Subject: [PATCH] offset nodepool update by 12 hrs

the theory that updating nodepool in the middle of the night to not be
disruptive runs afoul of the fact that if they do, there isn't anyone
around to fix them (due to when infra-root working hours are).  The
net being that half a day of development is lost, asia and europe lose
most of their day, until the first infra root member is up and can
trigger a roll back.

given that the infra team is largely centered on west coast if we
update this at 14 UTC instead of 2 UTC that means any issues will
surface while the entire infra team is on. Which means the ability
to catch these early.

Change-Id: I515bcd401ad09dcec405cd13dcb1f5652e10b2dc
---
 modules/openstack_project/templates/nodepool/nodepool.yaml.erb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/openstack_project/templates/nodepool/nodepool.yaml.erb b/modules/openstack_project/templates/nodepool/nodepool.yaml.erb
index cab9e6bfb9..054a99875a 100644
--- a/modules/openstack_project/templates/nodepool/nodepool.yaml.erb
+++ b/modules/openstack_project/templates/nodepool/nodepool.yaml.erb
@@ -4,7 +4,7 @@ dburi: 'mysql://nodepool:<%= mysql_password %>@localhost/nodepool'
 cron:
   cleanup: '*/1 * * * *'
   check: '*/15 * * * *'
-  update-image: '14 2 * * *'
+  update-image: '14 14 * * *'
 
 zmq-publishers:
   - tcp://jenkins01.openstack.org:8888