svn commit: r930595 - in /websites/staging/slider/trunk/content: ./ design/architecture.html docs/configuration/index.html docs/manpage.html

[bu...@apache.org]

Author: buildbot
Date: Wed Nov 26 15:40:30 2014
New Revision: 930595

Log:
Staging update by buildbot for slider

Modified:
    websites/staging/slider/trunk/content/   (props changed)
    websites/staging/slider/trunk/content/design/architecture.html
    websites/staging/slider/trunk/content/docs/configuration/index.html
    websites/staging/slider/trunk/content/docs/manpage.html

Propchange: websites/staging/slider/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Nov 26 15:40:30 2014
@@ -1 +1 @@
-1641675
+1641837

Modified: websites/staging/slider/trunk/content/design/architecture.html
==============================================================================
--- websites/staging/slider/trunk/content/design/architecture.html (original)
+++ websites/staging/slider/trunk/content/design/architecture.html Wed Nov 26 15:40:30 2014
@@ -245,19 +245,6 @@ the YARN resource manager.</p>
 <p>The final operation, <code>stopCluster()</code>, stops the application instance. </p>
 <h3 id="security-and-identity">Security and Identity</h3>
 <p>Slider's security model is described in detail in <a href="/docs/security.html">an accompanying document</a></p>
-<p>A Slider application instance is expected to access data belonging to the user creating the instance. </p>
-<p>In a secure YARN cluster, this is done by acquiring Kerberos tokens in the client when the application instance is updated, tokens which
-are propagated to the Slider AM and thence to the deployed application containers themselves. These
-tokens are valid for a finite time period. </p>
-<p>HBase has always required keytab files to be installed on every node in the Hadoop for it to have secure access -this requirement
-holds for Slider-deployed HBase clusters. Slider does not itself adopt the responsibility of preparing or distributing these files;
-this must be done via another channel.</p>
-<p>In Hadoop 2.2, the tokens for communication between the Slider AM and YARN expire after -by default- 72 hours. The
-HDFS tokens will also expire after some time period. This places an upper bound on the lifespan of a Slider application (or any
-other long-lived YARN application) in a secure Hadoop cluster. </p>
-<p>In an insecure Hadoopp cluster, the Slider AM and its containers are likely to run in a different OS account from the submitting user.
-To enable access to the database files as that submitting use, the identity of the user is provided when the AM is created; the
-AM will pass this same identity down to the created containers. This information <em>identifies</em> the user -but does not <em>authenticate</em> them: they are trusted to be who they claim to be.</p>
 <h3 id="agent-to-application-master-secure-communication">Agent to Application Master Secure Communication</h3>
 <p>By default, one-way SSL is leveraged to secure the communication between Slider agents and the Application Master.  However, two-way SSL can be enabled.  A more detailed discussion of the SSL implementation in Slider can be found <a href="/design/ssl_implementation.html">in the SSL documentation</a>.</p>
   </div>

Modified: websites/staging/slider/trunk/content/docs/configuration/index.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/configuration/index.html (original)
+++ websites/staging/slider/trunk/content/docs/configuration/index.html Wed Nov 26 15:40:30 2014
@@ -178,12 +178,14 @@ Latest release: <strong>0.60.0-incubatin
 -->
 
 <h1 id="apache-slider-specification-of-an-application-instance-revision-20">Apache Slider: Specification of an application instance, revision 2.0</h1>
-<p>The specification of an applicaton, comprises
-1. The persistent description of an application's configuration
-1. The persistent description of the desired topology and YARN resource
-requirements.
-1. The dynamic description of the running application, including information
-on the location of components and aggregated statistics. </p>
+<p>The specification of an application comprises</p>
+<ol>
+<li>The persistent description of an application's configuration</li>
+<li>The persistent description of the desired topology and YARN resource
+requirements.</li>
+<li>The dynamic description of the running application, including information
+on the location of components and aggregated statistics. </li>
+</ol>
 <p>The specifics of this are covered in the <a href="core.html">Core Configuration Specification</a></p>
 <h2 id="historical-references">Historical References</h2>
 <ol>

Modified: websites/staging/slider/trunk/content/docs/manpage.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/manpage.html (original)
+++ websites/staging/slider/trunk/content/docs/manpage.html Wed Nov 26 15:40:30 2014
@@ -193,24 +193,6 @@ and existing but not running "stopped" a
 <p>A <em>Slider application instance</em>  is a slider application configured to be deployable on a specific YARN cluster, with a specific configuration. An instance can be <em>live</em> -actually running- or <em>stopped</em>. When stopped all its configuration details and instance-specific data are preserved on HDFS.</p>
 </li>
 <li>
-<p>An <em>image</em> is a <em>tar.gz</em> file containing binaries used to create the application.  1. Images are kept in the HDFS filesystem and identified by their path names; filesystem permissions can be used to share images amongst users.</p>
-</li>
-<li>
-<p>An <em>image configuration</em> is a directory that is overlaid file-by-file onto the conf/ directory inside the HBase image.</p>
-</li>
-<li>
-<p>Users can have multiple image configurations -they too are kept in HDFS, identified by their path names, and can be shared by setting the appropriate permissions, along with a configuration template file.</p>
-</li>
-<li>
-<p>Only those files provided in the image configuration directory overwrite the default values contained in the image; all other configuration files are retained.</p>
-</li>
-<li>
-<p>Late-binding properties can also be provided at create time.</p>
-</li>
-<li>
-<p>Slider can overwrite some of the configuration properties to enable the dynamically created components to bind correctly to each other.</p>
-</li>
-<li>
 <p>An <em>instance directory</em> is a directory created in HDFS describing the application instance; it records the configuration -both user specified, application-default and any dynamically created by slider. </p>
 </li>
 <li>