Author: buildbot
Date: Wed Jan  6 15:58:35 2016
New Revision: 977158

Log:
Staging update by buildbot for slider

Modified:
    websites/staging/slider/trunk/content/   (props changed)
    websites/staging/slider/trunk/content/developing/releasing.html
    
websites/staging/slider/trunk/content/docs/slider_specs/application_pkg_upgrade.html

Propchange: websites/staging/slider/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jan  6 15:58:35 2016
@@ -1 +1 @@
-1722987
+1723354

Modified: websites/staging/slider/trunk/content/developing/releasing.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/releasing.html (original)
+++ websites/staging/slider/trunk/content/developing/releasing.html Wed Jan  6 
15:58:35 2016
@@ -530,9 +530,15 @@ Clone this project and read its instruct
 <span class="n">vote</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">negative</span><span class="p">=</span>0
 <span class="n">vote</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">positive</span><span class="p">=</span>0
 <span class="n">vote</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span class="n">zero</span><span 
class="p">=</span>0
+<span class="n">vote</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">comment</span><span class="p">=(</span><span class="n">any</span> 
<span class="n">other</span> <span class="n">commentary</span><span 
class="p">,</span> <span class="n">half</span> <span 
class="n">votes</span><span class="p">,</span> <span class="n">etc</span><span 
class="p">)</span>
 </pre></div>
 
 
+<p>If there aren't any non-binding votes, you can skip listing the totals; the
+binding values will propagate over. Once non-binding results come in, you
+need to increment both of the fields with every binding vote.</p>
+<p>The <code>vote.result.comment</code> property is for any optional text to be
+included in the results.</p>
 <h3 id="generate-the-result-message">Generate the result message<a 
class="headerlink" href="#generate-the-result-message" title="Permanent 
link">&para;</a></h3>
 <p>Generate the email to send to the developer list</p>
 <div class="codehilite"><pre><span class="n">ant</span> <span 
class="o">-</span><span class="n">f</span> <span class="n">bin</span><span 
class="o">/</span><span class="n">release</span><span class="p">.</span><span 
class="n">xml</span> <span class="n">generate</span><span 
class="o">-</span><span class="n">result</span><span class="o">-</span><span 
class="n">message</span>
@@ -578,10 +584,19 @@ if a binding Incubator PMC (IPMC) member
 <div class="codehilite"><pre><span class="n">vote</span><span 
class="p">.</span><span class="n">incubator</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">positive</span><span class="p">.</span><span 
class="n">binding</span><span class="p">=</span>0
 <span class="n">vote</span><span class="p">.</span><span 
class="n">incubator</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span class="n">zero</span><span 
class="p">.</span><span class="n">binding</span><span class="p">=</span>0
 <span class="n">vote</span><span class="p">.</span><span 
class="n">incubator</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">negative</span><span class="p">.</span><span 
class="n">binding</span><span class="p">=</span>0
+<span class="n">vote</span><span class="p">.</span><span 
class="n">incubator</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">positive</span><span class="p">=</span>0
+<span class="n">vote</span><span class="p">.</span><span 
class="n">incubator</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span class="n">zero</span><span 
class="p">=</span>0
+<span class="n">vote</span><span class="p">.</span><span 
class="n">incubator</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">negative</span><span class="p">=</span>0
+<span class="n">vote</span><span class="p">.</span><span 
class="n">incubator</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">comment</span><span class="p">=(</span><span class="n">any</span> 
<span class="n">other</span> <span class="n">commentary</span><span 
class="p">,</span> <span class="n">half</span> <span 
class="n">votes</span><span class="p">,</span> <span class="n">etc</span><span 
class="p">)</span>
 </pre></div>
 
 
-<p>Then create the release message</p>
+<p>If there aren't any non-binding votes, you can skip listing the totals; the
+binding values will propagate over. Once non-binding results come in, you
+need to increment both of the fields with every binding vote.</p>
+<p>The <code>vote.incubator.result.comment</code> property is for any optional 
text to be
+included in the results.</p>
+<p>Then: create the release message</p>
 <div class="codehilite"><pre><span class="n">ant</span> <span 
class="o">-</span><span class="n">f</span> <span class="n">bin</span><span 
class="o">/</span><span class="n">release</span><span class="p">.</span><span 
class="n">xml</span> <span class="n">generate</span><span 
class="o">-</span><span class="n">incubator</span><span class="o">-</span><span 
class="n">result</span><span class="o">-</span><span class="n">message</span>
 </pre></div>
 
@@ -643,13 +658,22 @@ updated by now to reflect the released v
 <span class="n">release</span><span class="p">.</span><span 
class="n">jira</span><span class="p">.</span><span 
class="n">version</span><span class="p">=</span>12334370
 <span class="n">release</span><span class="p">.</span><span 
class="n">rc</span><span class="p">.</span><span class="n">suffix</span><span 
class="p">=</span><span class="o">-</span><span class="n">RC1</span>
 <span class="n">svn</span><span class="p">.</span><span 
class="n">publish</span><span class="p">.</span><span class="n">dir</span><span 
class="p">=</span><span class="o">/</span><span class="n">Users</span><span 
class="o">/</span><span class="n">stevel</span><span class="o">/</span><span 
class="n">Projects</span><span class="o">/</span><span 
class="n">Apache</span><span class="o">/</span><span 
class="n">slider</span><span class="o">-</span><span class="n">dist</span>
-<span class="n">nexus</span><span class="p">.</span><span 
class="n">staging</span><span class="p">.</span><span 
class="n">repository</span><span class="p">=</span><span 
class="n">orgapacheslider</span><span class="o">-</span>1013
 <span class="n">git</span><span class="p">.</span><span 
class="n">release</span><span class="p">.</span><span 
class="n">branch</span><span class="p">=</span><span 
class="n">branches</span><span class="o">/</span><span 
class="n">branch</span><span class="o">-</span>0<span class="p">.</span>90
+<span class="n">git</span><span class="p">.</span><span 
class="n">version</span><span class="p">=</span>9<span 
class="n">bb379f83c78b61aeb4110b93796bc02c08c4226</span>
+<span class="n">nexus</span><span class="p">.</span><span 
class="n">staging</span><span class="p">.</span><span 
class="n">repository</span><span class="p">=</span><span 
class="n">orgapacheslider</span><span class="o">-</span>1013
+
 <span class="n">vote</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">positive</span><span class="p">.</span><span 
class="n">binding</span><span class="p">=</span>3
 <span class="n">vote</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span class="n">zero</span><span 
class="p">.</span><span class="n">binding</span><span class="p">=</span>0
 <span class="n">vote</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">negative</span><span class="p">.</span><span 
class="n">binding</span><span class="p">=</span>0
+<span class="n">vote</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">comment</span><span class="p">=</span>
+
 <span class="n">mail</span><span class="p">.</span><span 
class="n">vote</span><span class="p">.</span><span class="n">thread</span><span 
class="p">=</span><span class="n">http</span><span class="p">:</span><span 
class="o">//</span><span class="n">mail</span><span class="o">-</span><span 
class="n">archives</span><span class="p">.</span><span 
class="n">apache</span><span class="p">.</span><span class="n">org</span><span 
class="o">/</span><span class="n">mod_mbox</span><span class="o">/</span><span 
class="n">incubator</span><span class="o">-</span><span 
class="n">slider</span><span class="o">-</span><span class="n">dev</span><span 
class="o">/</span>201512<span class="p">.</span><span 
class="n">mbox</span><span class="o">/</span><span 
class="c">%3C7EBD312A-E115-4A99-AAE7-1BF553E3B28D%40hortonworks.com%3E</span>
 <span class="n">mail</span><span class="p">.</span><span 
class="n">vote</span><span class="p">.</span><span class="n">result</span><span 
class="p">.</span><span class="n">thread</span><span class="p">=</span><span 
class="n">http</span><span class="p">:</span><span class="o">//</span><span 
class="n">mail</span><span class="o">-</span><span 
class="n">archives</span><span class="p">.</span><span 
class="n">apache</span><span class="p">.</span><span class="n">org</span><span 
class="o">/</span><span class="n">mod_mbox</span><span class="o">/</span><span 
class="n">incubator</span><span class="o">-</span><span 
class="n">slider</span><span class="o">-</span><span class="n">dev</span><span 
class="o">/</span>201601<span class="p">.</span><span 
class="n">mbox</span><span class="o">/</span><span 
class="c">%3CC28233B7-9016-44F4-9A6B-1EBC8BFCDF08%40hortonworks.com%3E</span>
+
+<span class="n">vote</span><span class="p">.</span><span 
class="n">incubator</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">positive</span><span class="p">.</span><span 
class="n">binding</span><span class="p">=</span>4
+<span class="n">vote</span><span class="p">.</span><span 
class="n">incubator</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span class="n">zero</span><span 
class="p">.</span><span class="n">binding</span><span class="p">=</span>0
+<span class="n">vote</span><span class="p">.</span><span 
class="n">incubator</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">negative</span><span class="p">.</span><span 
class="n">binding</span><span class="p">=</span>0
+<span class="n">vote</span><span class="p">.</span><span 
class="n">incubator</span><span class="p">.</span><span 
class="n">result</span><span class="p">.</span><span 
class="n">comment</span><span class="p">=(</span><span class="n">and</span> 
<span class="n">a</span> <span class="o">+</span>0<span class="p">.</span>5 
<span class="n">vote</span> <span class="n">from</span> <span 
class="n">Daniel</span> <span class="n">Gruno</span><span class="p">)</span>
 </pre></div>
 
 
@@ -676,15 +700,15 @@ updated by now to reflect the released v
 if you re-run them between stages they may produce different artifacts.</p>
 </li>
 <li>
-<p>(you can set the property <code>git.version</code> if you wish to build a 
vote message
+<p>You can set the property <code>git.version</code> if you wish to build a 
vote message
 from a different git version from the current build, but as you must
 be calling for a vote on the version released, only do this if you are 
modifying
-the <code>release.xml</code> release file)`</p>
+the <code>release.xml</code> release file)</p>
 </li>
 <li>
 <p>You can create the <code>release.properties</code> file elsewhere and point 
to it via the
 ant <code>release.properties</code> property option. 
-This would need to be set in <code>build.properties</code> or on the command 
line</p>
+This would need to be set in <code>build.properties</code> or on the command 
line.</p>
 <div class="codehilite"><pre><span class="n">ant</span> <span 
class="o">-</span><span class="n">f</span> <span class="n">bin</span><span 
class="o">/</span><span class="n">release</span><span class="p">.</span><span 
class="n">xml</span> <span class="o">-</span><span 
class="n">Drelease</span><span class="p">.</span><span 
class="k">properties</span><span class="p">=</span><span 
class="o">~/</span><span class="n">release</span><span class="p">.</span><span 
class="k">properties</span>
 </pre></div>
 
@@ -726,8 +750,8 @@ Slider release.</p>
 <li><a href="http://www.apache.org/dev/release.html";>ASF release 
guidelines</a></li>
 <li><a href="http://www.apache.org/dev/release-publishing.html";>Publishing 
Releases</a></li>
 <li><a href="http://www.apache.org/dev/publishing-maven-artifacts.html";>ASF 
guide to publishing maven artifacts</a></li>
-<li><a 
href="https://wiki.apache.org/commons/UsingNexus";>https://wiki.apache.org/commons/UsingNexus</a></li>
-<li><a href="http://danielkummer.github.io/git-flow-cheatsheet/";>git 
flow</a></li>
+<li><a href="https://wiki.apache.org/commons/UsingNexus";>UsingNexus</a></li>
+<li><a href="http://www.apache.org/dev/release-signing.html";>ASF signing 
guidelines</a></li>
 </ul>
   </div>
 

Modified: 
websites/staging/slider/trunk/content/docs/slider_specs/application_pkg_upgrade.html
==============================================================================
--- 
websites/staging/slider/trunk/content/docs/slider_specs/application_pkg_upgrade.html
 (original)
+++ 
websites/staging/slider/trunk/content/docs/slider_specs/application_pkg_upgrade.html
 Wed Jan  6 15:58:35 2016
@@ -213,16 +213,16 @@ still be the older version. Hence <code>
 Automated application package upgrade will be supported soon.</p>
 <h2 id="phases-of-upgradedowngrade">Phases of Upgrade/Downgrade<a 
class="headerlink" href="#phases-of-upgradedowngrade" title="Permanent 
link">&para;</a></h2>
 <h4 id="yarn-core-libraries-and-configurations-upgradedowngrade">YARN core 
(libraries and configurations) upgrade/downgrade<a class="headerlink" 
href="#yarn-core-libraries-and-configurations-upgradedowngrade" 
title="Permanent link">&para;</a></h4>
-<p>&nbsp;&nbsp;&nbsp;&nbsp;Running Slider apps will continue to run, with no 
downtime</p>
+<p>Running Slider apps will continue to run, with no downtime</p>
 <h4 id="slider-client-upgradedowngrade">Slider client upgrade/downgrade<a 
class="headerlink" href="#slider-client-upgradedowngrade" title="Permanent 
link">&para;</a></h4>
-<p>&nbsp;&nbsp;&nbsp;&nbsp;Does not affect running Slider apps at all. New 
version of client can co-exist with older versions of client.</p>
+<p>Does not affect running Slider apps at all. New version of client can 
co-exist with older versions of client.</p>
 <h4 
id="slider-application-master-upgradedowngrade-of-running-applications">Slider 
Application Master upgrade/downgrade of running applications<a 
class="headerlink" 
href="#slider-application-master-upgradedowngrade-of-running-applications" 
title="Permanent link">&para;</a></h4>
-<p>&nbsp;&nbsp;&nbsp;&nbsp;Applications started prior to the start of YARN 
core upgrade/downgrade, will continue to run with the 
+<p>Applications started prior to the start of YARN core upgrade/downgrade, 
will continue to run with the 
 older versions of Slider core and Hadoop libraries. There is no support for 
rolling upgrade of Slider AM.
 To upgrade running Slider AMs, the application needs to be stopped and 
restarted with the new version
 of the client.</p>
 <h4 
id="applications-deployed-by-slider-binaries-and-configurations-upgradedowngrade">Applications
 deployed by Slider (binaries and configurations) upgrade/downgrade<a 
class="headerlink" 
href="#applications-deployed-by-slider-binaries-and-configurations-upgradedowngrade"
 title="Permanent link">&para;</a></h4>
-<p>&nbsp;&nbsp;&nbsp;&nbsp;This is what this document is primarily about.</p>
+<p>This is what this document is primarily about.</p>
 <h2 id="rolling-upgrade-of-applications-deployed-by-slider">Rolling Upgrade of 
Applications Deployed by Slider<a class="headerlink" 
href="#rolling-upgrade-of-applications-deployed-by-slider" title="Permanent 
link">&para;</a></h2>
 <p>A run-book style list of atomic steps exposed by Slider. These steps will 
be automated 
 by Apache Ambari in a future release. It can be easily orchestrated by a shell 
script 
@@ -356,8 +356,11 @@ Master with the old v1.0 config and reso
 
 <h2 id="pre-and-post-upgrade-hooks">Pre and post upgrade hooks<a 
class="headerlink" href="#pre-and-post-upgrade-hooks" title="Permanent 
link">&para;</a></h2>
 <h3 id="pre-upgrade-hook-optional">Pre-upgrade hook (optional)<a 
class="headerlink" href="#pre-upgrade-hook-optional" title="Permanent 
link">&para;</a></h3>
-<p>&nbsp;&nbsp;&nbsp;&nbsp;The pre-upgrade steps, if provided, will allow 
applications to execute simple housekeeping tasks 
-before Slider actually calls stop operation in an upgrade scenario 
(specifically if they need to 
+<div class="codehilite"><pre><span class="n">The</span> <span 
class="n">pre</span><span class="o">-</span><span class="n">upgrade</span> 
<span class="n">steps</span><span class="p">,</span> <span class="k">if</span> 
<span class="n">provided</span><span class="p">,</span> <span 
class="n">will</span> <span class="n">allow</span> <span 
class="n">applications</span> <span class="n">to</span> <span 
class="n">execute</span> <span class="n">simple</span> <span 
class="n">housekeeping</span> <span class="n">tasks</span>
+</pre></div>
+
+
+<p>before Slider actually calls stop operation in an upgrade scenario 
(specifically if they need to 
 be performed in every single container and 1000s of them are running). An 
example could be to 
 send a message to a queue that the current instance of memcached is going down 
so that the load 
 balancer rules can be dynamically updated. Performing long-running tasks or 
tasks that needs to 
@@ -366,13 +369,19 @@ performed manually before starting the u
 pre-upgrade hook is not a good candidate for such operations. Additional 
parameters might have 
 to be exposed, like timeout, which can be used to wait at most n seconds (say) 
after which Slider 
 will call the application stop hook even if the pre-upgrade operation is not 
completed.</p>
-<p>&nbsp;&nbsp;&nbsp;&nbsp;Use 
<code>app-packages/hbase/package/scripts/hbase_master.py</code> as a sample for 
defining the 
-pre-upgrade hook. Note, the pre-upgrade hook will be triggered only if the 
currently running
+<div class="codehilite"><pre><span class="n">Use</span> `<span 
class="n">app</span><span class="o">-</span><span 
class="n">packages</span><span class="o">/</span><span 
class="n">hbase</span><span class="o">/</span><span 
class="n">package</span><span class="o">/</span><span 
class="n">scripts</span><span class="o">/</span><span 
class="n">hbase_master</span><span class="p">.</span><span class="n">py</span>` 
<span class="n">as</span> <span class="n">a</span> <span 
class="n">sample</span> <span class="k">for</span> <span 
class="n">defining</span> <span class="n">the</span>
+</pre></div>
+
+
+<p>pre-upgrade hook. Note, the pre-upgrade hook will be triggered only if the 
currently running
 application has been created using Slider verion 
<code>0.80.0-incubating</code> or later and the scripts
 in the package has the pre-upgrade hook defined.</p>
 <h3 id="post-upgrade-hook-optional-not-yet-supported">Post-upgrade hook 
(optional) - <code>not yet supported</code><a class="headerlink" 
href="#post-upgrade-hook-optional-not-yet-supported" title="Permanent 
link">&para;</a></h3>
-<p>&nbsp;&nbsp;&nbsp;&nbsp;This allows applications to perform simple 
housekeeping tasks prior to calling start on the new 
-version of the application component. This is helpful only if such tasks are 
required to be 
+<div class="codehilite"><pre><span class="n">This</span> <span 
class="n">allows</span> <span class="n">applications</span> <span 
class="n">to</span> <span class="n">perform</span> <span 
class="n">simple</span> <span class="n">housekeeping</span> <span 
class="n">tasks</span> <span class="n">prior</span> <span class="n">to</span> 
<span class="n">calling</span> <span class="n">start</span> <span 
class="n">on</span> <span class="n">the</span> <span class="n">new</span>
+</pre></div>
+
+
+<p>version of the application component. This is helpful only if such tasks 
are required to be 
 performed in every single container and 1000s of them are running. This hook 
will be triggered only in the 
 upgrade scenario. It will not be called on new containers created using flex 
up, in non-upgrade 
 scenarios. This makes triggering of post-upgrade hook a little tricky and 
hence is not supported


Reply via email to