You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@slider.apache.org by bu...@apache.org on 2015/11/02 18:24:48 UTC
svn commit: r971096 [3/8] - in /websites/staging/slider/trunk/content: ./
design/ design/registry/ design/specification/ developing/ docs/ docs/api/
docs/configuration/ docs/configuration/revision-1/ docs/slider_specs/
downloads/ release_notes/
Modified: websites/staging/slider/trunk/content/design/ssl_implementation.html
==============================================================================
--- websites/staging/slider/trunk/content/design/ssl_implementation.html (original)
+++ websites/staging/slider/trunk/content/design/ssl_implementation.html Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block" href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
@@ -182,30 +193,30 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License. See accompanying LICENSE file.
-->
-<h1 id="agent-to-application-master-ssl-communication">Agent to Application Master SSL Communication</h1>
+<h1 id="agent-to-application-master-ssl-communication">Agent to Application Master SSL Communication<a class="headerlink" href="#agent-to-application-master-ssl-communication" title="Permanent link">¶</a></h1>
<p>Slider agents are configured to communicate with the Slider Application Master using SSL. By default, one-way SSL authentication is enabled (i.e., the agent verifies the identity of the application master). However, two-way SSL authentication can be enabled to further secure the communication channel.</p>
-<h2 id="application-master-ssl-support">Application Master SSL Support</h2>
+<h2 id="application-master-ssl-support">Application Master SSL Support<a class="headerlink" href="#application-master-ssl-support" title="Permanent link">¶</a></h2>
<p>There are two primary components enabling server-side SSL support:</p>
<ul>
<li>The server's certificate mananger</li>
<li>The agent-facing HTTPS Server</li>
</ul>
-<h3 id="server-certificate-manager">Server Certificate Manager</h3>
+<h3 id="server-certificate-manager">Server Certificate Manager<a class="headerlink" href="#server-certificate-manager" title="Permanent link">¶</a></h3>
<p>As the Slider application master starts up it leverages the certificate manager to ensure that the resources required to support SSL transport - the server certificate, the key store, and the truststore - are available. The certificate manager will create these artifacts if necessary (see figure 1).</p>
<p><img alt="Server Certificate Generation" src="../images/server_cert_gen.png" /></p>
<p>Figure 1 - Server Certificate and Keystore/Trustore Generation</p>
<p>In addition, if two-way SSL is enabled (more on that later), the Slider application master will leverage the certificate manager to create client certificates for every container launched as part of the application. These certificates, along with the AM's certificate, will subsequently be seeded to the given container's host machine via Yarn's resource localization facilities.</p>
-<h3 id="agent-facing-https-server">Agent-facing HTTPS Server</h3>
+<h3 id="agent-facing-https-server">Agent-facing HTTPS Server<a class="headerlink" href="#agent-facing-https-server" title="Permanent link">¶</a></h3>
<p>Once the artifacts necessary for supporting SSL transport are available, the agent-facing HTTP server instance is created and started. This instance creates two SSL connectors. The first connector is always configured for one-way SSL and supports server liveness checks from the agents. The second connector provides the port over which agent registration and heart beats are transmitted. It is configured for one-way SSL by default but can be explicitly configured for two-way SSL (hence the need for a certificate seeding mechanism as detailed above). Figure 2 illustrates this startup sequence.</p>
<p><img alt="Agent HTTPS server" src="../images/server_ssl_startup.png" /></p>
<p>Figure 2 - Server Agent-facing HTTP Server Initialization</p>
-<h2 id="agent-communication-modes">Agent Communication Modes</h2>
+<h2 id="agent-communication-modes">Agent Communication Modes<a class="headerlink" href="#agent-communication-modes" title="Permanent link">¶</a></h2>
<p>The agent and application master communicate over HTTPS in one of two modes:</p>
<ol>
<li>One-way SSL</li>
<li>Two-way SSL</li>
</ol>
-<h3 id="one-way-ssl">One-way SSL</h3>
+<h3 id="one-way-ssl">One-way SSL<a class="headerlink" href="#one-way-ssl" title="Permanent link">¶</a></h3>
<p>This is the default communication mode between the agent and application master. One-way SSL authentication requires the client to verify the identity of the server, but the server does not verify the identify of the client (in this case, the agent). </p>
<p>The sequence of events for the setup of agent to AM one-way SSL communication is:</p>
<ol>
@@ -216,7 +227,7 @@ Latest release: <strong>0.80.0-incubatin
<p>See Figure 3 for an illustration of this sequence.</p>
<p><img alt="One-way SSL" src="../images/agent_am_one_way_ssl.png" /></p>
<p>Figure 3 - Agent to AM One-way SSL Communication</p>
-<h3 id="two-way-ssl">Two-way SSL</h3>
+<h3 id="two-way-ssl">Two-way SSL<a class="headerlink" href="#two-way-ssl" title="Permanent link">¶</a></h3>
<p>The setup for two-way SSL is more involved since both parties must have each other's certificates available to establish the trust required for this authentication mechanism. Therefore, the Application Master seeds both the AM's certificate (trust store) and the client's certificate (key store) to the host machine as the container is being instantiated. Therefore, the two parties are configured for communication over the configured two-way SSL port. See Figure 4 for an illustration of this setup.</p>
<p><img alt="Two-way SSL" src="../images/agent_am_two_way_ssl.png" /></p>
<p>Figure 3 - Agent to AM Two-way SSL Communication</p>
Modified: websites/staging/slider/trunk/content/developing/building.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/building.html (original)
+++ websites/staging/slider/trunk/content/developing/building.html Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block" href="/downloads/" role="button">Download</a>
</div>
Modified: websites/staging/slider/trunk/content/developing/chaosmonkey.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/chaosmonkey.html (original)
+++ websites/staging/slider/trunk/content/developing/chaosmonkey.html Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block" href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
@@ -182,7 +193,7 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License. See accompanying LICENSE file.
-->
-<h1 id="slider-chaos-monkey">Slider Chaos Monkey</h1>
+<h1 id="slider-chaos-monkey">Slider Chaos Monkey<a class="headerlink" href="#slider-chaos-monkey" title="Permanent link">¶</a></h1>
<p>Slider includes a built in <a href="http://techblog.netflix.com/2012/07/chaos-monkey-released-into-wild.html">Chaos Monkey</a>.
This is a service which runs inside the Slider Application Master, and randomly
kills containers without any warning, or even the application master itself.</p>
@@ -208,7 +219,7 @@ to be exactly this value, nor will the i
<p>A monkey interval of 30 minutes and an AM kill probability of 25% would result
in the aggregate failure rate being approximately the same, but the interval between failures
would be different.</p>
-<h2 id="configuring-the-chaos-monkey">Configuring the Chaos Monkey</h2>
+<h2 id="configuring-the-chaos-monkey">Configuring the Chaos Monkey<a class="headerlink" href="#configuring-the-chaos-monkey" title="Permanent link">¶</a></h2>
<p>The Chaos Monkey is configured on a per-application basis, by setting options
in the <code>global</code> section of the internal resources file, <code>internal.json</code></p>
<p>Any option which takes a probability uses unit of hundreths of a percentage,
@@ -218,10 +229,10 @@ take place. A value of <code>100</code>
to floating point numbers.</p>
<p>the monkey can be enabled, after which the interval between checks must be set.
Available actions can then have their individidual probability set.</p>
-<h3 id="enabling-the-monkey">Enabling the Monkey</h3>
+<h3 id="enabling-the-monkey">Enabling the Monkey<a class="headerlink" href="#enabling-the-monkey" title="Permanent link">¶</a></h3>
<p>The option <code>internal.chaos.monkey.enabled</code> enables or disables the monkey; it
must equal <code>"true"</code> for the monkey to be enabled and other options read.</p>
-<h3 id="interval">Interval</h3>
+<h3 id="interval">Interval<a class="headerlink" href="#interval" title="Permanent link">¶</a></h3>
<p>The interval (aggregated to produce a total interval) between checks to see if
<em>any</em> chaos action is to be triggered.</p>
<ul>
@@ -231,7 +242,7 @@ must equal <code>"true"</code> for the m
<li><code>internal.chaos.monkey.interval.seconds</code></li>
</ul>
<p>If not interval is set the chaos monkey does not start</p>
-<h3 id="startup-delay">Startup delay</h3>
+<h3 id="startup-delay">Startup delay<a class="headerlink" href="#startup-delay" title="Permanent link">¶</a></h3>
<p>The chaos monkey can be given a startup delay before it begins
actions. The value defaults to the interval value (see above).</p>
<ul>
@@ -240,7 +251,7 @@ actions. The value defaults to the inter
<li><code>internal.chaos.monkey.delay.minutes</code></li>
<li><code>internal.chaos.monkey.delay.seconds</code></li>
</ul>
-<h2 id="application-master-kill">Application Master Kill</h2>
+<h2 id="application-master-kill">Application Master Kill<a class="headerlink" href="#application-master-kill" title="Permanent link">¶</a></h2>
<p>The probability of the AM being killed on a monkey check is:</p>
<div class="codehilite"><pre><span class="n">internal</span><span class="p">.</span><span class="n">chaos</span><span class="p">.</span><span class="n">monkey</span><span class="p">.</span><span class="n">probability</span><span class="p">.</span><span class="n">amfailure</span>
</pre></div>
@@ -253,7 +264,7 @@ running application itself to continue u
retries.</p>
<p>As a restarted AM resets all its internal state, the Chaos Monkey itself will be
restarted with a new interval <em>which begins from the moment the AM is restarted</em>.</p>
-<h2 id="container-kill">Container Kill</h2>
+<h2 id="container-kill">Container Kill<a class="headerlink" href="#container-kill" title="Permanent link">¶</a></h2>
<p>The probability of a container being killed in a single monkey "play" is:</p>
<div class="codehilite"><pre><span class="n">internal</span><span class="p">.</span><span class="n">chaos</span><span class="p">.</span><span class="n">monkey</span><span class="p">.</span><span class="n">probability</span><span class="p">.</span><span class="n">containerfailure</span>
</pre></div>
@@ -268,7 +279,7 @@ requesting and re-instantiating a replac
tolerate a failure rate.</p>
<p>If there are no containers hosting application components at the time
the chaos monkey performs its actions, then no container will be killed.</p>
-<h2 id="am-launch-failure">AM Launch Failure</h2>
+<h2 id="am-launch-failure">AM Launch Failure<a class="headerlink" href="#am-launch-failure" title="Permanent link">¶</a></h2>
<p>The launch failure is a special check at startup, if the monkey is enabled:
it defines the probability that the launch itself will fail.</p>
<p>It is tested precisely once per application attempt, at launch startup</p>
@@ -280,7 +291,7 @@ it defines the probability that the laun
1. the monkey must be enabled with <code>internal.chaos.monkey.enabled=true</code>
1. A non-zero monkey interval must be set via the <code>internal.chaos.monkey.interval</code>
properties</p>
-<h1 id="example">Example</h1>
+<h1 id="example">Example<a class="headerlink" href="#example" title="Permanent link">¶</a></h1>
<p>A disabled Chaos Monkey</p>
<div class="codehilite"><pre><span class="p">{</span>
"<span class="n">internal</span><span class="p">.</span><span class="n">chaos</span><span class="p">.</span><span class="n">monkey</span><span class="p">.</span><span class="n">enabled</span>"<span class="p">:</span>" <span class="n">false</span>"
Modified: websites/staging/slider/trunk/content/developing/debugging.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/debugging.html (original)
+++ websites/staging/slider/trunk/content/developing/debugging.html Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block" href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,19 +196,19 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="debugging-apache-slider">Debugging Apache Slider</h1>
+<h1 id="debugging-apache-slider">Debugging Apache Slider<a class="headerlink" href="#debugging-apache-slider" title="Permanent link">¶</a></h1>
<p>There are a number of options available to you for debugging Slider applications. They include:</p>
<ul>
<li>Using Slider logging</li>
<li>IDE-based remote debugging of the Application Master</li>
</ul>
-<h2 id="using-slider-logging">Using Slider logging</h2>
+<h2 id="using-slider-logging">Using Slider logging<a class="headerlink" href="#using-slider-logging" title="Permanent link">¶</a></h2>
<p>There are a number of options for viewing the generated log files:</p>
<ol>
<li>Using a web browser</li>
<li>Accessing the host machine</li>
</ol>
-<h3 id="using-a-web-browser">Using a web browser</h3>
+<h3 id="using-a-web-browser">Using a web browser<a class="headerlink" href="#using-a-web-browser" title="Permanent link">¶</a></h3>
<p>The log files are accessible via the Yarn Resource Manager UI. From the main page (e.g. <code>http://${YARN_RESOURCE_MGR_HOST}:8088</code>),
click on the link for the application instance of interest, and then click on the <code>logs</code> link.
This will present you with a page with links to the <code>slider-err.txt</code> file and the <code>slider-out.txt</code> file.
@@ -206,7 +217,7 @@ Once the log page is presented, click on
<p>If the file <code>slider-out.txt</code> is empty, then examine <code>slider-err.txt</code> -an empty
output log usually means that the java process failed to start -this should be
logged in the error file.</p>
-<h3 id="accessing-the-host-machine">Accessing the host machine</h3>
+<h3 id="accessing-the-host-machine">Accessing the host machine<a class="headerlink" href="#accessing-the-host-machine" title="Permanent link">¶</a></h3>
<p>If access to other log files is required, there is the option of logging in
to the host machine on which the application component is running
-provided you have the correct permissions.</p>
@@ -225,7 +236,7 @@ This file contains the logs from the Sli
<p>The command logs produced by the slider-agent are available in the <code>command-log</code> folder relative to <code>${AGENT_LOG_ROOT}/app</code></p>
<p>Note that the <em>fish</em> shell is convenient for debugging, as <code>cat log/**/slider-out.txt</code> will find the relevant output file
irrespective of what the path leading to it is.</p>
-<h2 id="ide-based-remote-debugging-of-the-application-master">IDE-based remote debugging of the Application Master</h2>
+<h2 id="ide-based-remote-debugging-of-the-application-master">IDE-based remote debugging of the Application Master<a class="headerlink" href="#ide-based-remote-debugging-of-the-application-master" title="Permanent link">¶</a></h2>
<p>For situations in which the logging does not yield enough information to debug an issue,
the user has the option of specifying JVM command line options for the
Application Master that enable attaching to the running process with a debugger
Modified: websites/staging/slider/trunk/content/developing/demo.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/demo.html (original)
+++ websites/staging/slider/trunk/content/developing/demo.html Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block" href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
@@ -182,7 +193,7 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License. See accompanying LICENSE file.
-->
-<h1 id="simple-slider-demo">Simple Slider Demo</h1>
+<h1 id="simple-slider-demo">Simple Slider Demo<a class="headerlink" href="#simple-slider-demo" title="Permanent link">¶</a></h1>
<p>These instructions cover how to give a simple demo of slider, showing
<em> creating an application instance
</em> starting and stopping an instance
@@ -194,14 +205,14 @@ Latest release: <strong>0.80.0-incubatin
<em> Configuring the application instance via <code>app_conf.json</code>
</em> Functional use of the deployed application other than viewing its web pages
* Security</p>
-<h2 id="preparation">Preparation</h2>
+<h2 id="preparation">Preparation<a class="headerlink" href="#preparation" title="Permanent link">¶</a></h2>
<p>Before starting the demo you need</p>
<ol>
<li>A Hadoop 2.6+ cluster, one node or greater</li>
<li>A local installation of the slider client (unzipped into a directory is sufficient)</li>
<li>A <code>slider-client.xml</code> file containing the binding information for the Hadoop cluster</li>
</ol>
-<h3 id="hadoop-cluster-setup">Hadoop cluster setup</h3>
+<h3 id="hadoop-cluster-setup">Hadoop cluster setup<a class="headerlink" href="#hadoop-cluster-setup" title="Permanent link">¶</a></h3>
<p>The cluster must be set up with no checks on memory use, and no minimum size on container allocations. This ensures that all requested VMs will be created, irrespective of how much memory there is available on the VM.</p>
<div class="codehilite"><pre> <span class="nt"><property></span>
<span class="nt"><name></span>yarn.scheduler.minimum-allocation-mb<span class="nt"></name></span>
@@ -225,8 +236,8 @@ Latest release: <strong>0.80.0-incubatin
</pre></div>
-<h3 id="local-environment-and-path-setup">Local environment and path setup</h3>
-<h4 id="bash">Bash</h4>
+<h3 id="local-environment-and-path-setup">Local environment and path setup<a class="headerlink" href="#local-environment-and-path-setup" title="Permanent link">¶</a></h3>
+<h4 id="bash">Bash<a class="headerlink" href="#bash" title="Permanent link">¶</a></h4>
<div class="codehilite"><pre> <span class="n">export</span> <span class="n">HADOOP_CONF_DIR</span><span class="p">=</span><span class="o">~/</span><span class="n">clusters</span><span class="o">/</span><span class="n">demo</span><span class="o">/</span><span class="n">hadoop</span><span class="o">-</span><span class="n">conf</span>
<span class="n">export</span> <span class="n">SLIDER_CONF_DIR</span><span class="p">=</span><span class="o">~/</span><span class="n">clusters</span><span class="o">/</span><span class="n">demo</span><span class="o">/</span><span class="n">slider</span><span class="p">;</span>
@@ -235,7 +246,7 @@ Latest release: <strong>0.80.0-incubatin
</pre></div>
-<h4 id="fish">Fish</h4>
+<h4 id="fish">Fish<a class="headerlink" href="#fish" title="Permanent link">¶</a></h4>
<div class="codehilite"><pre> <span class="n">set</span> <span class="o">-</span><span class="n">gx</span> <span class="n">HADOOP_CONF_DIR</span> <span class="o">~/</span><span class="n">clusters</span><span class="o">/</span><span class="n">demo</span><span class="o">/</span><span class="n">hadoop</span><span class="o">-</span><span class="n">conf</span>
<span class="n">set</span> <span class="o">-</span><span class="n">gx</span> <span class="n">SLIDER_CONF_DIR</span> <span class="o">~/</span><span class="n">clusters</span><span class="o">/</span><span class="n">demo</span><span class="o">/</span><span class="n">slider</span><span class="p">;</span>
@@ -250,13 +261,13 @@ Latest release: <strong>0.80.0-incubatin
</pre></div>
-<h4 id="tests">Tests</h4>
+<h4 id="tests">Tests<a class="headerlink" href="#tests" title="Permanent link">¶</a></h4>
<div class="codehilite"><pre><span class="n">slider</span> <span class="n">version</span>
<span class="n">slider</span> <span class="n">list</span>
</pre></div>
-<h3 id="creating-the-hdfs-paths">Creating the HDFS paths</h3>
+<h3 id="creating-the-hdfs-paths">Creating the HDFS paths<a class="headerlink" href="#creating-the-hdfs-paths" title="Permanent link">¶</a></h3>
<p>HDFS needs to have the user's path created, with the username of the user giving the demo, here <code>demo</code>. This username <em>MUST</em> be that of the local user.</p>
<div class="codehilite"><pre><span class="n">hdfs</span> <span class="n">dfs</span> <span class="o">-</span><span class="n">chmod</span> 777 <span class="o">/</span>
<span class="n">hdfs</span> <span class="n">dfs</span> <span class="o">-</span><span class="n">mkdir</span> <span class="o">-</span><span class="n">p</span> <span class="o">/</span><span class="n">user</span><span class="o">/</span><span class="n">demo</span>
@@ -271,7 +282,7 @@ Latest release: <strong>0.80.0-incubatin
</pre></div>
-<h3 id="building-and-installing-the-application">Building and installing the application</h3>
+<h3 id="building-and-installing-the-application">Building and installing the application<a class="headerlink" href="#building-and-installing-the-application" title="Permanent link">¶</a></h3>
<p>This demo uses HBase, so must have the slider hbase application package installed in the cluster.</p>
<ol>
<li>Download the hbase bin package, such as <code>hbase-0.99.1-bin.tar.gz</code></li>
@@ -294,7 +305,7 @@ Latest release: <strong>0.80.0-incubatin
</li>
</ol>
-<h3 id="preparing-the-resource-definitions">Preparing the resource definitions</h3>
+<h3 id="preparing-the-resource-definitions">Preparing the resource definitions<a class="headerlink" href="#preparing-the-resource-definitions" title="Permanent link">¶</a></h3>
<p>Take the template app's <code>resources-default.json</code> and <code>appConf-default.json</code> <em>FROM the target/ subdirectory</em>. They must be the ones with package versions fully expanded.</p>
<p>In <code>appConfig.json</code></p>
<ol>
Modified: websites/staging/slider/trunk/content/developing/functional_tests.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/functional_tests.html (original)
+++ websites/staging/slider/trunk/content/developing/functional_tests.html Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block" href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,7 +196,7 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="testing-apache-slider">Testing Apache Slider</h1>
+<h1 id="testing-apache-slider">Testing Apache Slider<a class="headerlink" href="#testing-apache-slider" title="Permanent link">¶</a></h1>
<div class="codehilite"><pre> <span class="n">The</span> <span class="n">key</span> <span class="n">words</span> "<span class="n">MUST</span>"<span class="p">,</span> "<span class="n">MUST</span> <span class="n">NOT</span>"<span class="p">,</span> "<span class="n">REQUIRED</span>"<span class="p">,</span> "<span class="n">SHALL</span>"<span class="p">,</span> "<span class="n">SHALL</span>
<span class="n">NOT</span>"<span class="p">,</span> "<span class="n">SHOULD</span>"<span class="p">,</span> "<span class="n">SHOULD</span> <span class="n">NOT</span>"<span class="p">,</span> "<span class="n">RECOMMENDED</span>"<span class="p">,</span> "<span class="n">MAY</span>"<span class="p">,</span> <span class="n">and</span>
"<span class="n">OPTIONAL</span>" <span class="n">in</span> <span class="n">this</span> <span class="n">document</span> <span class="n">are</span> <span class="n">to</span> <span class="n">be</span> <span class="n">interpreted</span> <span class="n">as</span> <span class="n">described</span> <span class="n">in</span>
@@ -193,7 +204,7 @@ Latest release: <strong>0.80.0-incubatin
</pre></div>
-<h1 id="functional-tests">Functional Tests</h1>
+<h1 id="functional-tests">Functional Tests<a class="headerlink" href="#functional-tests" title="Permanent link">¶</a></h1>
<p>The functional test suite is designed to test slider against
a live cluster. </p>
<p>For these to work you MUST have </p>
@@ -206,7 +217,7 @@ directory</li>
<li>(deprecated) Accumulo provider tests: Accumulo <code>.tar.gz</code> uploaded to HDFS, and a local or remote accumulo conf
directory</li>
</ol>
-<h2 id="configuration-of-functional-tests">Configuration of functional tests</h2>
+<h2 id="configuration-of-functional-tests">Configuration of functional tests<a class="headerlink" href="#configuration-of-functional-tests" title="Permanent link">¶</a></h2>
<p>Maven MUST have to be given</p>
<ol>
<li>A path to the expanded test archive</li>
@@ -227,10 +238,10 @@ If it is not present, the tests will fai
<p>This file is loaded whenever a slider build or test run takes place</p>
-<h2 id="configuration-of-slider-clientxml">Configuration of <code>slider-client.xml</code></h2>
+<h2 id="configuration-of-slider-clientxml">Configuration of <code>slider-client.xml</code><a class="headerlink" href="#configuration-of-slider-clientxml" title="Permanent link">¶</a></h2>
<p>The <code>slider-client.xml</code> must have extra configuration options for both the HBase and
Accumulo tests, as well as a common set for actually talking to a YARN cluster.</p>
-<h3 id="how-to-pick-up-core-sitexml-hdfs-sitexml-and-yarn-sitexml-values">How to pick up <code>core-site.xml</code>, <code>hdfs-site.xml</code> and <code>yarn-site.xml</code> values</h3>
+<h3 id="how-to-pick-up-core-sitexml-hdfs-sitexml-and-yarn-sitexml-values">How to pick up <code>core-site.xml</code>, <code>hdfs-site.xml</code> and <code>yarn-site.xml</code> values<a class="headerlink" href="#how-to-pick-up-core-sitexml-hdfs-sitexml-and-yarn-sitexml-values" title="Permanent link">¶</a></h3>
<p>The <code>slider-client.xml</code> file can declare a <code>HADOOP_CONF_DIR</code> value
for use by both the test runner AND the command line <code>bin\slider</code> application
invoked.</p>
@@ -277,7 +288,7 @@ or refer to the environment variable <co
are only performed on the test runs. If the same <code>slider-client.xml</code> value
is used directly from the CLI, the environment variable <code>HADOOP_CONF_DIR</code>
must be set to the absolute path of the hadoop configuration directory.</p>
-<h2 id="how-to-validate-the-configuration">How to validate the configuration</h2>
+<h2 id="how-to-validate-the-configuration">How to validate the configuration<a class="headerlink" href="#how-to-validate-the-configuration" title="Permanent link">¶</a></h2>
<p>A test case executing the <code>slider diagnostics</code> command can be used
to print out the configuration as seen by the <code>bin/slider</code> process</p>
<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">integration</span><span class="o">-</span><span class="n">test</span> <span class="o">\</span>
@@ -286,13 +297,13 @@ to print out the configuration as seen b
</pre></div>
-<h2 id="disabling-the-functional-tests-entirely">Disabling the functional tests entirely</h2>
+<h2 id="disabling-the-functional-tests-entirely">Disabling the functional tests entirely<a class="headerlink" href="#disabling-the-functional-tests-entirely" title="Permanent link">¶</a></h2>
<p>All functional tests which require a live YARN cluster
are run during the integration-test phase. They are executed with the commands
<code>mvn verify</code> or <code>mvn integration-test</code> .</p>
<p>If you do not wish to run the functional tests, simply use the <code>mvn package</code> command
and only those tests which do not require a live YARN cluster will run.</p>
-<h3 id="non-mandatory-options">Non-mandatory options</h3>
+<h3 id="non-mandatory-options">Non-mandatory options<a class="headerlink" href="#non-mandatory-options" title="Permanent link">¶</a></h3>
<p>The following test options may be added to <code>slider-client.xml</code> if the defaults
need to be changed</p>
<div class="codehilite"><pre><span class="nt"><property></span>
@@ -330,7 +341,7 @@ filesystem -here a URI to a path visible
the tests do not copy the .tar/.tar.gz files over. The application configuration
directories may be local or remote -they are copied into the <code>.slider</code> directory
during cluster creation.</p>
-<h2 id="provider-specific-parameters">Provider-specific parameters</h2>
+<h2 id="provider-specific-parameters">Provider-specific parameters<a class="headerlink" href="#provider-specific-parameters" title="Permanent link">¶</a></h2>
<p>An individual provider can pick up settings from their own
<code>src/test/resources/slider-client.xml</code> file, or the one in <code>slider-core</code>.
We strongly advice placing all the values in the <code>slider-core</code> file.</p>
@@ -339,7 +350,7 @@ We strongly advice placing all the value
away</li>
<li>There's one place to keep all the configuration values in sync.</li>
</ol>
-<h3 id="agent-tests">Agent Tests</h3>
+<h3 id="agent-tests">Agent Tests<a class="headerlink" href="#agent-tests" title="Permanent link">¶</a></h3>
<p>Agent tests are executed through the following mvn command executed at slider/slider-funtest:</p>
<div class="codehilite"><pre><span class="n">cd</span> <span class="n">slider</span><span class="o">-</span><span class="n">funtest</span>
<span class="n">mvn</span> <span class="n">verify</span> <span class="o">-</span><span class="n">Dslider</span><span class="p">.</span><span class="n">conf</span><span class="p">.</span><span class="n">dir</span><span class="p">=.</span><span class="o">./</span><span class="n">src</span><span class="o">/</span><span class="n">test</span><span class="o">/</span><span class="n">clusters</span><span class="o">/</span><span class="n">remote</span><span class="o">/</span><span class="n">slider</span> <span class="o">-</span><span class="n">Dit</span><span class="p">.</span><span class="n">test</span><span class="p">=</span><span class="n">AppsThroughAgentIT</span> <span class="o">-</span><span class="n">DfailIfNoTests</span><span class="p">=</span><span class="n">false</span>
@@ -374,7 +385,7 @@ away</li>
</pre></div>
-<h3 id="configuring-the-yarn-cluster-for-tests">Configuring the YARN cluster for tests</h3>
+<h3 id="configuring-the-yarn-cluster-for-tests">Configuring the YARN cluster for tests<a class="headerlink" href="#configuring-the-yarn-cluster-for-tests" title="Permanent link">¶</a></h3>
<p>Here are the configuration options we use in <code>yarn-site.xml</code> for testing:</p>
<p>These tell YARN to ignore memory requirements in allocating VMs, and
to keep the log files around after an application run. </p>
@@ -421,7 +432,7 @@ to keep the log files around after an ap
</pre></div>
-<h2 id="testing-against-a-secure-cluster">Testing against a secure cluster</h2>
+<h2 id="testing-against-a-secure-cluster">Testing against a secure cluster<a class="headerlink" href="#testing-against-a-secure-cluster" title="Permanent link">¶</a></h2>
<p>To test against a secure cluster</p>
<ol>
<li><code>slider-client.xml</code> must be configured as per <a href="/docs/security.html">Security</a>.</li>
@@ -430,12 +441,12 @@ the tests has access to HDFS and YARN.</
</ol>
<p>If there are problems authenticating (including the cluster being offline)
the tests appear to hang</p>
-<h3 id="validating-the-configuration">Validating the configuration</h3>
+<h3 id="validating-the-configuration">Validating the configuration<a class="headerlink" href="#validating-the-configuration" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">clean</span> <span class="n">verify</span> <span class="o">-</span><span class="n">Dit</span><span class="p">.</span><span class="n">test</span><span class="p">=</span><span class="n">BuildSetupIT</span>
</pre></div>
-<h2 id="parallel-execution">Parallel execution</h2>
+<h2 id="parallel-execution">Parallel execution<a class="headerlink" href="#parallel-execution" title="Permanent link">¶</a></h2>
<p>Attempts to run test cases in parallel failed âeven with a configuration
to run methods in a class sequentially, but separate classes independently.</p>
<p>Even after identifying and eliminating some unintended sharing of static
@@ -443,7 +454,7 @@ mutable variables, trying to run test ca
tests and produce timeouts.</p>
<p>For this reason parallel tests have been disabled. To accelerate test runs
through parallelization, run different tests on different hosts instead.</p>
-<h2 id="other-constraints">Other constraints</h2>
+<h2 id="other-constraints">Other constraints<a class="headerlink" href="#other-constraints" title="Permanent link">¶</a></h2>
<ul>
<li>Port assignments SHOULD NOT be fixed, as this will cause clusters to fail if
there are too many instances of a role on a same host, or if other tests are
@@ -454,7 +465,7 @@ and it must be different from all others
over time. Otherwise: use the value of <code>0</code> to allow the OS to assign free ports
on demand.</li>
</ul>
-<h2 id="test-requirements">Test Requirements</h2>
+<h2 id="test-requirements">Test Requirements<a class="headerlink" href="#test-requirements" title="Permanent link">¶</a></h2>
<ol>
<li>Test cases should be written so that each class works with exactly one
Slider-deployed cluster</li>
@@ -467,7 +478,7 @@ specific hbase or accumulo categories- a
<li>Tests within the suite (i.e. class) must be designed to be independent
-to work irrespectively of the ordering of other tests.</li>
</ol>
-<h2 id="running-and-debugging-the-functional-tests">Running and debugging the functional tests.</h2>
+<h2 id="running-and-debugging-the-functional-tests">Running and debugging the functional tests.<a class="headerlink" href="#running-and-debugging-the-functional-tests" title="Permanent link">¶</a></h2>
<p>The functional tests all </p>
<ol>
<li>
@@ -504,12 +515,12 @@ In this situation, the tests are in sync
-including any bug fixes- but the scripts executed by those tests are
of a previous build of <code>slider-core.jar</code>. As a result, the fixes are not picked
up.</p>
-<h2 id="limitations-of-slider-funtest">Limitations of slider-funtest</h2>
+<h2 id="limitations-of-slider-funtest">Limitations of slider-funtest<a class="headerlink" href="#limitations-of-slider-funtest" title="Permanent link">¶</a></h2>
<ol>
<li>All tests run from a single client -workload can't scale</li>
<li>Output from failed AM and containers aren't collected</li>
</ol>
-<h2 id="troubleshooting-the-functional-tests">Troubleshooting the functional tests</h2>
+<h2 id="troubleshooting-the-functional-tests">Troubleshooting the functional tests<a class="headerlink" href="#troubleshooting-the-functional-tests" title="Permanent link">¶</a></h2>
<ol>
<li>
<p>If application instances fail to come up as there are still outstanding
@@ -544,7 +555,7 @@ are any problems. Check also that it has
as the host OS.</p>
</li>
</ol>
-<h2 id="running-a-single-integration-test">running a single integration test</h2>
+<h2 id="running-a-single-integration-test">running a single integration test<a class="headerlink" href="#running-a-single-integration-test" title="Permanent link">¶</a></h2>
<p>You can run a single integration test (or a pattern of tests) by setting the
<code>it.test</code> property</p>
<p>For example, to run all Agent IT tests: </p>
@@ -552,7 +563,7 @@ as the host OS.</p>
</pre></div>
-<h4 id="accumulo-configuration-options">Accumulo configuration options</h4>
+<h4 id="accumulo-configuration-options">Accumulo configuration options<a class="headerlink" href="#accumulo-configuration-options" title="Permanent link">¶</a></h4>
<p>Optional parameters</p>
<div class="codehilite"><pre> <span class="nt"><property></span>
<span class="nt"><name></span>slider.test.accumulo.launch.wait.seconds<span class="nt"></name></span>
Modified: websites/staging/slider/trunk/content/developing/index.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/index.html (original)
+++ websites/staging/slider/trunk/content/developing/index.html Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block" href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,7 +196,7 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="developing-apache-slider">Developing Apache Slider</h1>
+<h1 id="developing-apache-slider">Developing Apache Slider<a class="headerlink" href="#developing-apache-slider" title="Permanent link">¶</a></h1>
<p>Slider is an open source project -anyone is free to contributed, and we
strongly encourage people to do so. </p>
<p>Here are documents covering how to go about building, testing and releasing
@@ -203,7 +214,7 @@ Slider</p>
<li><a href="demo.html">Demo Script</a></li>
<li><a href="chaosmonkey.html">Configuring the Slider Chaos Monkey</a></li>
</ul>
-<h2 id="historical-documents">Historical Documents</h2>
+<h2 id="historical-documents">Historical Documents<a class="headerlink" href="#historical-documents" title="Permanent link">¶</a></h2>
<p>These documents are obsolete; they are retained for reference.</p>
<ul>
<li><a href="releasing_process_v1.html">Releasing Process v1</a></li>
Modified: websites/staging/slider/trunk/content/developing/manual_testing.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/manual_testing.html (original)
+++ websites/staging/slider/trunk/content/developing/manual_testing.html Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block" href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,24 +196,24 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="manually-testing-apache-slider">Manually Testing Apache Slider</h1>
+<h1 id="manually-testing-apache-slider">Manually Testing Apache Slider<a class="headerlink" href="#manually-testing-apache-slider" title="Permanent link">¶</a></h1>
<p>Manual testing invloves using Slider package and an AppPackage to perform basic
cluster functionalities such as create/destroy, flex up/down, and start/stop.
A python helper script is provided that can be used to automatically test and app package.</p>
-<h2 id="slidertesterpy"><code>SliderTester.py</code></h2>
+<h2 id="slidertesterpy"><code>SliderTester.py</code><a class="headerlink" href="#slidertesterpy" title="Permanent link">¶</a></h2>
<p>Details to be added.</p>
-<h2 id="slidertesterini"><code>SliderTester.ini</code></h2>
+<h2 id="slidertesterini"><code>SliderTester.ini</code><a class="headerlink" href="#slidertesterini" title="Permanent link">¶</a></h2>
<p>The various config parameters are:</p>
-<h3 id="slider">slider</h3>
+<h3 id="slider">slider<a class="headerlink" href="#slider" title="Permanent link">¶</a></h3>
<ul>
<li><code>package</code>: location of the slider package</li>
<li><code>jdk.path</code>: jdk path on the test hosts</li>
</ul>
-<h3 id="app">app</h3>
+<h3 id="app">app<a class="headerlink" href="#app" title="Permanent link">¶</a></h3>
<ul>
<li><code>package</code>: location of the app package</li>
</ul>
-<h3 id="cluster">cluster</h3>
+<h3 id="cluster">cluster<a class="headerlink" href="#cluster" title="Permanent link">¶</a></h3>
<ul>
<li><code>yarn.application.classpath</code>: yarn application classpaths</li>
<li><code>slider.zookeeper.quorum</code>: the ZK quorum hosts</li>
@@ -210,7 +221,7 @@ Latest release: <strong>0.80.0-incubatin
<li><code>yarn.resourcemanager.scheduler.address</code>:</li>
<li><code>fs.defaultFS</code>: e.g. <code>hdfs://NN_HOST:8020</code></li>
</ul>
-<h3 id="test">test</h3>
+<h3 id="test">test<a class="headerlink" href="#test" title="Permanent link">¶</a></h3>
<ul>
<li><code>app.user</code>: user to use for app creation</li>
<li><code>hdfs.root.user</code>: hdfs root user</li>
@@ -220,7 +231,7 @@ Latest release: <strong>0.80.0-incubatin
<li><code>cluster.name</code>: name of the test cluster, default tst1</li>
<li><code>cluster.type</code>: cluster type to build and test, e.g. hbase,storm,accumulo</li>
</ul>
-<h3 id="agent">agent</h3>
+<h3 id="agent">agent<a class="headerlink" href="#agent" title="Permanent link">¶</a></h3>
</div>
<div id="footer">
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 Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block" href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,9 +196,9 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-release-process">Apache Slider Release Process</h1>
+<h1 id="apache-slider-release-process">Apache Slider Release Process<a class="headerlink" href="#apache-slider-release-process" title="Permanent link">¶</a></h1>
<p>Here is our release process from Slider 0.61-incubating onwards (January 2015)</p>
-<h3 id="tooling">Tooling</h3>
+<h3 id="tooling">Tooling<a class="headerlink" href="#tooling" title="Permanent link">¶</a></h3>
<p>As well as everything needed to build slider, there are some extra requirements
for releasing:</p>
<ol>
@@ -197,7 +208,7 @@ for releasing:</p>
This can perform the git flow operations, as well as show the state of your
git graph.</li>
</ol>
-<h3 id="before-you-begin">Before you begin</h3>
+<h3 id="before-you-begin">Before you begin<a class="headerlink" href="#before-you-begin" title="Permanent link">¶</a></h3>
<p>Check out the latest version of the branch to be released,
run the tests. This should be done on a checked out
version of the code that is not the one you are developing on
@@ -229,7 +240,7 @@ Slider release.</p>
</pre></div>
-<h3 id="checking-licenses">Checking licenses</h3>
+<h3 id="checking-licenses">Checking licenses<a class="headerlink" href="#checking-licenses" title="Permanent link">¶</a></h3>
<p>Maven can check that all dependent artifacts have valid licenses</p>
<p>For modules which publish JARs (<code>slider-core</code> and <code>slider-funtest</code>),
run the third party check for JARs. If you run this at the top level project
@@ -248,7 +259,7 @@ it will do it for the relevant sub proje
<p>This generates the metadata for licenses. Dependencies without a license are warned about.
To fix this, make sure that the (generated or updated) file <code>src/license/THIRD-PARTY.properties</code>
has an entry for every dependency without a license, declaring what their license is.</p>
-<h3 id="signing-keys">Signing keys</h3>
+<h3 id="signing-keys">Signing keys<a class="headerlink" href="#signing-keys" title="Permanent link">¶</a></h3>
<p>Verify your GPG key is provided to Apache. </p>
<p>Apache verifies that distributions are correctly signed.
Login to <a href="https://id.apache.org">https://id.apache.org</a> and verify the
@@ -261,12 +272,12 @@ Upload your GPG public key only to <code
<p><em>Tip</em>: if you are creating a new key, remember what password/passphrase you have
given it. Then generate a revocation certificate and store it somewhere, so
that you can revoke the published key.</p>
-<h5 id="note-profiles">Note: Profiles</h5>
+<h5 id="note-profiles">Note: Profiles<a class="headerlink" href="#note-profiles" title="Permanent link">¶</a></h5>
<p>The slider POMs offer different profiles of Hadoop versions to build against. The instructions
below do not choose one. If a profile is needed, append it to all the maven commands.</p>
<p>e.g. <code>mvn clean install -Prelease-2.6</code></p>
-<h2 id="prepare">Prepare</h2>
-<h3 id="check-everything-in">Check everything in</h3>
+<h2 id="prepare">Prepare<a class="headerlink" href="#prepare" title="Permanent link">¶</a></h2>
+<h3 id="check-everything-in">Check everything in<a class="headerlink" href="#check-everything-in" title="Permanent link">¶</a></h3>
<p>This and other other commands assume that <code>origin</code> maps
to <code>https://git-wip-us.apache.org/repos/asf/incubator-slider.git</code>;
you can check this with <code>git remote -v</code></p>
@@ -287,14 +298,14 @@ you can check this with <code>git remote
</li>
</ul>
-<h3 id="start-the-jira">Start the JIRA</h3>
+<h3 id="start-the-jira">Start the JIRA<a class="headerlink" href="#start-the-jira" title="Permanent link">¶</a></h3>
<p>Create a JIRA for the release, estimate 12h</p>
<div class="codehilite"><pre><span class="n">export</span> <span class="n">SLIDER_RELEASE_JIRA</span><span class="p">=</span><span class="n">SLIDER</span><span class="o">-</span>544
</pre></div>
<p>This seems pessimistic, but there may be surprises.</p>
-<h3 id="choose-your-versions">Choose your versions</h3>
+<h3 id="choose-your-versions">Choose your versions<a class="headerlink" href="#choose-your-versions" title="Permanent link">¶</a></h3>
<p>Choose the version number for the release</p>
<p>Example:</p>
<div class="codehilite"><pre>0<span class="p">.</span>61<span class="p">.</span>0<span class="o">-</span><span class="n">incubating</span>
@@ -306,7 +317,7 @@ you can check this with <code>git remote
</pre></div>
-<h3 id="test-that-everything-works">Test that everything works</h3>
+<h3 id="test-that-everything-works">Test that everything works<a class="headerlink" href="#test-that-everything-works" title="Permanent link">¶</a></h3>
<p>Do a final test run to make sure nothing is broken</p>
<p>In the <code>slider</code> directory, run:</p>
<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span> <span class="o">-</span><span class="n">DskipTests</span>
@@ -331,7 +342,7 @@ This stops functional tests failing beca
the tests time out.</p>
<p>As the test run takes 60+ minutes, now is a good time to consider
finalizing the release notes.</p>
-<h3 id="create-a-release-branch">Create a release branch</h3>
+<h3 id="create-a-release-branch">Create a release branch<a class="headerlink" href="#create-a-release-branch" title="Permanent link">¶</a></h3>
<p>Create or check out a release branch,</p>
<p>Example of creation then push to the origin</p>
<div class="codehilite"><pre><span class="n">git</span> <span class="n">checkout</span> <span class="o">-</span><span class="n">b</span> <span class="n">branches</span><span class="o">/</span><span class="n">branch</span><span class="o">-</span>0<span class="p">.</span>6
@@ -340,7 +351,7 @@ finalizing the release notes.</p>
<p>This branch is where all the release work will take place. That can include patching and cherry picking from the development branch.</p>
-<h3 id="update-the-version-numbers-on-the-main-branch">Update the version numbers on the main branch</h3>
+<h3 id="update-the-version-numbers-on-the-main-branch">Update the version numbers on the main branch<a class="headerlink" href="#update-the-version-numbers-on-the-main-branch" title="Permanent link">¶</a></h3>
<p>Get back to the develop branch and patch its versions</p>
<div class="codehilite"><pre><span class="n">git</span> <span class="n">checkout</span> <span class="n">develop</span>
<span class="n">mvn</span> <span class="n">versions</span><span class="p">:</span><span class="n">set</span> <span class="o">-</span><span class="n">DnewVersion</span><span class="p">=</span>$<span class="n">SLIDER_DEV</span>
@@ -349,7 +360,7 @@ finalizing the release notes.</p>
</pre></div>
-<h1 id="automated-releases-via-maven">Automated releases via maven</h1>
+<h1 id="automated-releases-via-maven">Automated releases via maven<a class="headerlink" href="#automated-releases-via-maven" title="Permanent link">¶</a></h1>
<p>The Slider project uses Maven to automatically publish all the slider artifacts âsource and binaryâ to the ASF repositories</p>
<p>Core sequence</p>
<ol>
@@ -368,8 +379,8 @@ finalizing the release notes.</p>
<li><a href="https://wiki.apache.org/commons/UsingNexus">https://wiki.apache.org/commons/UsingNexus</a></li>
<li><a href="http://repo.maven.apache.org/maven2/org/apache/apache/10/apache-10.pom">Apache Parent Pom</a> for a template POM containing the release plugins. This is not used in the slider release âit was used as a source of some of the actions; the remainder being from the hadoop project.</li>
</ul>
-<h2 id="preparation">Preparation</h2>
-<h3 id="maven-publishing-settings">Maven Publishing settings</h3>
+<h2 id="preparation">Preparation<a class="headerlink" href="#preparation" title="Permanent link">¶</a></h2>
+<h3 id="maven-publishing-settings">Maven Publishing settings<a class="headerlink" href="#maven-publishing-settings" title="Permanent link">¶</a></h3>
<p>You need to provide credentials to the ASF maven repos for publishing/releasing
artifacts, using your ASF username and password.</p>
<p>The ASF docs say use the maven encryption feature.
@@ -403,7 +414,7 @@ anyway.</p>
</pre></div>
-<h3 id="environment-variable-setup">Environment variable setup</h3>
+<h3 id="environment-variable-setup">Environment variable setup<a class="headerlink" href="#environment-variable-setup" title="Permanent link">¶</a></h3>
<p>It's handy to set up an environment with the arguments needed for releases.</p>
<div class="codehilite"><pre><span class="n">export</span> <span class="n">RELARGS</span><span class="p">=</span>"<span class="o">-</span><span class="n">DskipTests</span> <span class="o">-</span><span class="n">DskipITs</span> <span class="o">-</span><span class="n">Papache</span><span class="o">-</span><span class="n">release</span>"
<span class="n">echo</span> $<span class="n">RELARGS</span>
@@ -413,13 +424,13 @@ anyway.</p>
<p>The profile <code>apache-release</code> is used to select a subset of the app packages,
because the default builds of these weren't usable and had odd version numbers
too.</p>
-<h2 id="git-preparation">Git preparation</h2>
+<h2 id="git-preparation">Git preparation<a class="headerlink" href="#git-preparation" title="Permanent link">¶</a></h2>
<p>The maven automated release adds its own git tags and pushes things up to a branch.
All work must be done on a branch created for the release process, so as to
not interfere with the rest of the development.
You are likely to end up rolling back the branch, force-pushing changes etc.,
so cannot actively share the branch with anyone.</p>
-<h3 id="clone-the-repo">Clone the repo.</h3>
+<h3 id="clone-the-repo">Clone the repo.<a class="headerlink" href="#clone-the-repo" title="Permanent link">¶</a></h3>
<p>Don't release from your development dir; do it somewhere clean. Why so? Easier to clean up and guaranteed isolation.</p>
<p>In a directory of your choice</p>
<div class="codehilite"><pre><span class="n">git</span> <span class="n">clone</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">git</span><span class="o">-</span><span class="n">wip</span><span class="o">-</span><span class="n">us</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">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">incubator</span><span class="o">-</span><span class="n">slider</span><span class="p">.</span><span class="n">git</span> <span class="n">slider</span><span class="o">-</span>$<span class="n">SLIDER_RELEASE</span>
@@ -427,7 +438,7 @@ so cannot actively share the branch with
</pre></div>
-<h3 id="check-out-the-branch-you-plan-to-release-on-tag-it">Check out the branch you plan to release on; tag it</h3>
+<h3 id="check-out-the-branch-you-plan-to-release-on-tag-it">Check out the branch you plan to release on; tag it<a class="headerlink" href="#check-out-the-branch-you-plan-to-release-on-tag-it" title="Permanent link">¶</a></h3>
<p>The tag is so that if things go wrong you know what you have to roll back to.</p>
<div class="codehilite"><pre><span class="n">cd</span> <span class="n">incubator</span><span class="o">-</span><span class="n">slider</span>
<span class="n">git</span> <span class="n">checkout</span> <span class="o">-</span><span class="n">t</span> <span class="n">origin</span><span class="o">/</span><span class="n">branches</span><span class="o">/</span><span class="n">branch</span><span class="o">-</span>0<span class="p">.</span>6
@@ -439,7 +450,7 @@ so cannot actively share the branch with
</pre></div>
-<h2 id="test-deploy-a-snapshot">Test Deploy a snapshot</h2>
+<h2 id="test-deploy-a-snapshot">Test Deploy a snapshot<a class="headerlink" href="#test-deploy-a-snapshot" title="Permanent link">¶</a></h2>
<p>This pushes up a <code>-SNAPSHOT</code> version to the ASF snapshot repo.
It doesn't change the POMs; it does verify that you have the basic upload settings, signing keys etc.</p>
<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">clean</span> <span class="n">deploy</span> $<span class="n">RELARGS</span> <span class="o">-</span><span class="n">Darguments</span><span class="p">=</span>"$<span class="n">RELARGS</span>"
@@ -459,7 +470,7 @@ It doesn't change the POMs; it does veri
<li>Assuming you have an existing installation for testing, set <code>SLIDER_CONF_DIR</code> to the configuration directory, then
<code>slider start <INSTANCE></code> to start the relevant cluster instance. </li>
</ol>
-<h2 id="perform-a-dry-run-of-the-release">Perform a dry run of the release</h2>
+<h2 id="perform-a-dry-run-of-the-release">Perform a dry run of the release<a class="headerlink" href="#perform-a-dry-run-of-the-release" title="Permanent link">¶</a></h2>
<p>Perform a dry run. This will commit changes to your local branch.</p>
<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">release</span><span class="p">:</span><span class="n">prepare</span> <span class="o">-</span><span class="n">DdryRun</span><span class="p">=</span><span class="n">true</span> <span class="o">-</span><span class="n">DautoVersionSubmodules</span><span class="p">=</span><span class="n">true</span> <span class="o">-</span><span class="n">Darguments</span><span class="p">=</span>"$<span class="n">RELARGS</span>"
</pre></div>
@@ -474,7 +485,7 @@ versions. </li>
<li>Look at the output to verify the versions are what you want.</li>
<li>Roll back to the commit tagged earlier</li>
</ol>
-<h2 id="perform-the-maven-release">Perform the Maven release</h2>
+<h2 id="perform-the-maven-release">Perform the Maven release<a class="headerlink" href="#perform-the-maven-release" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">release</span><span class="p">:</span><span class="n">clean</span>
<span class="n">mvn</span> <span class="n">release</span><span class="p">:</span><span class="n">prepare</span> <span class="o">-</span><span class="n">DautoVersionSubmodules</span><span class="p">=</span><span class="n">true</span> <span class="o">-</span><span class="n">Darguments</span><span class="p">=</span>"$<span class="n">RELARGS</span>" <span class="o">-</span><span class="n">Dresume</span><span class="p">=</span><span class="n">false</span>
<span class="n">mvn</span> <span class="n">release</span><span class="p">:</span><span class="n">perform</span> <span class="o">-</span><span class="n">Darguments</span><span class="p">=</span>"$<span class="n">RELARGS</span>"
@@ -492,7 +503,7 @@ the staging process.</li>
Consult <a href="http://stackoverflow.com/questions/5343068/is-there-a-way-to-skip-password-typing-when-using-https-github">StackOverflow</a></p>
<p><em>rolling back</em>
After this phase (or when you cancel it), you'll need to roll back git,</p>
-<h3 id="tip-reverting-changes">Tip: reverting changes</h3>
+<h3 id="tip-reverting-changes">Tip: reverting changes<a class="headerlink" href="#tip-reverting-changes" title="Permanent link">¶</a></h3>
<p>Try</p>
<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">release</span><span class="p">:</span><span class="n">rollback</span>
</pre></div>
@@ -511,14 +522,14 @@ changing things. That should be the revi
</pre></div>
-<h3 id="tip-branching-instead-of-preparing">Tip: branching instead of preparing</h3>
+<h3 id="tip-branching-instead-of-preparing">Tip: branching instead of preparing<a class="headerlink" href="#tip-branching-instead-of-preparing" title="Permanent link">¶</a></h3>
<p>The <code>mvn release:branch</code> goal can be used instead of <code>mvn release:prepare</code>,
which creates a branch explicitly for the release. We haven't used this yet.</p>
-<h3 id="tip-validating-the-artifacts">Tip: Validating the artifacts</h3>
+<h3 id="tip-validating-the-artifacts">Tip: Validating the artifacts<a class="headerlink" href="#tip-validating-the-artifacts" title="Permanent link">¶</a></h3>
<p>There's a small projects <a href="https://github.com/steveloughran/slider-dependency-check">slider-dependency-check</a>
which verifies that slider artifacts can be downloaded from the public or staging repositories.
Clone this project and read its instructions to verify that everything went up to the staging repo.</p>
-<h2 id="close-the-release-in-nexus">Close the release in Nexus</h2>
+<h2 id="close-the-release-in-nexus">Close the release in Nexus<a class="headerlink" href="#close-the-release-in-nexus" title="Permanent link">¶</a></h2>
<ol>
<li>log in to <a href="https://repository.apache.org/index.html">https://repository.apache.org/index.html</a>
with your ASF username & LDAP password</li>
@@ -530,7 +541,7 @@ with your ASF username & LDAP passwo
<li>Wait for the close process to complete.</li>
<li>Get the URL of the closed staging repository. This is needed for the next step âthe votes.</li>
</ol>
-<h2 id="tell-jira-of-the-releases">Tell JIRA of the releases</h2>
+<h2 id="tell-jira-of-the-releases">Tell JIRA of the releases<a class="headerlink" href="#tell-jira-of-the-releases" title="Permanent link">¶</a></h2>
<p>Tell JIRA there's a new release. This moves it from "unreleased" to "released", creating a URL listing all issues fixed. </p>
<p>This URL can be used in the vote emails to highlight changes.</p>
<p><em>Important:</em> To perform this task, you must be registered as an admin for the
@@ -548,8 +559,8 @@ Slider project on JIRA.</p>
<li>Ideally, shorten it via the <a href="https://s.apache.org/">ASF Link shortener</a></li>
</ol>
<p>If the vote is cancelled, the release can be "unreleased". </p>
-<h2 id="get-the-votes-in">Get the Votes In</h2>
-<h3 id="set-up-your-env-vars-for-email-templates">Set up your env vars for email templates</h3>
+<h2 id="get-the-votes-in">Get the Votes In<a class="headerlink" href="#get-the-votes-in" title="Permanent link">¶</a></h2>
+<h3 id="set-up-your-env-vars-for-email-templates">Set up your env vars for email templates<a class="headerlink" href="#set-up-your-env-vars-for-email-templates" title="Permanent link">¶</a></h3>
<p>set up the environment with the git release tag, URL to the staging repository, and your ASF username:</p>
<div class="codehilite"><pre><span class="n">export</span> <span class="n">RELEASE_TAG</span><span class="p">=</span>
<span class="n">export</span> <span class="n">STAGING_REPO</span><span class="p">=</span>
@@ -574,7 +585,7 @@ Slider project on JIRA.</p>
</pre></div>
-<h3 id="call-for-a-release-vote-on-the-devslider-list">Call for a release vote on the dev@slider list</h3>
+<h3 id="call-for-a-release-vote-on-the-devslider-list">Call for a release vote on the dev@slider list<a class="headerlink" href="#call-for-a-release-vote-on-the-devslider-list" title="Permanent link">¶</a></h3>
<p>Call for a release VOTE to the dev mailing list (<code>dev@slider.incubator.apache.org</code>).</p>
<p>To build the URLs, echo them then verify in your browser that they are present.</p>
<p><strong>Subject:</strong>
@@ -606,11 +617,11 @@ http://slider.incubator.apache.org/devel
<ul>
<li>CHECK ALL THE URLS *</li>
</ul>
-<h3 id="wait-for-the-devslider-result">Wait for the dev@slider result</h3>
+<h3 id="wait-for-the-devslider-result">Wait for the dev@slider result<a class="headerlink" href="#wait-for-the-devslider-result" title="Permanent link">¶</a></h3>
<p>When it comes in, post the results in another email, with Subject -
<br>
[RESULT] [VOTE] Apache Slider Incubating Release $SLIDER_RELEASE</p>
-<h3 id="call-for-an-incubator-vote">Call for an incubator vote</h3>
+<h3 id="call-for-an-incubator-vote">Call for an incubator vote<a class="headerlink" href="#call-for-an-incubator-vote" title="Permanent link">¶</a></h3>
<p>If the VOTE passes, call for (the binding) VOTE from IPMC. Include the VOTE and RESULT threads from the developer mailing list.</p>
<ol>
<li>Go to the <a href="http://mail-archives.apache.org/mod_mbox/incubator-slider-dev/">Slider mail archives</a>.</li>
@@ -654,7 +665,7 @@ http://slider.incubator.apache.org/devel
<p>Thank You,
The Apache Slider Team
</pre></p>
-<h3 id="await-the-generalincubator-results-publish-them">Await the general@incubator results; publish them</h3>
+<h3 id="await-the-generalincubator-results-publish-them">Await the general@incubator results; publish them<a class="headerlink" href="#await-the-generalincubator-results-publish-them" title="Permanent link">¶</a></h3>
<p>After 72 hours, publish the results</p>
<p>Sample:</p>
<div class="codehilite"><pre><span class="n">Title</span><span class="p">:</span> <span class="p">[</span><span class="n">RESULT</span><span class="p">][</span><span class="n">VOTE</span><span class="p">]</span> <span class="n">Apache</span> <span class="n">Slider</span> $<span class="n">SLIDER_RELEASE</span> $<span class="n">RELEASE_RC</span>
@@ -671,7 +682,7 @@ The Apache Slider Team
<p>If the vote has been successful âyou may now release the artifacts.</p>
-<h2 id="publishing-the-nexus-staging-repository">Publishing the Nexus staging repository</h2>
+<h2 id="publishing-the-nexus-staging-repository">Publishing the Nexus staging repository<a class="headerlink" href="#publishing-the-nexus-staging-repository" title="Permanent link">¶</a></h2>
<p>Once âand only onceâ the incubator vote is successful, you may release the nexus-staged artifacts.</p>
<ol>
<li>Log in to <a href="https://repository.apache.org/index.html#stagingRepositories">the ASF Nexus server</a></li>
@@ -679,12 +690,12 @@ The Apache Slider Team
<li>In the toolbar above, press the <strong>release</strong> button</li>
</ol>
<p>Releasing "can take time", as the web site will inform you.</p>
-<h2 id="publishing-the-source-and-binary-tarzip-files">Publishing the source and binary tar/zip files</h2>
+<h2 id="publishing-the-source-and-binary-tarzip-files">Publishing the source and binary tar/zip files<a class="headerlink" href="#publishing-the-source-and-binary-tarzip-files" title="Permanent link">¶</a></h2>
<p>The ASF distribution system mirrors the source and binary files across all
apache mirror sites.</p>
<p>This the standard way which the archives are distributed.</p>
<p>Publish the release as below:</p>
-<h3 id="grab-the-released-artifacts-from-nexus">Grab the released artifacts from Nexus</h3>
+<h3 id="grab-the-released-artifacts-from-nexus">Grab the released artifacts from Nexus<a class="headerlink" href="#grab-the-released-artifacts-from-nexus" title="Permanent link">¶</a></h3>
<ol>
<li>Fetch the files from where released
(e.g. <a href="https://repository.apache.org/content/groups/public/org/apache/slider/slider-assembly/0.61.0-incubating/">slider-assembly 0.61</a></li>
@@ -709,7 +720,7 @@ the zip and tar files and their checksum
</li>
<li>Repeat for the source files <code>org/apache/slider/slider/$SLIDER_RELEASE</code></li>
</ol>
-<h3 id="check-out-the-distribution-dir-under-publishing">Check out the distribution dir under <code>publishing</code></h3>
+<h3 id="check-out-the-distribution-dir-under-publishing">Check out the distribution dir under <code>publishing</code><a class="headerlink" href="#check-out-the-distribution-dir-under-publishing" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">svn</span> <span class="n">co</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">dist</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">repos</span><span class="o">/</span><span class="n">dist</span><span class="o">/</span><span class="n">release</span><span class="o">/</span><span class="n">incubator</span><span class="o">/</span><span class="n">slider</span> <span class="n">slider</span><span class="o">-</span><span class="n">dist</span>
<span class="n">cd</span> <span class="n">slider</span><span class="o">-</span><span class="n">dist</span>
@@ -727,13 +738,13 @@ are at the top of that file</p>
<p>The commit can take time. In the past it has been rejected due to the size of
the patch...this has now been addressed and should remain so.</p>
-<h3 id="web-site-updates">Web site updates</h3>
+<h3 id="web-site-updates">Web site updates<a class="headerlink" href="#web-site-updates" title="Permanent link">¶</a></h3>
<p>Update the Slider website as needed. Most of the documents would have been
updated by now to reflect the released version.
<em>The remaining changes should really be modifying the references to the latest release to the new version.</em></p>
<p>The download details for the latest release needs to be updated after mirrors are updated in . </p>
<p>Verify the download links at <a href="http://slider.incubator.apache.org">Slider Page</a>.</p>
-<h2 id="announcing">Announcing</h2>
+<h2 id="announcing">Announcing<a class="headerlink" href="#announcing" title="Permanent link">¶</a></h2>
<p>Send an announcement:</p>
<p>The released artifacts may take up to 24 hours to replicate to the mirrors.</p>
<p>Send an announcement to the Slider dev, Slider user, and the general Apache announcement (<code>announce@apache.org</code>) list after the bits have replicated.
@@ -773,16 +784,16 @@ To send the message to <code>announce@ap
</pre></div>
-<h2 id="update-the-site">Update the site</h2>
+<h2 id="update-the-site">Update the site<a class="headerlink" href="#update-the-site" title="Permanent link">¶</a></h2>
<ol>
<li>Update documentation in the svn site repo. In particular, review
<code>content/downloads/index.md</code></li>
<li><a href="https://cms.apache.org/slider/publish">trigger a site rebuild</a>.</li>
</ol>
-<h2 id="finish-the-jira">Finish the JIRA</h2>
+<h2 id="finish-the-jira">Finish the JIRA<a class="headerlink" href="#finish-the-jira" title="Permanent link">¶</a></h2>
<p>Log the time, close the issue. This should normally be the end of a
sprint âso wrap that up too.</p>
-<h2 id="get-back-to-developing">Get back to developing!</h2>
+<h2 id="get-back-to-developing">Get back to developing!<a class="headerlink" href="#get-back-to-developing" title="Permanent link">¶</a></h2>
<p>Check out the develop branch and purge all release artifacts</p>
<div class="codehilite"><pre><span class="n">git</span> <span class="n">checkout</span> <span class="n">develop</span>
<span class="n">git</span> <span class="n">pull</span> <span class="n">origin</span>
Modified: websites/staging/slider/trunk/content/developing/releasing_process_v1.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/releasing_process_v1.html (original)
+++ websites/staging/slider/trunk/content/developing/releasing_process_v1.html Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block" href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
@@ -185,7 +196,7 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License.
-->
-<h1 id="apache-slider-release-process-v1">Apache Slider Release Process v1</h1>
+<h1 id="apache-slider-release-process-v1">Apache Slider Release Process v1<a class="headerlink" href="#apache-slider-release-process-v1" title="Permanent link">¶</a></h1>
<p>This was release process for Slider versions up to and including Slider 0.60,
which was released in November 2014.</p>
<p>The process was superceded in January 2015 âlater releases follow the process
@@ -195,7 +206,7 @@ described in <a href="releasing.html">Re
<li><a href="#phase1">Phase I</a>: Merge <code>develop</code> branch with <code>master</code> so that you can release from <code>master</code></li>
<li><a href="#phase2">Phase II</a>: Perform Apache release from <code>master</code></li>
</ul>
-<h3 id="tooling">Tooling</h3>
+<h3 id="tooling">Tooling<a class="headerlink" href="#tooling" title="Permanent link">¶</a></h3>
<p>As well as everything needed to build slider, there are some extra requirements
for releasing:</p>
<ol>
@@ -205,7 +216,7 @@ for releasing:</p>
This can perform the git flow operations, as well as show the state of your
git graph.</li>
</ol>
-<h3 id="before-you-begin">Before you begin</h3>
+<h3 id="before-you-begin">Before you begin<a class="headerlink" href="#before-you-begin" title="Permanent link">¶</a></h3>
<p><em>1.</em> Check out the latest version of the develop branch,
run the tests. This should be done on a checked out
version of the code that is not the one you are developing on
@@ -229,11 +240,11 @@ starting to make a release</em></p>
<li>Note the git revision number of this build -for documentation.</li>
<li>Maybe: tag that revision so you can easily revert to it</li>
</ol>
-<h5 id="profiles">Profiles</h5>
+<h5 id="profiles">Profiles<a class="headerlink" href="#profiles" title="Permanent link">¶</a></h5>
<p>The slider POMs offer different profiles of hadoop versions to build against. The instructions
below do not choose one. If a profile is needed, append it to all the maven commands.</p>
<p>e.g. <code>mvn clean install -DskipTests -Prelease-2.6</code></p>
-<h2 id="phase-i"><a name="phase1"></a>Phase - I</h2>
+<h2 id="phase-i"><a name="phase1"></a>Phase - I<a class="headerlink" href="#phase-i" title="Permanent link">¶</a></h2>
<p><strong>Step #0:</strong> Sync up with the ASF repo. You do not want to release the wrong
code.</p>
<div class="codehilite"><pre><span class="n">git</span> <span class="n">checkout</span> <span class="n">develop</span>
@@ -366,7 +377,7 @@ sprint -so wrap that up too.</p>
<p><em>At this point you are ready for Apache release from master.</em></p>
-<h2 id="phase-ii-publish-to-the-asf"><a name="phase2"></a>Phase - II: publish to the ASF</h2>
+<h2 id="phase-ii-publish-to-the-asf"><a name="phase2"></a>Phase - II: publish to the ASF<a class="headerlink" href="#phase-ii-publish-to-the-asf" title="Permanent link">¶</a></h2>
<p>This phase of the process creates the artifacts for the ASF.
This is done in a separate directory to ensure that nothing accidentally gets in.</p>
<p>Preamble: set up the RC Version </p>
@@ -600,7 +611,7 @@ Slider project on JIRA.</p>
<p>Go to the <a href="https://issues.apache.org/jira/plugins/servlet/project-config/SLIDER/versions">Slider Versions page</a></p>
<p>Release the version you've done, carrying forward issues that haven't been done
yet.</p>
-<h2 id="hotfixing-a-release">Hotfixing a release</h2>
+<h2 id="hotfixing-a-release">Hotfixing a release<a class="headerlink" href="#hotfixing-a-release" title="Permanent link">¶</a></h2>
<p>If you need to change a release âsuch as to issue a new RC, you must
create a hotfix release which updates the <code>master/</code> and <code>develop/</code> branches.
you can then create a new release off the last commit off the hotfix branch
@@ -666,13 +677,13 @@ the actual development version.</p>
<p>Continue the release process from step 12.</p>
</li>
</ol>
-<h2 id="publishing-artifacts">Publishing artifacts</h2>
+<h2 id="publishing-artifacts">Publishing artifacts<a class="headerlink" href="#publishing-artifacts" title="Permanent link">¶</a></h2>
<p>Once the vote has (successfully) completed on both slider-dev and incubator-general, the artifacts may be published in two ways</p>
<ol>
<li>tarballs for download via the apache distribution system</li>
<li>JAR files for download via the maven repository</li>
</ol>
-<h3 id="publishing-files-for-apache-release">Publishing files for apache release</h3>
+<h3 id="publishing-files-for-apache-release">Publishing files for apache release<a class="headerlink" href="#publishing-files-for-apache-release" title="Permanent link">¶</a></h3>
<p>See the <a href="http://www.apache.org/dev/release.html">ASF release guidelines</a></p>
</div>
Modified: websites/staging/slider/trunk/content/developing/style.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/style.html (original)
+++ websites/staging/slider/trunk/content/developing/style.html Mon Nov 2 17:24:47 2015
@@ -155,7 +155,7 @@
<div style="text-align: center">
<h1><a href="/index.html">Apache Slider (incubating)</a></h1>
<hr>
-Latest release: <strong>0.80.0-incubating</strong><br>
+Latest release: <strong>0.81.1-incubating</strong><br>
<br>
<a id="download-button-sidebar" class="btn btn-success btn-block" href="/downloads/" role="button">Download</a>
</div>
@@ -168,7 +168,18 @@ Latest release: <strong>0.80.0-incubatin
<h1 class="title"></h1>
- <!---
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<!---
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
@@ -182,14 +193,14 @@ Latest release: <strong>0.80.0-incubatin
limitations under the License. See accompanying LICENSE file.
-->
-<h1 id="slider-code-style-rules">Slider Code Style Rules</h1>
+<h1 id="slider-code-style-rules">Slider Code Style Rules<a class="headerlink" href="#slider-code-style-rules" title="Permanent link">¶</a></h1>
<p>The [Hadoop Guidelines|https://wiki.apache.org/hadoop/CodeReviewChecklist] apply to the slider code
with some minor changes</p>
-<h3 id="all">All</h3>
+<h3 id="all">All<a class="headerlink" href="#all" title="Permanent link">¶</a></h3>
<ul>
<li>Lines can be up to 100 characters long.</li>
</ul>
-<h3 id="java">Java</h3>
+<h3 id="java">Java<a class="headerlink" href="#java" title="Permanent link">¶</a></h3>
<ul>
<li>
<p>SLF4J is the logging platform. Log operations do not need to be guarded with <code>f (log.isDebugEnabled())</code> statements; instead the log string should reference variables inline with <code>{}</code> references, rather than append strings to build the log statements.</p>
@@ -198,7 +209,7 @@ with some minor changes</p>
<p>Provide meaningful <code>toString()</code> operations for debugging, logging and assertions.</p>
</li>
</ul>
-<h3 id="groovy">Groovy</h3>
+<h3 id="groovy">Groovy<a class="headerlink" href="#groovy" title="Permanent link">¶</a></h3>
<p>Groovy is used for most of our test cases. It's style guidelines are similar to those of the
Java guidelines</p>
<ul>
@@ -213,11 +224,11 @@ Java guidelines</p>
<em> the rules of how strings are evaluated to true or false in conditions, or the more [esoteric operators|http://groovy.codehaus.org/Operators] such as 'spaceship' or 'elvis'
</em> automatic return values of functions (except for very short ones)
* applying actions across entire list elements. (if used: comment)</p>
-<h3 id="python">Python</h3>
+<h3 id="python">Python<a class="headerlink" href="#python" title="Permanent link">¶</a></h3>
<ul>
<li>Python files must use an indentation of four characters.</li>
</ul>
-<h3 id="maven-pom-files">Maven POM files</h3>
+<h3 id="maven-pom-files">Maven POM files<a class="headerlink" href="#maven-pom-files" title="Permanent link">¶</a></h3>
<ul>
<li>Versions of artifacts (and template dependency definitions) MUST go into the root <code>slider/pom.xml</code>; individual modules MUST then repeat the dependency declaration, <em>excluding version and exclusion details</em>. This is to keep versions consistent across the project.</li>
</ul>