[ARVADOS] updated: 28467b488760dbf7385cc5001b154f9220982a62

[git at public.curoverse.com]

Summary of changes:
 services/nodemanager/doc/gce.example.cfg | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

       via  28467b488760dbf7385cc5001b154f9220982a62 (commit)
      from  37916fadb45b240c0731a328ddc153b723959ad3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit 28467b488760dbf7385cc5001b154f9220982a62
Author: Brett Smith <brett at curoverse.com>
Date:   Tue Feb 17 10:42:47 2015 -0500

    4138: Fixup GCE shutdown window docs.

diff --git a/services/nodemanager/doc/gce.example.cfg b/services/nodemanager/doc/gce.example.cfg
index 9464075..7e7813c 100644
--- a/services/nodemanager/doc/gce.example.cfg
+++ b/services/nodemanager/doc/gce.example.cfg
@@ -72,12 +72,12 @@ provider = gce
 # then it WILL NOT shut down for N3 minutes; and so on.  For example,
 # "54, 5, 1" means the node may shut down from the 54th to the 59th
 # minute of each hour of uptime.
-# GCE bills by the minute, and does not provide information about
-# when a node booted.  Because of that, Node Manager will pretend a
-# node booted when it's first seen by the process.  To help
-# counterbalance that, these shutdown settings are very aggressive.
-# You may want to adjust this if you want more continuity of service
-# from a single node.
+# GCE bills by the minute, and does not provide information about when
+# a node booted.  Node Manager will store this information in metadata
+# when it boots a node; if that information is not available, it will
+# assume the node booted at the epoch.  These shutdown settings are
+# very aggressive.  You may want to adjust this if you want more
+# continuity of service from a single node.
 shutdown_windows = 20, 999999
 
 [Cloud Credentials]

-----------------------------------------------------------------------


hooks/post-receive
--