aurora-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jco...@apache.org
Subject svn commit: r1762695 [13/19] - in /aurora/site: data/ publish/ publish/documentation/0.10.0/ publish/documentation/0.10.0/build-system/ publish/documentation/0.10.0/client-cluster-configuration/ publish/documentation/0.10.0/client-commands/ publish/doc...
Date Wed, 28 Sep 2016 18:23:59 GMT
Modified: aurora/site/publish/documentation/latest/operations/configuration/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/operations/configuration/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/operations/configuration/index.html (original)
+++ aurora/site/publish/documentation/latest/operations/configuration/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/operations/configuration/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >
@@ -118,8 +122,9 @@ documentation, see <a href="../../refere
 <span style="color: #999988;font-style: italic"># Environment variables controlling libmesos</span>
 <span style="color: #0086B3">export </span><span style="color: #008080">JAVA_HOME</span><span style="color: #000000;font-weight: bold">=</span>...
 <span style="color: #0086B3">export </span><span style="color: #008080">GLOG_v</span><span style="color: #000000;font-weight: bold">=</span>1
-<span style="color: #999988;font-style: italic"># Port used to communicate with the Mesos master and for the replicated log</span>
+<span style="color: #999988;font-style: italic"># Port and public ip used to communicate with the Mesos master and for the replicated log</span>
 <span style="color: #0086B3">export </span><span style="color: #008080">LIBPROCESS_PORT</span><span style="color: #000000;font-weight: bold">=</span>8083
+<span style="color: #0086B3">export </span><span style="color: #008080">LIBPROCESS_IP</span><span style="color: #000000;font-weight: bold">=</span>192.168.33.7
 
 <span style="color: #008080">JAVA_OPTS</span><span style="color: #000000;font-weight: bold">=</span><span style="color: #d14">"</span><span style="color: #000000;font-weight: bold">${</span><span style="color: #008080">JAVA_OPTS</span><span style="background-color: #f8f8f8">[*]</span><span style="color: #000000;font-weight: bold">}</span><span style="color: #d14">"</span> <span style="color: #0086B3">exec</span> <span style="color: #d14">"</span><span style="color: #008080">$AURORA_HOME</span><span style="color: #d14">/bin/aurora-scheduler"</span> <span style="color: #d14">"</span><span style="color: #000000;font-weight: bold">${</span><span style="color: #008080">AURORA_FLAGS</span><span style="background-color: #f8f8f8">[@]</span><span style="color: #000000;font-weight: bold">}</span><span style="color: #d14">"</span>
 </code></pre>
@@ -178,7 +183,7 @@ for Mesos replicated log files to ensure
 
 <p>ZooKeeper path used for Mesos replicated log quorum discovery.</p>
 
-<p>See <a href="https://github.com/apache/aurora/blob/rel/0.15.0/src/main/java/org/apache/aurora/scheduler/log/mesos/MesosLogStreamModule.java">code</a> for
+<p>See <a href="https://github.com/apache/aurora/blob/rel/0.16.0/src/main/java/org/apache/aurora/scheduler/log/mesos/MesosLogStreamModule.java">code</a> for
 other available Mesos replicated log configuration options and default values.</p>
 
 <h3 id="changing-the-quorum-size">Changing the Quorum Size</h3>
@@ -199,26 +204,119 @@ or truncating of the replicated log used
 
 <p>Configuration options for the Aurora scheduler backup manager.</p>
 
-<h3 id="backup_interval"><code>-backup_interval</code></h3>
+<ul>
+<li><code>-backup_interval</code>: The interval on which the scheduler writes local storage backups.  The default is every hour.</li>
+<li><code>-backup_dir</code>: Directory to write backups to.</li>
+<li><code>-max_saved_backups</code>: Maximum number of backups to retain before deleting the oldest backup(s).</li>
+</ul>
+
+<h2 id="resource-isolation">Resource Isolation</h2>
+
+<p>For proper CPU, memory, and disk isolation as mentioned in our <a href="../../features/resource-isolation/">enduser documentation</a>,
+we recommend to add the following isolators to the <code>--isolation</code> flag of the Mesos agent:</p>
+
+<ul>
+<li><code>cgroups/cpu</code></li>
+<li><code>cgroups/mem</code></li>
+<li><code>disk/du</code></li>
+</ul>
+
+<p>In addition, we recommend to set the following <a href="http://mesos.apache.org/documentation/latest/configuration/">agent flags</a>:</p>
+
+<ul>
+<li><code>--cgroups_limit_swap</code> to enable memory limits on both memory and swap instead of just memory.
+Alternatively, you could disable swap on your agent hosts.</li>
+<li><code>--cgroups_enable_cfs</code> to enable hard limits on CPU resources via the CFS bandwidth limiting
+feature.</li>
+<li><code>--enforce_container_disk_quota</code> to enable disk quota enforcement for containers.</li>
+</ul>
+
+<p>To enable the optional GPU support in Mesos, please see the GPU related flags in the
+<a href="http://mesos.apache.org/documentation/latest/configuration/">Mesos configuration</a>.
+To enable the corresponding feature in Aurora, you have to start the scheduler with the
+flag</p>
+<pre class="highlight plaintext"><code>-allow_gpu_resource=true
+</code></pre>
+
+<p>If you want to use revocable resources, first follow the
+<a href="http://mesos.apache.org/documentation/latest/oversubscription/">Mesos oversubscription documentation</a>
+and then set set this Aurora scheduler flag to allow receiving revocable Mesos offers:</p>
+<pre class="highlight plaintext"><code>-receive_revocable_resources=true
+</code></pre>
+
+<p>Both CPUs and RAM are supported as revocable resources. The former is enabled by the default,
+the latter needs to be enabled via:</p>
+<pre class="highlight plaintext"><code>-enable_revocable_ram=true
+</code></pre>
+
+<p>Unless you want to use the <a href="https://github.com/apache/aurora/blob/rel/0.16.0/src/main/resources/org/apache/aurora/scheduler/tiers.json">default</a>
+tier configuration, you will also have to specify a file path:</p>
+<pre class="highlight plaintext"><code>-tier_config=path/to/tiers/config.json
+</code></pre>
+
+<h2 id="containers">Containers</h2>
 
-<p>The interval on which the scheduler writes local storage backups.  The default is every hour.</p>
+<p>Both the Mesos and Docker containerizers require configuration of the Mesos agent.</p>
 
-<h3 id="backup_dir"><code>-backup_dir</code></h3>
+<h3 id="mesos-containerizer">Mesos Containerizer</h3>
 
-<p>Directory to write backups to.</p>
+<p>The minimal agent configuration requires to enable Docker and Appc image support for the Mesos
+containerizer:</p>
+<pre class="highlight plaintext"><code>--containerizers=mesos
+--image_providers=appc,docker
+--isolation=filesystem/linux,docker/runtime  # as an addition to your other isolators
+</code></pre>
+
+<p>Further details can be found in the corresponding <a href="http://mesos.apache.org/documentation/latest/container-image/">Mesos documentation</a>.</p>
 
-<h3 id="max_saved_backups"><code>-max_saved_backups</code></h3>
+<h3 id="docker-containerizer">Docker Containerizer</h3>
 
-<p>Maximum number of backups to retain before deleting the oldest backup(s).</p>
+<p>The <a href="http://mesos.apache.org/documentation/latest/docker-containerizer/">Docker containerizer</a>
+requires the Docker engine is installed on each agent host. In addition, it  must be enabled on the
+Mesos agents by launching them with the option:</p>
+<pre class="highlight plaintext"><code>--containerizers=mesos,docker
+</code></pre>
 
-<h2 id="process-logs">Process Logs</h2>
+<p>If you would like to run a container with a read-only filesystem, it may also be necessary to use
+the scheduler flag <code>-thermos_home_in_sandbox</code> in order to set HOME to the sandbox
+before the executor runs. This will make sure that the executor/runner PEX extractions happens
+inside of the sandbox instead of the container filesystem root.</p>
+
+<p>If you would like to supply your own parameters to <code>docker run</code> when launching jobs in docker
+containers, you may use the following flags:</p>
+<pre class="highlight plaintext"><code>-allow_docker_parameters
+-default_docker_parameters
+</code></pre>
+
+<p><code>-allow_docker_parameters</code> controls whether or not users may pass their own configuration parameters
+through the job configuration files. If set to <code>false</code> (the default), the scheduler will reject
+jobs with custom parameters. <em>NOTE</em>: this setting should be used with caution as it allows any job
+owner to specify any parameters they wish, including those that may introduce security concerns
+(<code>privileged=true</code>, for example).</p>
+
+<p><code>-default_docker_parameters</code> allows a cluster operator to specify a universal set of parameters that
+should be used for every container that does not have parameters explicitly configured at the job
+level. The argument accepts a multimap format:</p>
+<pre class="highlight plaintext"><code>-default_docker_parameters="read-only=true,tmpfs=/tmp,tmpfs=/run"
+</code></pre>
+
+<h3 id="common-options">Common Options</h3>
+
+<p>The following Aurora options work for both containerizers.</p>
+
+<p>A scheduler flag, <code>-global_container_mounts</code> allows mounting paths from the host (i.e the agent machine)
+into all containers on that host. The format is a comma separated list of host<em>path:container</em>path[:mode]
+tuples. For example <code>-global_container_mounts=/opt/secret_keys_dir:/mnt/secret_keys_dir:ro</code> mounts
+<code>/opt/secret_keys_dir</code> from the agents into all launched containers. Valid modes are <code>ro</code> and <code>rw</code>.</p>
+
+<h2 id="thermos-process-logs">Thermos Process Logs</h2>
 
 <h3 id="log-destination">Log destination</h3>
 
-<p>By default, Thermos will write process stdout/stderr to log files in the sandbox. Process object configuration
-allows specifying alternate log file destinations like streamed stdout/stderr or suppression of all log output.
-Default behavior can be configured for the entire cluster with the following flag (through the <code>-thermos_executor_flags</code>
-argument to the Aurora scheduler):</p>
+<p>By default, Thermos will write process stdout/stderr to log files in the sandbox. Process object
+configuration allows specifying alternate log file destinations like streamed stdout/stderr or
+suppression of all log output. Default behavior can be configured for the entire cluster with the
+following flag (through the <code>-thermos_executor_flags</code> argument to the Aurora scheduler):</p>
 <pre class="highlight plaintext"><code>--runner-logger-destination=both
 </code></pre>
 
@@ -232,7 +330,7 @@ argument to the Aurora scheduler):</p>
 without bound. An individual user may change this behavior via configuration on the Process object,
 but it may also be desirable to change the default configuration for the entire cluster.
 In order to enable rotation by default, the following flags can be applied to Thermos (through the
--thermos<em>executor</em>flags argument to the Aurora scheduler):</p>
+<code>-thermos_executor_flags</code> argument to the Aurora scheduler):</p>
 <pre class="highlight plaintext"><code>--runner-logger-mode=rotate
 --runner-rotate-log-size-mb=100
 --runner-rotate-log-backups=10
@@ -244,248 +342,29 @@ their process, it will override these de
 
 <h2 id="thermos-executor-wrapper">Thermos Executor Wrapper</h2>
 
-<p>If you need to do computation before starting the thermos executor (for example, setting a different
-<code>--announcer-hostname</code> parameter for every executor), then the thermos executor should be invoked
- inside a wrapper script. In such a case, the aurora scheduler should be started with
- <code>-thermos_executor_path</code> pointing to the wrapper script and <code>-thermos_executor_resources</code>
- set to a comma separated string of all the resources that should be copied into
- the sandbox (including the original thermos executor).</p>
+<p>If you need to do computation before starting the Thermos executor (for example, setting a different
+<code>--announcer-hostname</code> parameter for every executor), then the Thermos executor should be invoked
+inside a wrapper script. In such a case, the aurora scheduler should be started with
+<code>-thermos_executor_path</code> pointing to the wrapper script and <code>-thermos_executor_resources</code> set to a
+comma separated string of all the resources that should be copied into the sandbox (including the
+original Thermos executor). Ensure the wrapper script does not access resources outside of the
+sandbox, as when the script is run from within a Docker container those resources may not exist.</p>
 
 <p>For example, to wrap the executor inside a simple wrapper, the scheduler will be started like this
 <code>-thermos_executor_path=/path/to/wrapper.sh -thermos_executor_resources=/usr/share/aurora/bin/thermos_executor.pex</code></p>
 
-<h2 id="custom-executor

">Custom Executor

</h2>
-
-<p>If the need arises to use a Mesos executor other than the Thermos executor, the scheduler can be
-configured to utilize a custom executor by specifying the <code>-custom_executor_config</code> flag.
-The flag must be set to the path of a valid executor configuration file.
</p>
-
-<p>The configuration file must be valid JSON and contain, at minimum, the name, command and resources fields.</p>
-
-<h3 id="executor">executor</h3>
-
-<table><thead>
-<tr>
-<th>Property</th>
-<th>Description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td>name (required)</td>
-<td>Name of the executor.</td>
-</tr>
-<tr>
-<td>command (required)</td>
-<td>How to run the executor.</td>
-</tr>
-<tr>
-<td>resources (required)</td>
-<td>Overhead to use for each executor instance.</td>
-</tr>
-</tbody></table>
-
-<h4 id="command">command</h4>
-
-<table><thead>
-<tr>
-<th>Property</th>
-<th>Description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td>value (required)</td>
-<td>The command to execute.</td>
-</tr>
-<tr>
-<td>arguments (optional)</td>
-<td>A list of arguments to pass to the command.</td>
-</tr>
-<tr>
-<td>uris (optional)</td>
-<td>List of resources to download into the task sandbox.</td>
-</tr>
-</tbody></table>
-
-<h5 id="uris-list">uris (list)</h5>
-
-<ul>
-<li>Follows the <a href="http://mesos.apache.org/documentation/latest/fetcher/">Mesos Fetcher schema</a></li>
-</ul>
-
-<table><thead>
-<tr>
-<th>Property</th>
-<th>Description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td>value (required)</td>
-<td>Path to the resource needed in the sandbox.</td>
-</tr>
-<tr>
-<td>executable (optional)</td>
-<td>Change resource to be executable via chmod.</td>
-</tr>
-<tr>
-<td>extract (optional)</td>
-<td>Extract files from packed or compressed archives into the sandbox.</td>
-</tr>
-<tr>
-<td>cache (optional)</td>
-<td>Use caching mechanism provided by Mesos for resources.</td>
-</tr>
-</tbody></table>
+<h2 id="custom-executors">Custom Executors</h2>
 
-<h4 id="resources-list">resources (list)</h4>
+<p>The scheduler can be configured to utilize a custom executor by specifying the <code>-custom_executor_config</code> flag.
+The flag must be set to the path of a valid executor configuration file.</p>
 
-<table><thead>
-<tr>
-<th>Property</th>
-<th>Description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td>name (required)</td>
-<td>Name of the resource: cpus or mem.</td>
-</tr>
-<tr>
-<td>type (required)</td>
-<td>Type of resource. Should always be SCALAR.</td>
-</tr>
-<tr>
-<td>scalar (required)</td>
-<td>Value in float for cpus or int for mem (in MBs)</td>
-</tr>
-</tbody></table>
+<p>For more information on this feature please see the custom executors <a href="../../features/custom-executors/">documentation</a>.</p>
 
-<h3 id="volume_mounts-list">volume_mounts (list)</h3>
+<h2 id="a-note-on-increasing-executor-overhead">A note on increasing executor overhead</h2>
 
-<table><thead>
-<tr>
-<th>Property</th>
-<th>Description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td>host_path (required)</td>
-<td>Host path to mount inside the container.</td>
-</tr>
-<tr>
-<td>container_path (required)</td>
-<td>Path inside the container where <code>host_path</code> will be mounted.</td>
-</tr>
-<tr>
-<td>mode (required)</td>
-<td>Mode in which to mount the volume, Read-Write (RW) or Read-Only (RO).</td>
-</tr>
-</tbody></table>
-
-<p>A sample configuration is as follows:

-<code>
-     {
-       &quot;executor&quot;: {
-         &quot;name&quot;: &quot;myExecutor&quot;,
-         &quot;command&quot;: {
-           &quot;value&quot;: &quot;myExecutor.sh&quot;,
-           &quot;arguments&quot;: [
-             &quot;localhost:2181&quot;,
-             &quot;-verbose&quot;,
-             &quot;-config myConfiguration.config&quot;
-           ],
-           &quot;uris&quot;: [
-             {
-               &quot;value&quot;: &quot;/dist/myExecutor.sh&quot;,
-               &quot;executable&quot;: true,
-               &quot;extract&quot;: false,
-               &quot;cache&quot;: true
-             },
-             {
-               &quot;value&quot;: &quot;/home/user/myConfiguration.config&quot;,
-               &quot;executable&quot;: false,
-               &quot;extract&quot;: false,
-               &quot;cache&quot;: false
-             }
-           ]
-         },
-         &quot;resources&quot;: [
-           {
-             &quot;name&quot;: &quot;cpus&quot;,
-             &quot;type&quot;: &quot;SCALAR&quot;,
-             &quot;scalar&quot;: {
-               &quot;value&quot;: 1.00
-             }
-           },
-           {
-             &quot;name&quot;: &quot;mem&quot;,
-             &quot;type&quot;: &quot;SCALAR&quot;,
-             &quot;scalar&quot;: {
-               &quot;value&quot;: 512
-             }
-           }
-         ]
-       },
-       &quot;volume_mounts&quot;: [
-         {
-           &quot;mode&quot;: &quot;RO&quot;,
-           &quot;container_path&quot;: &quot;/path/on/container&quot;,
-           &quot;host_path&quot;: &quot;/path/to/host/directory&quot;
-         },
-         {
-           &quot;mode&quot;: &quot;RW&quot;,
-           &quot;container_path&quot;: &quot;/container&quot;,
-           &quot;host_path&quot;: &quot;/host&quot;
-         }
-       ]
-     }
-</code></p>
-
-<p>It should be noted that if you do not use thermos or a thermos based executor, links in the scheduler&rsquo;s
-Web UI for tasks
 will not work (at least for the time being).
-Some information about launched tasks can still be accessed via the Mesos Web UI or via the Aurora Client.
-Furthermore, this configuration replaces the default thermos executor.
-Work is in progress to allow support for multiple executors to co-exist within a single scheduler.</p>
-
-<h3 id="docker-containers">Docker containers</h3>
-
-<p>In order for Aurora to launch jobs using docker containers, a few extra configuration options
-must be set.  The <a href="http://mesos.apache.org/documentation/latest/docker-containerizer/">docker containerizer</a>
-must be enabled on the Mesos agents by launching them with the <code>--containerizers=docker,mesos</code> option.</p>
-
-<p>By default, Aurora will configure Mesos to copy the file specified in <code>-thermos_executor_path</code>
-into the container&rsquo;s sandbox.  If using a wrapper script to launch the thermos executor,
-specify the path to the wrapper in that argument. In addition, the path to the executor pex itself
-must be included in the <code>-thermos_executor_resources</code> option. Doing so will ensure that both the
-wrapper script and executor are correctly copied into the sandbox. Finally, ensure the wrapper
-script does not access resources outside of the sandbox, as when the script is run from within a
-docker container those resources will not exist.</p>
-
-<p>A scheduler flag, <code>-global_container_mounts</code> allows mounting paths from the host (i.e the agent machine)
-into all containers on that host. The format is a comma separated list of host<em>path:container</em>path[:mode]
-tuples. For example <code>-global_container_mounts=/opt/secret_keys_dir:/mnt/secret_keys_dir:ro</code> mounts
-<code>/opt/secret_keys_dir</code> from the agents into all launched containers. Valid modes are <code>ro</code> and <code>rw</code>.</p>
-
-<p>If you would like to run a container with a read-only filesystem, it may also be necessary to
-pass to use the scheduler flag <code>-thermos_home_in_sandbox</code> in order to set HOME to the sandbox
-before the executor runs. This will make sure that the executor/runner PEX extractions happens
-inside of the sandbox instead of the container filesystem root.</p>
-
-<p>If you would like to supply your own parameters to <code>docker run</code> when launching jobs in docker
-containers, you may use the following flags:</p>
-<pre class="highlight plaintext"><code>-allow_docker_parameters
--default_docker_parameters
-</code></pre>
-
-<p><code>-allow_docker_parameters</code> controls whether or not users may pass their own configuration parameters
-through the job configuration files. If set to <code>false</code> (the default), the scheduler will reject
-jobs with custom parameters. <em>NOTE</em>: this setting should be used with caution as it allows any job
-owner to specify any parameters they wish, including those that may introduce security concerns
-(<code>privileged=true</code>, for example).</p>
-
-<p><code>-default_docker_parameters</code> allows a cluster operator to specify a universal set of parameters that
-should be used for every container that does not have parameters explicitly configured at the job
-level. The argument accepts a multimap format:</p>
-<pre class="highlight plaintext"><code>-default_docker_parameters="read-only=true,tmpfs=/tmp,tmpfs=/run"
-</code></pre>
+<p>Increasing executor overhead on an existing cluster, whether it be for custom executors or for Thermos,
+will result in degraded preemption performance until all task which began life with the previous
+executor configuration with less overhead are preempted/restarted.</p>
 
 </div>
 

Modified: aurora/site/publish/documentation/latest/operations/installation/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/operations/installation/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/operations/installation/index.html (original)
+++ aurora/site/publish/documentation/latest/operations/installation/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/operations/installation/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >
@@ -153,8 +157,8 @@ sudo apt-get install -y openjdk-8-jre-he
 
 sudo update-alternatives --set java /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
 
-wget -c https://apache.bintray.com/aurora/ubuntu-trusty/aurora-scheduler_0.12.0_amd64.deb
-sudo dpkg -i aurora-scheduler_0.12.0_amd64.deb
+wget -c https://apache.bintray.com/aurora/ubuntu-trusty/aurora-scheduler_0.15.0_amd64.deb
+sudo dpkg -i aurora-scheduler_0.15.0_amd64.deb
 </code></pre></li>
 </ol>
 
@@ -175,8 +179,8 @@ sudo systemctl start zookeeper-server
 <li><p>Install the Aurora scheduler</p>
 <pre class="highlight plaintext"><code>sudo yum install -y wget
 
-wget -c https://apache.bintray.com/aurora/centos-7/aurora-scheduler-0.12.0-1.el7.centos.aurora.x86_64.rpm
-sudo yum install -y aurora-scheduler-0.12.0-1.el7.centos.aurora.x86_64.rpm
+wget -c https://apache.bintray.com/aurora/centos-7/aurora-scheduler-0.15.0-1.el7.centos.aurora.x86_64.rpm
+sudo yum install -y aurora-scheduler-0.15.0-1.el7.centos.aurora.x86_64.rpm
 </code></pre></li>
 </ol>
 
@@ -217,8 +221,8 @@ Skip down to <a href="#mesos-on-ubuntu-t
 # for the python mesos native bindings.
 sudo apt-get -y install libcurl4-nss-dev
 
-wget -c https://apache.bintray.com/aurora/ubuntu-trusty/aurora-executor_0.12.0_amd64.deb
-sudo dpkg -i aurora-executor_0.12.0_amd64.deb
+wget -c https://apache.bintray.com/aurora/ubuntu-trusty/aurora-executor_0.15.0_amd64.deb
+sudo dpkg -i aurora-executor_0.15.0_amd64.deb
 </code></pre></li>
 </ol>
 
@@ -232,8 +236,8 @@ Skip down to <a href="#mesos-on-centos-7
 <li><p>Install Aurora executor and observer</p>
 <pre class="highlight plaintext"><code>sudo yum install -y python2 wget
 
-wget -c https://apache.bintray.com/aurora/centos-7/aurora-executor-0.12.0-1.el7.centos.aurora.x86_64.rpm
-sudo yum install -y aurora-executor-0.12.0-1.el7.centos.aurora.x86_64.rpm
+wget -c https://apache.bintray.com/aurora/centos-7/aurora-executor-0.15.0-1.el7.centos.aurora.x86_64.rpm
+sudo yum install -y aurora-executor-0.15.0-1.el7.centos.aurora.x86_64.rpm
 </code></pre></li>
 </ol>
 
@@ -280,18 +284,6 @@ Aurora observer start scripts and restar
 <pre class="highlight plaintext"><code>sudo sh -c 'echo "MESOS_ROOT=/tmp/mesos" &gt;&gt; /etc/default/thermos'
 </code></pre>
 
-<p>NB: In Aurora releases up through 0.12.0, you&rsquo;ll also need to edit /etc/init/thermos.conf like so:</p>
-<pre class="highlight diff"><code><span style="color: #999999">diff -C 1 /etc/init/thermos.conf.orig /etc/init/thermos.conf
-</span>*** /etc/init/thermos.conf.orig 2016-03-22 22:34:46.286199718 +0000
-<span style="color: #000000;background-color: #ffdddd">--- /etc/init/thermos.conf  2016-03-22 17:09:49.357689038 +0000
-</span>***************
-*** 24,25 ****
-<span style="color: #000000;background-color: #ffdddd">--- 24,26 ----
-</span>      --port=${OBSERVER_PORT:-1338} \
-<span style="color: #000000;background-color: #ddffdd">+     --mesos-root=${MESOS_ROOT:-/var/lib/mesos} \
-</span>      --log_to_disk=NONE \
-</code></pre>
-
 <h4 id="centos-7">CentOS 7</h4>
 
 <p>Make an edit to add the <code>--mesos-root</code> flag resulting in something like:</p>
@@ -309,15 +301,15 @@ OBSERVER_ARGS=(
 <h3 id="ubuntu-trusty">Ubuntu Trusty</h3>
 <pre class="highlight plaintext"><code>sudo apt-get install -y python2.7 wget
 
-wget -c https://apache.bintray.com/aurora/ubuntu-trusty/aurora-tools_0.12.0_amd64.deb
-sudo dpkg -i aurora-tools_0.12.0_amd64.deb
+wget -c https://apache.bintray.com/aurora/ubuntu-trusty/aurora-tools_0.15.0_amd64.deb
+sudo dpkg -i aurora-tools_0.15.0_amd64.deb
 </code></pre>
 
 <h3 id="centos-7">CentOS 7</h3>
 <pre class="highlight plaintext"><code>sudo yum install -y python2 wget
 
-wget -c https://apache.bintray.com/aurora/centos-7/aurora-tools-0.12.0-1.el7.centos.aurora.x86_64.rpm
-sudo yum install -y aurora-tools-0.12.0-1.el7.centos.aurora.x86_64.rpm
+wget -c https://apache.bintray.com/aurora/centos-7/aurora-tools-0.15.0-1.el7.centos.aurora.x86_64.rpm
+sudo yum install -y aurora-tools-0.15.0-1.el7.centos.aurora.x86_64.rpm
 </code></pre>
 
 <h3 id="mac-os-x">Mac OS X</h3>
@@ -350,12 +342,12 @@ echo "deb http://repos.mesosphere.io/${D
 sudo apt-get -y update
 
 # Use `apt-cache showpkg mesos | grep [version]` to find the exact version.
-sudo apt-get -y install mesos=0.25.0-0.2.70.ubuntu1404
+sudo apt-get -y install mesos=0.28.2-2.0.27.ubuntu1404_amd64
 </code></pre>
 
 <h3 id="mesos-on-centos-7">Mesos on CentOS 7</h3>
 <pre class="highlight plaintext"><code>sudo rpm -Uvh https://repos.mesosphere.io/el/7/noarch/RPMS/mesosphere-el-repo-7-1.noarch.rpm
-sudo yum -y install mesos-0.25.0
+sudo yum -y install mesos-0.28.2
 </code></pre>
 
 <h2 id="troubleshooting">Troubleshooting</h2>

Modified: aurora/site/publish/documentation/latest/operations/monitoring/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/operations/monitoring/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/operations/monitoring/index.html (original)
+++ aurora/site/publish/documentation/latest/operations/monitoring/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/operations/monitoring/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >

Modified: aurora/site/publish/documentation/latest/operations/security/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/operations/security/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/operations/security/index.html (original)
+++ aurora/site/publish/documentation/latest/operations/security/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/operations/security/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >

Modified: aurora/site/publish/documentation/latest/operations/storage/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/operations/storage/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/operations/storage/index.html (original)
+++ aurora/site/publish/documentation/latest/operations/storage/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/operations/storage/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >

Modified: aurora/site/publish/documentation/latest/reference/client-cluster-configuration/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/reference/client-cluster-configuration/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/reference/client-cluster-configuration/index.html (original)
+++ aurora/site/publish/documentation/latest/reference/client-cluster-configuration/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/reference/client-cluster-configuration/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >

Modified: aurora/site/publish/documentation/latest/reference/client-commands/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/reference/client-commands/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/reference/client-commands/index.html (original)
+++ aurora/site/publish/documentation/latest/reference/client-commands/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/reference/client-commands/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >

Modified: aurora/site/publish/documentation/latest/reference/client-hooks/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/reference/client-hooks/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/reference/client-hooks/index.html (original)
+++ aurora/site/publish/documentation/latest/reference/client-hooks/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/reference/client-hooks/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >

Modified: aurora/site/publish/documentation/latest/reference/configuration-best-practices/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/reference/configuration-best-practices/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/reference/configuration-best-practices/index.html (original)
+++ aurora/site/publish/documentation/latest/reference/configuration-best-practices/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/reference/configuration-best-practices/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >

Modified: aurora/site/publish/documentation/latest/reference/configuration-templating/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/reference/configuration-templating/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/reference/configuration-templating/index.html (original)
+++ aurora/site/publish/documentation/latest/reference/configuration-templating/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/reference/configuration-templating/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >

Modified: aurora/site/publish/documentation/latest/reference/configuration-tutorial/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/reference/configuration-tutorial/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/reference/configuration-tutorial/index.html (original)
+++ aurora/site/publish/documentation/latest/reference/configuration-tutorial/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/reference/configuration-tutorial/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >

Modified: aurora/site/publish/documentation/latest/reference/configuration/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/reference/configuration/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/reference/configuration/index.html (original)
+++ aurora/site/publish/documentation/latest/reference/configuration/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/reference/configuration/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >
@@ -260,21 +264,17 @@ schedule.</p>
 
 <h4 id="logger">logger</h4>
 
-<p>The default behavior of Thermos is to store  stderr/stdout logs in files which grow unbounded.
-In the event that you have large log volume, you may want to configure Thermos to automatically rotate logs
-after they grow to a certain size, which can prevent your job from using more than its allocated
-disk space.</p>
-
-<p>A Logger union consists of a destination enum, a mode enum and a rotation policy.
-It&rsquo;s to set where the process logs should be sent using <code>destination</code>. Default
-option is <code>file</code>. Its also possible to specify <code>console</code> to get logs output
-to stdout/stderr, <code>none</code> to suppress any logs output or <code>both</code> to send logs to files and
-console output. In case of using <code>none</code> or <code>console</code> rotation attributes are ignored.
-Rotation policies only apply to loggers whose mode is <code>rotate</code>. The acceptable values
-for the LoggerMode enum are <code>standard</code> and <code>rotate</code>. The rotation policy applies to both
-stderr and stdout.</p>
+<p>The default behavior of Thermos is to store stderr/stdout logs in files which grow unbounded.
+In the event that you have large log volume, you may want to configure Thermos to automatically
+rotate logs after they grow to a certain size, which can prevent your job from using more than its
+allocated disk space.</p>
+
+<p>Logger objects specify a <code>destination</code> for Process logs which is, by default, <code>file</code> - a pair of
+<code>stdout</code> and <code>stderr</code> files. Its also possible to specify <code>console</code> to get logs output to
+the Process stdout and stderr streams, <code>none</code> to suppress any logs output or <code>both</code> to send logs to
+files and console streams.</p>
 
-<p>By default, all processes use the <code>standard</code> LoggerMode.</p>
+<p>The default Logger <code>mode</code> is <code>standard</code> which lets the stdout and stderr streams grow without bound.</p>
 
 <table><thead>
 <tr>
@@ -296,12 +296,13 @@ stderr and stdout.</p>
 <tr>
 <td><strong>rotate</strong></td>
 <td style="text-align: center">RotatePolicy</td>
-<td>An optional rotation policy.</td>
+<td>An optional rotation policy. (Default: <code>Empty</code>)</td>
 </tr>
 </tbody></table>
 
-<p>A RotatePolicy describes log rotation behavior for when <code>mode</code> is set to <code>rotate</code>. It is ignored
-otherwise.</p>
+<p>A RotatePolicy describes log rotation behavior for when <code>mode</code> is set to <code>rotate</code> and it is ignored
+otherwise. If <code>rotate</code> is <code>Empty</code> or <code>RotatePolicy()</code> when the <code>mode</code> is set to <code>rotate</code> the
+defaults below are used.</p>
 
 <table><thead>
 <tr>
@@ -568,6 +569,9 @@ resources are allocated.</p>
   deprecated in favor of setting its value directly to the appropriate <code>Docker</code> or <code>Mesos</code>
   container type</em></p>
 
+<p><em>Note: Specifying preemption behavior of tasks through <code>production</code> flag is deprecated in favor of
+  electing appropriate task tier via <code>tier</code> attribute.</em></p>
+
 <table><thead>
 <tr>
 <th>name</th>
@@ -648,7 +652,7 @@ resources are allocated.</p>
 <tr>
 <td><code>production</code></td>
 <td style="text-align: center">Boolean</td>
-<td>Whether or not this is a production task that may <a href="../../features/multitenancy/#preemption">preempt</a> other tasks (Default: False). Production job role must have the appropriate <a href="../../features/multitenancy/#preemption">quota</a>.</td>
+<td>(Deprecated) Whether or not this is a production task that may <a href="../../features/multitenancy/#preemption">preempt</a> other tasks (Default: False). Production job role must have the appropriate <a href="../../features/multitenancy/#preemption">quota</a>.</td>
 </tr>
 <tr>
 <td><code>health_check_config</code></td>
@@ -668,7 +672,7 @@ resources are allocated.</p>
 <tr>
 <td><code>tier</code></td>
 <td style="text-align: center">String</td>
-<td>Task tier type. The default scheduler tier configuration allows for 3 tiers: <code>revocable</code>, <code>preemptible</code>, and <code>preferred</code>. The <code>revocable</code> tier requires the task to run with Mesos revocable resources. Setting the task&rsquo;s tier to <code>preemptible</code> allows for the possibility of that task being preempted by other tasks when cluster is running low on resources. The <code>preferred</code> tier prevents the task from using revocable resources and from being preempted. Since it is possible that a cluster is configured with a custom tier configuration, users should consult their cluster administrator to be informed of the tiers supported by the cluster. Attempts to schedule jobs with an unsupported tier will be rejected by the scheduler.</td>
+<td>Task tier type. The default scheduler tier configuration allows for 3 tiers: <code>revocable</code>, <code>preemptible</code>, and <code>preferred</code>. If a tier is not elected, Aurora assigns the task to a tier based on its choice of <code>production</code> (that is <code>preferred</code> for production and <code>preemptible</code> for non-production jobs). See the section on <a href="../../features/multitenancy/#configuration-tiers">Configuration Tiers</a> for more information.</td>
 </tr>
 <tr>
 <td><code>announce</code></td>
@@ -899,11 +903,6 @@ guarantees should they be needed.</p>
 
 <h3 id="container-objects">Container Objects</h3>
 
-<p><em>Note: Both Docker and Mesos unified-container support are currently EXPERIMENTAL.</em>
-<em>Note: In order to correctly execute processes inside a job, the Docker container must have python 2.7 installed.</em></p>
-
-<p><em>Note: For private docker registry, mesos mandates the docker credential file to be named as <code>.dockercfg</code>, even though docker may create a credential file with a different name on various platforms. Also, the <code>.dockercfg</code> file needs to be copied into the sandbox using the <code>-thermos_executor_resources</code> flag, specified while starting Aurora.</em></p>
-
 <p>Describes the container the job&rsquo;s processes will run inside. If not using Docker or the Mesos
 unified-container, the container can be omitted from your job config.</p>
 
@@ -915,18 +914,18 @@ unified-container, the container can be
 </tr>
 </thead><tbody>
 <tr>
-<td><code>docker</code></td>
-<td style="text-align: center">Docker</td>
-<td>A docker container to use.</td>
-</tr>
-<tr>
 <td><code>mesos</code></td>
 <td style="text-align: center">Mesos</td>
-<td>A mesos container to use.</td>
+<td>A native Mesos container to use.</td>
+</tr>
+<tr>
+<td><code>docker</code></td>
+<td style="text-align: center">Docker</td>
+<td>A Docker container to use (via Docker engine)</td>
 </tr>
 </tbody></table>
 
-<h3 id="docker-object">Docker Object</h3>
+<h3 id="mesos-object">Mesos Object</h3>
 
 <table><thead>
 <tr>
@@ -937,20 +936,14 @@ unified-container, the container can be
 </thead><tbody>
 <tr>
 <td><code>image</code></td>
-<td style="text-align: center">String</td>
-<td>The name of the docker image to execute.  If the image does not exist locally it will be pulled with <code>docker pull</code>.</td>
-</tr>
-<tr>
-<td><code>parameters</code></td>
-<td style="text-align: center">List(Parameter)</td>
-<td>Additional parameters to pass to the docker containerizer.</td>
+<td style="text-align: center">Choice(AppcImage, DockerImage)</td>
+<td>An optional filesystem image to use within this container.</td>
 </tr>
 </tbody></table>
 
-<h3 id="docker-parameter-object">Docker Parameter Object</h3>
+<h3 id="appcimage">AppcImage</h3>
 
-<p>Docker CLI parameters. This needs to be enabled by the scheduler <code>allow_docker_parameters</code> option.
-See <a href="https://docs.docker.com/reference/commandline/run/">Docker Command Line Reference</a> for valid parameters.</p>
+<p>Describes an AppC filesystem image.</p>
 
 <table><thead>
 <tr>
@@ -962,16 +955,18 @@ See <a href="https://docs.docker.com/ref
 <tr>
 <td><code>name</code></td>
 <td style="text-align: center">String</td>
-<td>The name of the docker parameter. E.g. volume</td>
+<td>The name of the appc image.</td>
 </tr>
 <tr>
-<td><code>value</code></td>
+<td><code>image_id</code></td>
 <td style="text-align: center">String</td>
-<td>The value of the parameter. E.g. /usr/local/bin:/usr/bin:rw</td>
+<td>The <a href="https://github.com/appc/spec/blob/master/spec/aci.md#image-id">image id</a> of the appc image.</td>
 </tr>
 </tbody></table>
 
-<h3 id="mesos-object">Mesos Object</h3>
+<h3 id="dockerimage">DockerImage</h3>
+
+<p>Describes a Docker filesystem image.</p>
 
 <table><thead>
 <tr>
@@ -981,17 +976,21 @@ See <a href="https://docs.docker.com/ref
 </tr>
 </thead><tbody>
 <tr>
-<td><code>image</code></td>
-<td style="text-align: center">Choice(AppcImage, DockerImage)</td>
-<td>An optional filesystem image to use within this container.</td>
+<td><code>name</code></td>
+<td style="text-align: center">String</td>
+<td>The name of the docker image.</td>
+</tr>
+<tr>
+<td><code>tag</code></td>
+<td style="text-align: center">String</td>
+<td>The tag that identifies the docker image.</td>
 </tr>
 </tbody></table>
 
-<h3 id="appcimage">AppcImage</h3>
-
-<p><em>Note: In order to correctly execute processes inside a job, the filesystem image must include python 2.7.</em></p>
+<h3 id="docker-object">Docker Object</h3>
 
-<p>Describes an AppC filesystem image.</p>
+<p><em>Note: In order to correctly execute processes inside a job, the Docker container must have Python 2.7 installed.</em>
+<em>Note: For private docker registry, mesos mandates the docker credential file to be named as <code>.dockercfg</code>, even though docker may create a credential file with a different name on various platforms. Also, the <code>.dockercfg</code> file needs to be copied into the sandbox using the <code>-thermos_executor_resources</code> flag, specified while starting Aurora.</em></p>
 
 <table><thead>
 <tr>
@@ -1001,22 +1000,21 @@ See <a href="https://docs.docker.com/ref
 </tr>
 </thead><tbody>
 <tr>
-<td><code>name</code></td>
+<td><code>image</code></td>
 <td style="text-align: center">String</td>
-<td>The name of the appc image.</td>
+<td>The name of the docker image to execute.  If the image does not exist locally it will be pulled with <code>docker pull</code>.</td>
 </tr>
 <tr>
-<td><code>image_id</code></td>
-<td style="text-align: center">String</td>
-<td>The <a href="https://github.com/appc/spec/blob/master/spec/aci.md#image-id">image id</a> of the appc image.</td>
+<td><code>parameters</code></td>
+<td style="text-align: center">List(Parameter)</td>
+<td>Additional parameters to pass to the Docker engine.</td>
 </tr>
 </tbody></table>
 
-<h3 id="dockerimage">DockerImage</h3>
-
-<p><em>Note: In order to correctly execute processes inside a job, the filesystem image must include python 2.7.</em></p>
+<h3 id="docker-parameter-object">Docker Parameter Object</h3>
 
-<p>Describes a Docker filesystem image.</p>
+<p>Docker CLI parameters. This needs to be enabled by the scheduler <code>-allow_docker_parameters</code> option.
+See <a href="https://docs.docker.com/reference/commandline/run/">Docker Command Line Reference</a> for valid parameters.</p>
 
 <table><thead>
 <tr>
@@ -1028,12 +1026,12 @@ See <a href="https://docs.docker.com/ref
 <tr>
 <td><code>name</code></td>
 <td style="text-align: center">String</td>
-<td>The name of the docker image.</td>
+<td>The name of the docker parameter. E.g. volume</td>
 </tr>
 <tr>
-<td><code>tag</code></td>
+<td><code>value</code></td>
 <td style="text-align: center">String</td>
-<td>The tag that identifies the docker image.</td>
+<td>The value of the parameter. E.g. /usr/local/bin:/usr/bin:rw</td>
 </tr>
 </tbody></table>
 

Modified: aurora/site/publish/documentation/latest/reference/scheduler-configuration/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/reference/scheduler-configuration/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/reference/scheduler-configuration/index.html (original)
+++ aurora/site/publish/documentation/latest/reference/scheduler-configuration/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/reference/scheduler-configuration/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >
@@ -110,6 +114,8 @@ Required flags:
     Max number of idle connections to the database via MyBatis
 -framework_authentication_file
     Properties file which contains framework credentials to authenticate with Mesosmaster. Must contain the properties 'aurora_authentication_principal' and 'aurora_authentication_secret'.
+-ip
+    The ip address to listen. If not set, the scheduler will listen on all interfaces.
 -mesos_master_address [not null]
     Address for the mesos master, can be a socket address or zookeeper path.
 -mesos_role
@@ -122,12 +128,16 @@ Required flags:
     Path to the thermos executor entry point.
 -tier_config [file must be readable]
     Configuration file defining supported task tiers, task traits and behaviors.
+-webhook_config [file must exist, file must be readable]
+    Path to webhook configuration file.
 -zk_endpoints [must have at least 1 item]
     Endpoint specification for the ZooKeeper servers.
 
 Optional flags:
 -allow_docker_parameters (default false)
     Allow to pass docker container parameters in the job.
+-allow_gpu_resource (default false)
+    Allow jobs to request Mesos GPU resource.
 -allowed_container_types (default [MESOS])
     Container types that are allowed to be used by jobs.
 -async_slot_stat_update_interval (default (1, mins))
@@ -164,10 +174,16 @@ Optional flags:
     List of domains for which CORS support should be enabled.
 -enable_h2_console (default false)
     Enable H2 DB management console.
+-enable_mesos_fetcher (default false)
+    Allow jobs to pass URIs to the Mesos Fetcher. Note that enabling this feature could pose a privilege escalation threat.
 -enable_preemptor (default true)
     Enable the preemptor and preemption
+-enable_revocable_cpus (default true)
+    Treat CPUs as a revocable resource.
+-enable_revocable_ram (default false)
+    Treat RAM as a revocable resource.
 -executor_user (default root)
-    User to start the executor. Defaults to "root". Set this to an unprivileged user if the mesos master was started with "--no-root_submissions". If set to anything other than "root", the executor will ignore the "role" setting for jobs since it can't use setuid() anymore. This means that all your jobs will run under the specified user and the user has to exist on the mesos slaves.
+    User to start the executor. Defaults to "root". Set this to an unprivileged user if the mesos master was started with "--no-root_submissions". If set to anything other than "root", the executor will ignore the "role" setting for jobs since it can't use setuid() anymore. This means that all your jobs will run under the specified user and the user has to exist on the Mesos agents.
 -first_schedule_delay (default (1, ms))
     Initial amount of time to wait before first attempting to schedule a PENDING task.
 -flapping_task_threshold (default (5, mins))
@@ -251,7 +267,7 @@ Optional flags:
 -offer_hold_jitter_window (default (1, mins))
     Maximum amount of random jitter to add to the offer hold time window.
 -offer_reservation_duration (default (3, mins))
-    Time to reserve a slave's offers while trying to satisfy a task preempting another.
+    Time to reserve a agent's offers while trying to satisfy a task preempting another.
 -populate_discovery_info (default false)
     If true, Aurora populates DiscoveryInfo field of Mesos TaskInfo.
 -preemption_delay (default (3, mins))
@@ -262,6 +278,10 @@ Optional flags:
     Time interval between pending task preemption slot searches.
 -receive_revocable_resources (default false)
     Allows receiving revocable resource offers from Mesos.
+-reconciliation_explicit_batch_interval (default (5, secs))
+    Interval between explicit batch reconciliation requests.
+-reconciliation_explicit_batch_size (default 1000) [must be &gt; 0]
+    Number of tasks in a single batch request sent to Mesos for explicit reconciliation.
 -reconciliation_explicit_interval (default (60, mins))
     Interval on which scheduler will ask Mesos for status updates of all non-terminal tasks known to scheduler.
 -reconciliation_implicit_interval (default (60, mins))
@@ -274,7 +294,7 @@ Optional flags:
     If false, Docker tasks may run without an executor (EXPERIMENTAL)
 -shiro_ini_path
     Path to shiro.ini for authentication and authorization configuration.
--shiro_realm_modules (default [org.apache.aurora.scheduler.app.MoreModules$1@13c9d689])
+-shiro_realm_modules (default [org.apache.aurora.scheduler.app.MoreModules$1@158a8276])
     Guice modules for configuring Shiro Realms.
 -sla_non_prod_metrics (default [])
     Metric categories collected for non production tasks.
@@ -306,8 +326,6 @@ Optional flags:
     Whether to use the experimental database-backed task store.
 -viz_job_url_prefix (default )
     URL prefix for job container stats.
--webhook_config [file must be readable]
-    File to configure a HTTP webhook to receive task state change events.
 -zk_chroot_path
     chroot path to use for the ZooKeeper connections
 -zk_digest_credentials
@@ -316,8 +334,8 @@ Optional flags:
     Launches an embedded zookeeper server for local testing causing -zk_endpoints to be ignored if specified.
 -zk_session_timeout (default (4, secs))
     The ZooKeeper session timeout.
--zk_use_curator (default false)
-    Uses Apache Curator as the zookeeper client; otherwise a copy of Twitter commons/zookeeper (the legacy library) is used.
+-zk_use_curator (default true)
+    DEPRECATED: Uses Apache Curator as the zookeeper client; otherwise a copy of Twitter commons/zookeeper (the legacy library) is used.
 -------------------------------------------------------------------------
 </code></pre>
 

Modified: aurora/site/publish/documentation/latest/reference/scheduler-endpoints/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/reference/scheduler-endpoints/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/reference/scheduler-endpoints/index.html (original)
+++ aurora/site/publish/documentation/latest/reference/scheduler-endpoints/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/reference/scheduler-endpoints/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >

Modified: aurora/site/publish/documentation/latest/reference/task-lifecycle/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/reference/task-lifecycle/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/reference/task-lifecycle/index.html (original)
+++ aurora/site/publish/documentation/latest/reference/task-lifecycle/index.html Wed Sep 28 18:23:53 2016
@@ -41,10 +41,14 @@
 <h5 class="page-header text-uppercase">Documentation
 <select onChange="window.location.href='/documentation/' + this.value + '/reference/task-lifecycle/'"
         value="latest">
+  <option value="0.16.0"
+    >
+    0.16.0
+      (latest)
+  </option>
   <option value="0.15.0"
     >
     0.15.0
-      (latest)
   </option>
   <option value="0.14.0"
     >

Modified: aurora/site/publish/downloads/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/downloads/index.html?rev=1762695&r1=1762694&r2=1762695&view=diff
==============================================================================
--- aurora/site/publish/downloads/index.html (original)
+++ aurora/site/publish/downloads/index.html Wed Sep 28 18:23:53 2016
@@ -60,6 +60,12 @@
 
 <h2 id="source-distributions">Source distributions</h2>
 
+<h4 id="0-16-0"><a href="http://www.apache.org/dyn/closer.cgi?path=/aurora/0.16.0/apache-aurora-0.16.0.tar.gz">0.16.0</a></h4>
+
+<p><a href="https://www.apache.org/dist/aurora/0.16.0/">signatures</a>
+| <a href="https://git-wip-us.apache.org/repos/asf?p=aurora.git;a=log;h=refs/tags/rel/0.16.0">commit log</a>
+| <a href="/blog/aurora-0-16-0-released/">release notes</a></p>
+
 <h4 id="0-15-0"><a href="http://www.apache.org/dyn/closer.cgi?path=/aurora/0.15.0/apache-aurora-0.15.0.tar.gz">0.15.0</a></h4>
 
 <p><a href="https://www.apache.org/dist/aurora/0.15.0/">signatures</a>



Mime
View raw message