Modified: aurora/site/publish/documentation/0.9.0/configuration-tutorial/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/configuration-tutorial/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/configuration-tutorial/index.html (original) +++ aurora/site/publish/documentation/0.9.0/configuration-tutorial/index.html Sun Dec 13 00:49:43 2015 @@ -47,7 +47,7 @@ and best practices. When writing a confi arguments as <code>aurora job create</code> or <code>aurora job update</code>. It first ensures the configuration parses, then outputs it in human-readable form.</p> -<p>You should read this after going through the general <a href="/documentation/0.9.0//">Aurora Tutorial</a>.</p> +<p>You should read this after going through the general <a href="/documentation/0.9.0/tutorial/">Aurora Tutorial</a>.</p> <ul> <li><a href="#aurora-configuration-tutorial">Aurora Configuration Tutorial</a> @@ -151,12 +151,12 @@ configuration specification and reuse. P via {{}} surrounded templates.</p> <p>When writing your <code>.aurora</code> file, you may use any Pystachio datatypes, as -well as any objects shown in the <a href="/documentation/0.9.0//"><em>Aurora+Thermos Configuration +well as any objects shown in the <a href="/documentation/0.9.0/configuration-reference/"><em>Aurora+Thermos Configuration Reference</em></a>, without <code>import</code> statements - the Aurora config loader injects them automatically. Other than that, an <code>.aurora</code> file works like any other Python script.</p> -<p><a href="/documentation/0.9.0//"><em>Aurora+Thermos Configuration Reference</em></a> +<p><a href="/documentation/0.9.0/configuration-reference/"><em>Aurora+Thermos Configuration Reference</em></a> has a full reference of all Aurora/Thermos defined Pystachio objects.</p> <h3 id="use-bottom-to-top-object-ordering">Use Bottom-To-Top Object Ordering</h3> @@ -715,7 +715,7 @@ task is unhealthy.</li> constraints. Most users will not need to specify constraints, as the scheduler automatically inserts reasonable defaults. Please do not set this field unless you are sure of what you are doing. See the -section in the Aurora + Thermos Reference manual on <a href="/documentation/0.9.0//">Specifying +section in the Aurora + Thermos Reference manual on <a href="/documentation/0.9.0/configuration-reference/">Specifying Scheduling Constraints</a> for more information.</li> </ul> @@ -733,7 +733,7 @@ following runs first <code>job1</code>, <code>Process</code>, and other classes are defined by a templating library called <em>Pystachio</em>, a powerful tool for configuration specification and reuse.</p> -<p><a href="/documentation/0.9.0//">Aurora+Thermos Configuration Reference</a> +<p><a href="/documentation/0.9.0/configuration-reference/">Aurora+Thermos Configuration Reference</a> has a full reference of all Aurora/Thermos defined Pystachio objects.</p> <p>When writing your <code>.aurora</code> file, you may use any Pystachio datatypes, as
Modified: aurora/site/publish/documentation/0.9.0/cron-jobs/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/cron-jobs/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/cron-jobs/index.html (original) +++ aurora/site/publish/documentation/0.9.0/cron-jobs/index.html Sun Dec 13 00:49:43 2015 @@ -74,11 +74,11 @@ <p>A job is identified as a cron job by the presence of a <code>cron_schedule</code> attribute containing a cron-style schedule in the -<a href="/documentation/0.9.0//"><code>Job</code></a> object. Examples of cron schedules +<a href="/documentation/0.9.0/configuration-reference/#job-objects"><code>Job</code></a> object. Examples of cron schedules include “every 5 minutes” (<code>*/5 * * * *</code>), “Fridays at 17:00” (<code>* 17 * * FRI</code>), and “the 1st and 15th day of the month at 03:00” (<code>0 3 1,15 *</code>).</p> -<p>Example (available in the <a href="/documentation/0.9.0//">Vagrant environment</a>):</p> +<p>Example (available in the <a href="/documentation/0.9.0/vagrant/">Vagrant environment</a>):</p> <pre class="highlight plaintext"><code>$ cat /vagrant/examples/job/cron_hello_world.aurora # cron_hello_world.aurora # A cron job that runs every 5 minutes. @@ -119,7 +119,7 @@ grow faster than they can process it.</p <p>Unlike with services, which aurora will always re-execute regardless of exit status, instances of cron jobs retry according to the <code>max_task_failures</code> attribute of the -<a href="/documentation/0.9.0//">Task</a> object. To get “run-until-success” semantics, +<a href="/documentation/0.9.0/configuration-reference/#task-objects">Task</a> object. To get “run-until-success” semantics, set <code>max_task_failures</code> to <code>-1</code>.</p> <h2 id="interacting-with-cron-jobs-via-the-aurora-cli">Interacting with cron jobs via the Aurora CLI</h2> Modified: aurora/site/publish/documentation/0.9.0/deploying-aurora-scheduler/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/deploying-aurora-scheduler/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/deploying-aurora-scheduler/index.html (original) +++ aurora/site/publish/documentation/0.9.0/deploying-aurora-scheduler/index.html Sun Dec 13 00:49:43 2015 @@ -194,7 +194,7 @@ should be set to <code>2</code>, and in <p><em>Incorrectly setting this flag will cause data corruption to occur!</em></p> -<p>See <a href="/documentation/0.9.0//">this document</a> for more replicated +<p>See <a href="/documentation/0.9.0/storage-config/#scheduler-storage-configuration-flags">this document</a> for more replicated log and storage configuration options.</p> <h2 id="initializing-the-replicated-log">Initializing the Replicated Log</h2> @@ -210,7 +210,7 @@ Failing to do this will result the follo <h3 id="storage-performance-considerations">Storage Performance Considerations</h3> -<p>See <a href="/documentation/0.9.0//">this document</a> for scheduler storage performance considerations.</p> +<p>See <a href="/documentation/0.9.0/scheduler-storage/">this document</a> for scheduler storage performance considerations.</p> <h3 id="network-considerations">Network considerations</h3> @@ -270,13 +270,13 @@ restarted.</p> <h2 id="security-considerations">Security Considerations</h2> -<p>See <a href="/documentation/0.9.0//">security.md</a>.</p> +<p>See <a href="/documentation/0.9.0/security/">security.md</a>.</p> <h3 id="maintaining-an-aurora-installation">Maintaining an Aurora Installation</h3> <h3 id="monitoring">Monitoring</h3> -<p>Please see our dedicated <a href="/documentation/0.9.0//">monitoring guide</a> for in-depth discussion on monitoring.</p> +<p>Please see our dedicated <a href="/documentation/0.9.0/monitoring/">monitoring guide</a> for in-depth discussion on monitoring.</p> <h3 id="running-stateful-services">Running stateful services</h3> @@ -289,7 +289,7 @@ like databases, or services that otherwi static attributes (not to be confused with <code>--resources</code>, which are dynamic and accounted).</p> <p>Aurora makes these attributes available for matching with scheduling -<a href="/documentation/0.9.0//">constraints</a>. Most of these +<a href="/documentation/0.9.0/configuration-reference/#specifying-scheduling-constraints">constraints</a>. Most of these constraints are arbitrary and available for custom use. There is one exception, though: the <code>dedicated</code> attribute. Aurora treats this specially, and only allows matching jobs to run on these machines, and will only schedule matching jobs on these machines.</p> @@ -372,7 +372,7 @@ the master in ZooKeeper, make sure comma <h4 id="symptoms">Symptoms</h4> -<p>The scheduler is registered, and <a href="/documentation/0.9.0//">receiving offers</a>, +<p>The scheduler is registered, and <a href="/documentation/0.9.0/monitoring/#scheduler_resource_offers">receiving offers</a>, but tasks are perpetually shown as <code>PENDING - Constraint not satisfied: host</code>.</p> <h4 id="solution">Solution</h4> Modified: aurora/site/publish/documentation/0.9.0/developing-aurora-client/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/developing-aurora-client/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/developing-aurora-client/index.html (original) +++ aurora/site/publish/documentation/0.9.0/developing-aurora-client/index.html Sun Dec 13 00:49:43 2015 @@ -48,9 +48,9 @@ <p>The client uses a configuration file that specifies available clusters. More information about the contents of this file can be found in the -<a href="/documentation/0.9.0//">Client Cluster Configuration</a> documentation. Information about +<a href="/documentation/0.9.0/client-cluster-configuration/">Client Cluster Configuration</a> documentation. Information about how the client locates this file can be found in the -<a href="/documentation/0.9.0//">Client Commands</a> documentation.</p> +<a href="/documentation/0.9.0/client-commands/#cluster-configuration">Client Commands</a> documentation.</p> <h1 id="building-and-testing-the-client">Building and Testing the Client</h1> @@ -128,7 +128,7 @@ is the directory where our example clust <h1 id="making-thrift-schema-changes">Making thrift schema changes</h1> -<p>See <a href="/documentation/0.9.0//">this document</a> for any thrift related changes.</p> +<p>See <a href="/documentation/0.9.0/thrift-deprecation/">this document</a> for any thrift related changes.</p> </div> Modified: aurora/site/publish/documentation/0.9.0/developing-aurora-scheduler/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/developing-aurora-scheduler/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/developing-aurora-scheduler/index.html (original) +++ aurora/site/publish/documentation/0.9.0/developing-aurora-scheduler/index.html Sun Dec 13 00:49:43 2015 @@ -147,7 +147,7 @@ repository root and commit the changed f <h1 id="making-thrift-schema-changes">Making thrift schema changes</h1> -<p>See <a href="/documentation/0.9.0//">this document</a> for any thrift related changes.</p> +<p>See <a href="/documentation/0.9.0/thrift-deprecation/">this document</a> for any thrift related changes.</p> </div> Modified: aurora/site/publish/documentation/0.9.0/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/index.html (original) +++ aurora/site/publish/documentation/0.9.0/index.html Sun Dec 13 00:49:43 2015 @@ -54,41 +54,41 @@ <h2 id="users">Users</h2> <ul> -<li><a href="/documentation/0.9.0//">Install Aurora on virtual machines on your private machine</a></li> -<li><a href="/documentation/0.9.0//">Hello World Tutorial</a></li> -<li><a href="/documentation/0.9.0//">User Guide</a></li> -<li><a href="/documentation/0.9.0//">Configuration Tutorial</a></li> -<li><a href="/documentation/0.9.0//">Aurora + Thermos Reference</a></li> -<li><a href="/documentation/0.9.0//">Command Line Client</a></li> -<li><a href="/documentation/0.9.0//">Cron Jobs</a></li> +<li><a href="/documentation/0.9.0/vagrant/">Install Aurora on virtual machines on your private machine</a></li> +<li><a href="/documentation/0.9.0/tutorial/">Hello World Tutorial</a></li> +<li><a href="/documentation/0.9.0/user-guide/">User Guide</a></li> +<li><a href="/documentation/0.9.0/configuration-tutorial/">Configuration Tutorial</a></li> +<li><a href="/documentation/0.9.0/configuration-reference/">Aurora + Thermos Reference</a></li> +<li><a href="/documentation/0.9.0/client-commands/">Command Line Client</a></li> +<li><a href="/documentation/0.9.0/cron-jobs/">Cron Jobs</a></li> </ul> <h2 id="operators">Operators</h2> <ul> -<li><a href="/documentation/0.9.0//">Deploy Aurora</a></li> -<li><a href="/documentation/0.9.0//">Monitoring</a></li> -<li><a href="/documentation/0.9.0//">Hooks for Aurora Client API</a></li> -<li><a href="/documentation/0.9.0//">Scheduler Storage</a></li> -<li><a href="/documentation/0.9.0//">Scheduler Storage and Maintenance</a></li> -<li><a href="/documentation/0.9.0//">SLA Measurement</a></li> -<li><a href="/documentation/0.9.0//">Resource Isolation and Sizing</a></li> -<li><a href="/documentation/0.9.0//">Generating test resources</a></li> +<li><a href="/documentation/0.9.0/deploying-aurora-scheduler/">Deploy Aurora</a></li> +<li><a href="/documentation/0.9.0/monitoring/">Monitoring</a></li> +<li><a href="/documentation/0.9.0/hooks/">Hooks for Aurora Client API</a></li> +<li><a href="/documentation/0.9.0/storage/">Scheduler Storage</a></li> +<li><a href="/documentation/0.9.0/storage-config/">Scheduler Storage and Maintenance</a></li> +<li><a href="/documentation/0.9.0/sla/">SLA Measurement</a></li> +<li><a href="/documentation/0.9.0/resource-isolation/">Resource Isolation and Sizing</a></li> +<li><a href="/documentation/0.9.0/test-resource-generation/">Generating test resources</a></li> </ul> <h2 id="developers">Developers</h2> <ul> <li><a href="contributing/">Contributing to the project</a></li> -<li><a href="/documentation/0.9.0//">Developing the Aurora Scheduler</a></li> -<li><a href="/documentation/0.9.0//">Developing the Aurora Client</a></li> -<li><a href="/documentation/0.9.0//">Committers Guide</a></li> +<li><a href="/documentation/0.9.0/developing-aurora-scheduler/">Developing the Aurora Scheduler</a></li> +<li><a href="/documentation/0.9.0/developing-aurora-client/">Developing the Aurora Client</a></li> +<li><a href="/documentation/0.9.0/committers/">Committers Guide</a></li> </ul> <h2 id="additional-resources">Additional Resources</h2> <ul> -<li><a href="/documentation/0.9.0//">Presentation videos and slides</a></li> +<li><a href="/documentation/0.9.0/presentations/">Presentation videos and slides</a></li> </ul> </div> Modified: aurora/site/publish/documentation/0.9.0/storage-config/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/storage-config/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/storage-config/index.html (original) +++ aurora/site/publish/documentation/0.9.0/storage-config/index.html Sun Dec 13 00:49:43 2015 @@ -71,7 +71,7 @@ <p>This document summarizes Aurora storage configuration and maintenance details and is intended for use by anyone deploying and/or maintaining Aurora.</p> -<p>For a high level overview of the Aurora storage architecture refer to <a href="/documentation/0.9.0//">this document</a>.</p> +<p>For a high level overview of the Aurora storage architecture refer to <a href="/documentation/0.9.0/storage/">this document</a>.</p> <h2 id="scheduler-storage-configuration-flags">Scheduler storage configuration flags</h2> @@ -83,7 +83,7 @@ or require attention before deploying in <h4 id="nativelogquorum_size">-native<em>log</em>quorum_size</h4> <p>Defines the Mesos replicated log quorum size. See -<a href="/documentation/0.9.0//">the replicated log configuration document</a> +<a href="/documentation/0.9.0/deploying-aurora-scheduler/#replicated-log-configuration">the replicated log configuration document</a> on how to choose the right value.</p> <h4 id="nativelogfile_path">-native<em>log</em>file_path</h4> Modified: aurora/site/publish/documentation/0.9.0/storage/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/storage/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/storage/index.html (original) +++ aurora/site/publish/documentation/0.9.0/storage/index.html Sun Dec 13 00:49:43 2015 @@ -82,7 +82,7 @@ is <a href="https://github.com/apache/th This helps establishing periodic recovery checkpoints and speeds up volatile storage recovery on restart.</li> <li>Backup manager: as a precaution, snapshots are periodically written out into backup files. -This solves a <a href="/documentation/0.9.0//">disaster recovery problem</a> +This solves a <a href="/documentation/0.9.0/storage-config/#recovering-from-a-scheduler-backup">disaster recovery problem</a> in case of a complete loss or corruption of Mesos log files.</li> </ul> Modified: aurora/site/publish/documentation/0.9.0/test-resource-generation/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/test-resource-generation/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/test-resource-generation/index.html (original) +++ aurora/site/publish/documentation/0.9.0/test-resource-generation/index.html Sun Dec 13 00:49:43 2015 @@ -62,7 +62,7 @@ that would undermine the goal of ensurin <p>The most common reason to add a new checkpoint file would be to provide coverage for new thermos features that alter the data format. This is accomplished by writing and running a -<a href="/documentation/0.9.0//">job configuration</a> that exercises the feature, and +<a href="/documentation/0.9.0/configuration-reference/">job configuration</a> that exercises the feature, and copying the checkpoint file from the sandbox directory, by default this is <code>/var/run/thermos/checkpoints/<aurora task id></code>.</p> Modified: aurora/site/publish/documentation/0.9.0/thrift-deprecation/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/thrift-deprecation/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/thrift-deprecation/index.html (original) +++ aurora/site/publish/documentation/0.9.0/thrift-deprecation/index.html Sun Dec 13 00:49:43 2015 @@ -92,7 +92,7 @@ See <a href="https://github.com/apache/a <p>It’s always advisable to test your changes in the local vagrant environment to build more confidence that you change is backwards compatible. It’s easy to simulate different -client/scheduler versions by playing with <code>aurorabuild</code> command. See <a href="/documentation/0.9.0//">this document</a> +client/scheduler versions by playing with <code>aurorabuild</code> command. See <a href="/documentation/0.9.0/vagrant/">this document</a> for more.</p> </div> Modified: aurora/site/publish/documentation/0.9.0/tutorial/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/tutorial/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/tutorial/index.html (original) +++ aurora/site/publish/documentation/0.9.0/tutorial/index.html Sun Dec 13 00:49:43 2015 @@ -74,7 +74,7 @@ getting up to speed on the system.</p> <h2 id="setup-install-aurora">Setup: Install Aurora</h2> <p>You use the Aurora client and web UI to interact with Aurora jobs. To -install it locally, see <a href="/documentation/0.9.0//">vagrant.md</a>. The remainder of this +install it locally, see <a href="/documentation/0.9.0/vagrant/">vagrant.md</a>. The remainder of this Tutorial assumes you are running Aurora using Vagrant. Unless otherwise stated, all commands are to be run from the root of the aurora repository clone.</p> @@ -146,8 +146,8 @@ code in the file <code>hello_world.auror <span style="background-color: #f8f8f8">]</span> </code></pre> -<p>For more about Aurora configuration files, see the <a href="/documentation/0.9.0//">Configuration -Tutorial</a> and the <a href="/documentation/0.9.0//">Aurora + Thermos +<p>For more about Aurora configuration files, see the <a href="/documentation/0.9.0/configuration-tutorial/">Configuration +Tutorial</a> and the <a href="/documentation/0.9.0/configuration-reference/">Aurora + Thermos Reference</a> (preferably after finishing this tutorial).</p> @@ -298,13 +298,13 @@ vagrant@precise64:~$ <p>Now that you’ve finished this Tutorial, you should read or do the following:</p> <ul> -<li><a href="/documentation/0.9.0//">The Aurora Configuration Tutorial</a>, which provides more examples +<li><a href="/documentation/0.9.0/configuration-tutorial/">The Aurora Configuration Tutorial</a>, which provides more examples and best practices for writing Aurora configurations. You should also look at -the <a href="/documentation/0.9.0//">Aurora + Thermos Configuration Reference</a>.</li> -<li>The <a href="/documentation/0.9.0//">Aurora User Guide</a> provides an overview of how Aurora, Mesos, and +the <a href="/documentation/0.9.0/configuration-reference/">Aurora + Thermos Configuration Reference</a>.</li> +<li>The <a href="/documentation/0.9.0/user-guide/">Aurora User Guide</a> provides an overview of how Aurora, Mesos, and Thermos work “under the hood”.</li> <li>Explore the Aurora Client - use <code>aurora -h</code>, and read the -<a href="/documentation/0.9.0//">Aurora Client Commands</a> document.</li> +<a href="/documentation/0.9.0/client-commands/">Aurora Client Commands</a> document.</li> </ul> </div> Modified: aurora/site/publish/documentation/0.9.0/user-guide/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/user-guide/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/user-guide/index.html (original) +++ aurora/site/publish/documentation/0.9.0/user-guide/index.html Sun Dec 13 00:49:43 2015 @@ -68,7 +68,7 @@ <p>This document gives an overview of how Aurora works under the hood. It assumes you’ve already worked through the “hello world” example -job in the <a href="/documentation/0.9.0//">Aurora Tutorial</a>. Specifics of how to use Aurora are <strong>not</strong> +job in the <a href="/documentation/0.9.0/tutorial/">Aurora Tutorial</a>. Specifics of how to use Aurora are <strong>not</strong> given here, but pointers to documentation about how to use Aurora are provided.</p> @@ -280,7 +280,7 @@ requests:</p> </tbody></table> <p>Please see the -<a href="/documentation/0.9.0//">configuration reference</a> for +<a href="/documentation/0.9.0/configuration-reference/#healthcheckconfig-objects">configuration reference</a> for configuration options for this feature.</p> <h4 id="snoozing-health-checks">Snoozing Health Checks</h4> @@ -363,8 +363,8 @@ Aurora configuration files. Their filena suffix, and you write them in Python making use of the Pystachio templating language, along with specific Aurora, Mesos, and Thermos commands and methods. See the -<a href="/documentation/0.9.0//">Configuration Guide and Reference</a> and -<a href="/documentation/0.9.0//">Configuration Tutorial</a>.</p> +<a href="/documentation/0.9.0/configuration-reference/">Configuration Guide and Reference</a> and +<a href="/documentation/0.9.0/configuration-tutorial/">Configuration Tutorial</a>.</p> <h2 id="service-discovery">Service Discovery</h2> @@ -380,13 +380,13 @@ of which there are several reference imp <p>These can also be used natively in Finagle using the <a href="https://github.com/twitter/finagle/blob/master/finagle-serversets/src/main/scala/com/twitter/finagle/zookeeper/ZookeeperServerSetCluster.scala";>ZookeeperServerSetCluster</a>.</p> -<p>For more information about how to configure announcing, see the <a href="/documentation/0.9.0//">Configuration Reference</a>.</p> +<p>For more information about how to configure announcing, see the <a href="/documentation/0.9.0/configuration-reference/">Configuration Reference</a>.</p> <h2 id="creating-jobs">Creating Jobs</h2> <p>You create and manipulate Aurora Jobs with the Aurora client, which starts all its command line commands with -<code>aurora</code>. See <a href="/documentation/0.9.0//">Aurora Client Commands</a> for details +<code>aurora</code>. See <a href="/documentation/0.9.0/client-commands/">Aurora Client Commands</a> for details about the Aurora Client.</p> <h2 id="interacting-with-jobs">Interacting With Jobs</h2> @@ -426,7 +426,7 @@ about the Aurora Client.</p> <li>The Aurora client</li> </ul> -<p>See <a href="/documentation/0.9.0//">client commands</a>.</p> +<p>See <a href="/documentation/0.9.0/client-commands/">client commands</a>.</p> </div> Modified: aurora/site/publish/documentation/0.9.0/vagrant/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.9.0/vagrant/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/0.9.0/vagrant/index.html (original) +++ aurora/site/publish/documentation/0.9.0/vagrant/index.html Sun Dec 13 00:49:43 2015 @@ -134,7 +134,7 @@ will use in client commands.</p> <h2 id="run-your-first-job">Run your first job</h2> <p>Now that your cluster is up and running, you are ready to define and run your first job in Aurora. -For more information, see the <a href="/documentation/0.9.0//">Aurora Tutorial</a>.</p> +For more information, see the <a href="/documentation/0.9.0/tutorial/">Aurora Tutorial</a>.</p> <h2 id="rebuild-components">Rebuild components</h2> Modified: aurora/site/publish/documentation/latest/client-commands/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/client-commands/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/client-commands/index.html (original) +++ aurora/site/publish/documentation/latest/client-commands/index.html Sun Dec 13 00:49:43 2015 @@ -129,7 +129,7 @@ communicates with a single (non-leader-e </code></pre> <p>For more details on cluster configuration see the -<a href="/documentation/latest//">Client Cluster Configuration</a> documentation.</p> +<a href="/documentation/latest/client-cluster-configuration/">Client Cluster Configuration</a> documentation.</p> <h2 id="job-keys">Job Keys</h2> @@ -175,7 +175,7 @@ the machine executing Aurora commands.</ </ul> <p>The process for writing and activating them is complex enough -that we explain it in a devoted document, <a href="/documentation/latest//">Hooks for Aurora Client API</a>.</p> +that we explain it in a devoted document, <a href="/documentation/latest/hooks/">Hooks for Aurora Client API</a>.</p> <h2 id="regular-jobs">Regular Jobs</h2> @@ -247,7 +247,7 @@ pulsing an active coordinated job update <a href="https://github.com/apache/aurora/blob/#{git_tag}/api/src/main/thrift/org/apache/aurora/gen/api.thrift";>pulseJobUpdate RPC</a>).</p> <p>A coordinated update is defined by setting a positive -<a href="/documentation/latest//">pulse<em>interval</em>secs</a> value in job configuration +<a href="/documentation/latest/configuration-reference/#updateconfig-objects">pulse<em>interval</em>secs</a> value in job configuration file. If no pulses are received within specified interval the update will be blocked. A blocked update is unable to continue rolling forward (or rolling back) but retains its active status. It may only be unblocked by a fresh <code>pulseJobUpdate</code> call.</p> @@ -336,7 +336,7 @@ if it contains hook definitions and acti <h2 id="cron-jobs">Cron Jobs</h2> <p>You can manage cron jobs using the <code>aurora cron</code> command. Please see -<a href="/documentation/latest//">cron-jobs.md</a> for more details.</p> +<a href="/documentation/latest/cron-jobs/">cron-jobs.md</a> for more details.</p> <p>You will see various commands and options relating to cron jobs in <code>aurora -h</code> and similar. Ignore them, as they’re not yet implemented.</p> @@ -372,8 +372,8 @@ configuration file, and displays the par </code></pre> <p>Prints the production quota allocated to the role’s value at the given -cluster. Only non-<a href="/documentation/latest//">dedicated</a> -<a href="/documentation/latest//">production</a> jobs consume quota.</p> +cluster. Only non-<a href="/documentation/latest/deploying-aurora-scheduler/#dedicated-attribute">dedicated</a> +<a href="/documentation/latest/configuration-reference/#job-objects">production</a> jobs consume quota.</p> <h3 id="finding-a-job-on-web-ui">Finding a Job on Web UI</h3> Modified: aurora/site/publish/documentation/latest/configuration-reference/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/configuration-reference/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/configuration-reference/index.html (original) +++ aurora/site/publish/documentation/latest/configuration-reference/index.html Sun Dec 13 00:49:43 2015 @@ -114,8 +114,8 @@ powerful, and configurations can become cases.</p> <p>For examples of simple configurations to get something up and running -quickly, check out the <a href="/documentation/latest//">Tutorial</a>. When you feel comfortable with the basics, move -on to the <a href="/documentation/latest//">Configuration Tutorial</a> for more in-depth coverage of +quickly, check out the <a href="/documentation/latest/tutorial/">Tutorial</a>. When you feel comfortable with the basics, move +on to the <a href="/documentation/latest/configuration-tutorial/">Configuration Tutorial</a> for more in-depth coverage of configuration design.</p> <p>For additional basic configuration examples, see <a href="#BasicExamples">the end of this document</a>.</p> @@ -439,7 +439,7 @@ ordering constraints.</p> <h3 id="resource-object">Resource Object</h3> <p>Specifies the amount of CPU, Ram, and disk resources the task needs. See the -<a href="/documentation/latest//">Resource Isolation document</a> for suggested values and to understand how +<a href="/documentation/latest/resources/">Resource Isolation document</a> for suggested values and to understand how resources are allocated.</p> <table><thead> @@ -515,7 +515,7 @@ resources are allocated.</p> <tr> <td><code>cron_schedule</code></td> <td style="text-align: center">String</td> -<td>Cron schedule in cron format. May only be used with non-service jobs. See <a href="/documentation/latest//">Cron Jobs</a> for more information. Default: None (not a cron job.)</td> +<td>Cron schedule in cron format. May only be used with non-service jobs. See <a href="/documentation/latest/cron-jobs/">Cron Jobs</a> for more information. Default: None (not a cron job.)</td> </tr> <tr> <td><code>cron_collision_policy</code></td> @@ -550,7 +550,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="/documentation/latest//">preempt</a> other tasks (Default: False). Production job role must have the appropriate <a href="/documentation/latest//">quota</a>.</td> +<td>Whether or not this is a production task that may <a href="/documentation/latest/resources/#task-preemption">preempt</a> other tasks (Default: False). Production job role must have the appropriate <a href="/documentation/latest/resources/#resource-quota">quota</a>.</td> </tr> <tr> <td><code>health_check_config</code></td> @@ -595,7 +595,7 @@ value.</p> <p>More implementation details in this <a href="https://issues.apache.org/jira/browse/AURORA-1343";>ticket</a>.</p> -<p>Scheduler must be <a href="/documentation/latest//">configured</a> +<p>Scheduler must be <a href="/documentation/latest/deploying-aurora-scheduler/#configuring-resource-oversubscription">configured</a> to receive revocable offers from Mesos and accept revocable jobs. If not configured properly revocable tasks will never get assigned to hosts and will stay in PENDING.</p> @@ -648,7 +648,7 @@ revocable tasks will never get assigned <tr> <td><code>pulse_interval_secs</code></td> <td style="text-align: center">Integer</td> -<td>Indicates a <a href="/documentation/latest//">coordinated update</a>. If no pulses are received within the provided interval the update will be blocked. Beta-updater only. Will fail on submission when used with client updater. (Default: None)</td> +<td>Indicates a <a href="/documentation/latest/client-commands/#coordinated-job-updates">coordinated update</a>. If no pulses are received within the provided interval the update will be blocked. Beta-updater only. Will fail on submission when used with client updater. (Default: None)</td> </tr> </tbody></table> @@ -705,7 +705,7 @@ revocable tasks will never get assigned <p>If the <code>announce</code> field in the Job configuration is set, each task will be registered in the ServerSet <code>/aurora/role/environment/jobname</code> in the zookeeper ensemble configured by the executor. If no Announcer object is specified, -no announcement will take place. For more information about ServerSets, see the <a href="/documentation/latest//">User Guide</a>.</p> +no announcement will take place. For more information about ServerSets, see the <a href="/documentation/latest/user-guide/">User Guide</a>.</p> <table><thead> <tr> Modified: aurora/site/publish/documentation/latest/configuration-tutorial/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/configuration-tutorial/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/configuration-tutorial/index.html (original) +++ aurora/site/publish/documentation/latest/configuration-tutorial/index.html Sun Dec 13 00:49:43 2015 @@ -47,7 +47,7 @@ and best practices. When writing a confi arguments as <code>aurora job create</code> or <code>aurora job update</code>. It first ensures the configuration parses, then outputs it in human-readable form.</p> -<p>You should read this after going through the general <a href="/documentation/latest//">Aurora Tutorial</a>.</p> +<p>You should read this after going through the general <a href="/documentation/latest/tutorial/">Aurora Tutorial</a>.</p> <ul> <li><a href="#aurora-configuration-tutorial">Aurora Configuration Tutorial</a> @@ -151,12 +151,12 @@ configuration specification and reuse. P via {{}} surrounded templates.</p> <p>When writing your <code>.aurora</code> file, you may use any Pystachio datatypes, as -well as any objects shown in the <a href="/documentation/latest//"><em>Aurora+Thermos Configuration +well as any objects shown in the <a href="/documentation/latest/configuration-reference/"><em>Aurora+Thermos Configuration Reference</em></a>, without <code>import</code> statements - the Aurora config loader injects them automatically. Other than that, an <code>.aurora</code> file works like any other Python script.</p> -<p><a href="/documentation/latest//"><em>Aurora+Thermos Configuration Reference</em></a> +<p><a href="/documentation/latest/configuration-reference/"><em>Aurora+Thermos Configuration Reference</em></a> has a full reference of all Aurora/Thermos defined Pystachio objects.</p> <h3 id="use-bottom-to-top-object-ordering">Use Bottom-To-Top Object Ordering</h3> @@ -315,7 +315,7 @@ run = Process(name = 'app', cmdline = 'j run_task = SequentialTask(processes = [stage, run]) </code></pre> -<p><code>Process</code> also has optional attributes to customize its behaviour. Details can be found in the <a href="/documentation/latest//"><em>Aurora+Thermos Configuration Reference</em></a>.</p> +<p><code>Process</code> also has optional attributes to customize its behaviour. Details can be found in the <a href="/documentation/latest/configuration-reference/#process-objects"><em>Aurora+Thermos Configuration Reference</em></a>.</p> <h2 id="getting-your-code-into-the-sandbox">Getting Your Code Into The Sandbox</h2> @@ -375,7 +375,7 @@ the processes run in parallel or sequent disk = 1*GB)) </code></pre> -<p>A Task has optional attributes to customize its behaviour. Details can be found in the <a href="/documentation/latest//"><em>Aurora+Thermos Configuration Reference</em></a></p> +<p>A Task has optional attributes to customize its behaviour. Details can be found in the <a href="/documentation/latest/configuration-reference/#task-object"><em>Aurora+Thermos Configuration Reference</em></a></p> <h3 id="sequentialtask-running-processes-in-parallel-or-sequentially">SequentialTask: Running Processes in Parallel or Sequentially</h3> @@ -532,7 +532,7 @@ default. For these four parameters, a Jo </code></pre> <p>In addition to the required attributes, there are several optional -attributes. Details can be found in the <a href="/documentation/latest//">Aurora+Thermos Configuration Reference</a>.</p> +attributes. Details can be found in the <a href="/documentation/latest/configuration-reference/#job-objects">Aurora+Thermos Configuration Reference</a>.</p> <h2 id="the-jobs-list">The jobs List</h2> @@ -548,7 +548,7 @@ following runs first <code>job1</code>, <code>Process</code>, and other classes are defined by a templating library called <em>Pystachio</em>, a powerful tool for configuration specification and reuse.</p> -<p><a href="/documentation/latest//">Aurora+Thermos Configuration Reference</a> +<p><a href="/documentation/latest/configuration-reference/">Aurora+Thermos Configuration Reference</a> has a full reference of all Aurora/Thermos defined Pystachio objects.</p> <p>When writing your <code>.aurora</code> file, you may use any Pystachio datatypes, as Modified: aurora/site/publish/documentation/latest/cron-jobs/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/cron-jobs/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/cron-jobs/index.html (original) +++ aurora/site/publish/documentation/latest/cron-jobs/index.html Sun Dec 13 00:49:43 2015 @@ -74,11 +74,11 @@ <p>A job is identified as a cron job by the presence of a <code>cron_schedule</code> attribute containing a cron-style schedule in the -<a href="/documentation/latest//"><code>Job</code></a> object. Examples of cron schedules +<a href="/documentation/latest/configuration-reference/#job-objects"><code>Job</code></a> object. Examples of cron schedules include “every 5 minutes” (<code>*/5 * * * *</code>), “Fridays at 17:00” (<code>* 17 * * FRI</code>), and “the 1st and 15th day of the month at 03:00” (<code>0 3 1,15 *</code>).</p> -<p>Example (available in the <a href="/documentation/latest//">Vagrant environment</a>):</p> +<p>Example (available in the <a href="/documentation/latest/vagrant/">Vagrant environment</a>):</p> <pre class="highlight plaintext"><code>$ cat /vagrant/examples/job/cron_hello_world.aurora # cron_hello_world.aurora # A cron job that runs every 5 minutes. @@ -119,7 +119,7 @@ grow faster than they can process it.</p <p>Unlike with services, which aurora will always re-execute regardless of exit status, instances of cron jobs retry according to the <code>max_task_failures</code> attribute of the -<a href="/documentation/latest//">Task</a> object. To get “run-until-success” semantics, +<a href="/documentation/latest/configuration-reference/#task-objects">Task</a> object. To get “run-until-success” semantics, set <code>max_task_failures</code> to <code>-1</code>.</p> <h2 id="interacting-with-cron-jobs-via-the-aurora-cli">Interacting with cron jobs via the Aurora CLI</h2> Modified: aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html (original) +++ aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html Sun Dec 13 00:49:43 2015 @@ -203,7 +203,7 @@ should be set to <code>2</code>, and in <p><em>Incorrectly setting this flag will cause data corruption to occur!</em></p> -<p>See <a href="/documentation/latest//">this document</a> for more replicated +<p>See <a href="/documentation/latest/storage-config/#scheduler-storage-configuration-flags">this document</a> for more replicated log and storage configuration options.</p> <h2 id="initializing-the-replicated-log">Initializing the Replicated Log</h2> @@ -219,7 +219,7 @@ Failing to do this will result the follo <h3 id="storage-performance-considerations">Storage Performance Considerations</h3> -<p>See <a href="/documentation/latest//">this document</a> for scheduler storage performance considerations.</p> +<p>See <a href="/documentation/latest/scheduler-storage/">this document</a> for scheduler storage performance considerations.</p> <h3 id="network-considerations">Network considerations</h3> @@ -279,12 +279,12 @@ restarted.</p> <h2 id="security-considerations">Security Considerations</h2> -<p>See <a href="/documentation/latest//">security.md</a>.</p> +<p>See <a href="/documentation/latest/security/">security.md</a>.</p> <h2 id="configuring-resource-oversubscription">Configuring Resource Oversubscription</h2> <p><strong>WARNING</strong>: This feature is currently in alpha status. Do not use it in production clusters! -See <a href="/documentation/latest//">this document</a> for more feature details.</p> +See <a href="/documentation/latest/configuration-reference/#revocable-jobs">this document</a> for more feature details.</p> <p>Set these scheduler flag to allow receiving revocable Mesos offers:</p> <pre class="highlight plaintext"><code>-receive_revocable_resources=true @@ -300,7 +300,7 @@ See <a href="/documentation/latest//"> <h3 id="monitoring">Monitoring</h3> -<p>Please see our dedicated <a href="/documentation/latest//">monitoring guide</a> for in-depth discussion on monitoring.</p> +<p>Please see our dedicated <a href="/documentation/latest/monitoring/">monitoring guide</a> for in-depth discussion on monitoring.</p> <h3 id="running-stateful-services">Running stateful services</h3> @@ -313,12 +313,12 @@ like databases, or services that otherwi static attributes (not to be confused with <code>--resources</code>, which are dynamic and accounted).</p> <p>Aurora makes these attributes available for matching with scheduling -<a href="/documentation/latest//">constraints</a>. Most of these +<a href="/documentation/latest/configuration-reference/#specifying-scheduling-constraints">constraints</a>. Most of these constraints are arbitrary and available for custom use. There is one exception, though: the <code>dedicated</code> attribute. Aurora treats this specially, and only allows matching jobs to run on these machines, and will only schedule matching jobs on these machines.</p> -<p>See the <a href="/documentation/latest//">section</a> about resource quotas to learn how quotas apply to +<p>See the <a href="/documentation/latest/resources/#resource-quota">section</a> about resource quotas to learn how quotas apply to dedicated jobs.</p> <h5 id="syntax">Syntax</h5> @@ -361,7 +361,7 @@ the mesos-slave with them as <p>When it comes time to schedule jobs, Aurora will automatically spread them across the failure domains as specified in the -<a href="/documentation/latest//">job configuration</a>.</p> +<a href="/documentation/latest/configuration-reference/#specifying-scheduling-constraints">job configuration</a>.</p> <p>Note: in virtualized environments like EC2, the only attribute that usually makes sense for this purpose is <code>host</code>.</p> @@ -419,7 +419,7 @@ Since Aurora uses a Mesos replicated log <h3 id="preparation">Preparation</h3> -<p>Increase <a href="/documentation/latest//">-native<em>log</em>quorum_size</a> on each +<p>Increase <a href="/documentation/latest/storage-config/#-native_log_quorum_size">-native<em>log</em>quorum_size</a> on each existing scheduler and restart them. When updating from 3 to 5 schedulers, the quorum size would grow from 2 to 3.</p> @@ -428,7 +428,7 @@ would grow from 2 to 3.</p> <p>Start the new schedulers with <code>-native_log_quorum_size</code> set to the new value. Failing to first increase the quorum size on running schedulers can in some cases result in corruption or truncating of the replicated log used by Aurora. In that case, see the documentation on -<a href="/documentation/latest//">recovering from backup</a>.</p> +<a href="/documentation/latest/storage-config/#recovering-from-a-scheduler-backup">recovering from backup</a>.</p> </div> Modified: aurora/site/publish/documentation/latest/developing-aurora-client/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/developing-aurora-client/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/developing-aurora-client/index.html (original) +++ aurora/site/publish/documentation/latest/developing-aurora-client/index.html Sun Dec 13 00:49:43 2015 @@ -48,9 +48,9 @@ <p>The client uses a configuration file that specifies available clusters. More information about the contents of this file can be found in the -<a href="/documentation/latest//">Client Cluster Configuration</a> documentation. Information about +<a href="/documentation/latest/client-cluster-configuration/">Client Cluster Configuration</a> documentation. Information about how the client locates this file can be found in the -<a href="/documentation/latest//">Client Commands</a> documentation.</p> +<a href="/documentation/latest/client-commands/#cluster-configuration">Client Commands</a> documentation.</p> <h1 id="building-and-testing-the-client">Building and Testing the Client</h1> @@ -128,7 +128,7 @@ is the directory where our example clust <h1 id="making-thrift-schema-changes">Making thrift schema changes</h1> -<p>See <a href="/documentation/latest//">this document</a> for any thrift related changes.</p> +<p>See <a href="/documentation/latest/thrift-deprecation/">this document</a> for any thrift related changes.</p> </div> Modified: aurora/site/publish/documentation/latest/developing-aurora-scheduler/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/developing-aurora-scheduler/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/developing-aurora-scheduler/index.html (original) +++ aurora/site/publish/documentation/latest/developing-aurora-scheduler/index.html Sun Dec 13 00:49:43 2015 @@ -166,7 +166,7 @@ repository root and commit the changed f <h1 id="making-thrift-schema-changes">Making thrift schema changes</h1> -<p>See <a href="/documentation/latest//">this document</a> for any thrift related changes.</p> +<p>See <a href="/documentation/latest/thrift-deprecation/">this document</a> for any thrift related changes.</p> </div> Modified: aurora/site/publish/documentation/latest/resources/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/resources/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/resources/index.html (original) +++ aurora/site/publish/documentation/latest/resources/index.html Sun Dec 13 00:49:43 2015 @@ -191,21 +191,21 @@ the same host may cause contention.</p> <h2 id="resource-quota">Resource Quota</h2> <p>Aurora requires resource quotas for -<a href="/documentation/latest//">production non-dedicated jobs</a>. Quota is enforced at +<a href="/documentation/latest/configuration-reference/#job-objects">production non-dedicated jobs</a>. Quota is enforced at the job role level and when set, defines a non-preemptible pool of compute resources within that role.</p> <p>To grant quota to a particular role in production use <code>aurora_admin set_quota</code> command.</p> <p>NOTE: all job types (service, adhoc or cron) require role resource quota unless a job has -<a href="/documentation/latest//">dedicated constraint set</a>.</p> +<a href="/documentation/latest/deploying-aurora-scheduler/#dedicated-attribute">dedicated constraint set</a>.</p> <h2 id="task-preemption">Task preemption</h2> <p>Under a particular resource shortage pressure, tasks from -<a href="/documentation/latest//">production</a> jobs may preempt tasks from any non-production +<a href="/documentation/latest/configuration-reference/#job-objects">production</a> jobs may preempt tasks from any non-production job. A production task may only be preempted by tasks from production jobs in the same role with -higher <a href="/documentation/latest//">priority</a>.</p> +higher <a href="/documentation/latest/configuration-reference/#job-objects">priority</a>.</p> </div> Modified: aurora/site/publish/documentation/latest/storage-config/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/storage-config/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/storage-config/index.html (original) +++ aurora/site/publish/documentation/latest/storage-config/index.html Sun Dec 13 00:49:43 2015 @@ -71,7 +71,7 @@ <p>This document summarizes Aurora storage configuration and maintenance details and is intended for use by anyone deploying and/or maintaining Aurora.</p> -<p>For a high level overview of the Aurora storage architecture refer to <a href="/documentation/latest//">this document</a>.</p> +<p>For a high level overview of the Aurora storage architecture refer to <a href="/documentation/latest/storage/">this document</a>.</p> <h2 id="scheduler-storage-configuration-flags">Scheduler storage configuration flags</h2> @@ -83,7 +83,7 @@ or require attention before deploying in <h4 id="nativelogquorum_size">-native<em>log</em>quorum_size</h4> <p>Defines the Mesos replicated log quorum size. See -<a href="/documentation/latest//">the replicated log configuration document</a> +<a href="/documentation/latest/deploying-aurora-scheduler/#replicated-log-configuration">the replicated log configuration document</a> on how to choose the right value.</p> <h4 id="nativelogfile_path">-native<em>log</em>file_path</h4> Modified: aurora/site/publish/documentation/latest/storage/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/storage/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/storage/index.html (original) +++ aurora/site/publish/documentation/latest/storage/index.html Sun Dec 13 00:49:43 2015 @@ -82,7 +82,7 @@ is <a href="https://github.com/apache/th This helps establishing periodic recovery checkpoints and speeds up volatile storage recovery on restart.</li> <li>Backup manager: as a precaution, snapshots are periodically written out into backup files. -This solves a <a href="/documentation/latest//">disaster recovery problem</a> +This solves a <a href="/documentation/latest/storage-config/#recovering-from-a-scheduler-backup">disaster recovery problem</a> in case of a complete loss or corruption of Mesos log files.</li> </ul> Modified: aurora/site/publish/documentation/latest/test-resource-generation/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/test-resource-generation/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/test-resource-generation/index.html (original) +++ aurora/site/publish/documentation/latest/test-resource-generation/index.html Sun Dec 13 00:49:43 2015 @@ -62,7 +62,7 @@ that would undermine the goal of ensurin <p>The most common reason to add a new checkpoint file would be to provide coverage for new thermos features that alter the data format. This is accomplished by writing and running a -<a href="/documentation/latest//">job configuration</a> that exercises the feature, and +<a href="/documentation/latest/configuration-reference/">job configuration</a> that exercises the feature, and copying the checkpoint file from the sandbox directory, by default this is <code>/var/run/thermos/checkpoints/<aurora task id></code>.</p> Modified: aurora/site/publish/documentation/latest/thrift-deprecation/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/thrift-deprecation/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/thrift-deprecation/index.html (original) +++ aurora/site/publish/documentation/latest/thrift-deprecation/index.html Sun Dec 13 00:49:43 2015 @@ -92,7 +92,7 @@ See <a href="https://github.com/apache/a <p>It’s always advisable to test your changes in the local vagrant environment to build more confidence that you change is backwards compatible. It’s easy to simulate different -client/scheduler versions by playing with <code>aurorabuild</code> command. See <a href="/documentation/latest//">this document</a> +client/scheduler versions by playing with <code>aurorabuild</code> command. See <a href="/documentation/latest/vagrant/">this document</a> for more.</p> </div> Modified: aurora/site/publish/documentation/latest/tutorial/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/tutorial/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/tutorial/index.html (original) +++ aurora/site/publish/documentation/latest/tutorial/index.html Sun Dec 13 00:49:43 2015 @@ -74,7 +74,7 @@ getting up to speed on the system.</p> <h2 id="setup-install-aurora">Setup: Install Aurora</h2> <p>You use the Aurora client and web UI to interact with Aurora jobs. To -install it locally, see <a href="/documentation/latest//">vagrant.md</a>. The remainder of this +install it locally, see <a href="/documentation/latest/vagrant/">vagrant.md</a>. The remainder of this Tutorial assumes you are running Aurora using Vagrant. Unless otherwise stated, all commands are to be run from the root of the aurora repository clone.</p> @@ -146,8 +146,8 @@ code in the file <code>hello_world.auror <span style="background-color: #f8f8f8">]</span> </code></pre> -<p>For more about Aurora configuration files, see the <a href="/documentation/latest//">Configuration -Tutorial</a> and the <a href="/documentation/latest//">Aurora + Thermos +<p>For more about Aurora configuration files, see the <a href="/documentation/latest/configuration-tutorial/">Configuration +Tutorial</a> and the <a href="/documentation/latest/configuration-reference/">Aurora + Thermos Reference</a> (preferably after finishing this tutorial).</p> @@ -298,13 +298,13 @@ vagrant@precise64:~$ <p>Now that you’ve finished this Tutorial, you should read or do the following:</p> <ul> -<li><a href="/documentation/latest//">The Aurora Configuration Tutorial</a>, which provides more examples +<li><a href="/documentation/latest/configuration-tutorial/">The Aurora Configuration Tutorial</a>, which provides more examples and best practices for writing Aurora configurations. You should also look at -the <a href="/documentation/latest//">Aurora + Thermos Configuration Reference</a>.</li> -<li>The <a href="/documentation/latest//">Aurora User Guide</a> provides an overview of how Aurora, Mesos, and +the <a href="/documentation/latest/configuration-reference/">Aurora + Thermos Configuration Reference</a>.</li> +<li>The <a href="/documentation/latest/user-guide/">Aurora User Guide</a> provides an overview of how Aurora, Mesos, and Thermos work “under the hood”.</li> <li>Explore the Aurora Client - use <code>aurora -h</code>, and read the -<a href="/documentation/latest//">Aurora Client Commands</a> document.</li> +<a href="/documentation/latest/client-commands/">Aurora Client Commands</a> document.</li> </ul> </div> Modified: aurora/site/publish/documentation/latest/user-guide/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/user-guide/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/user-guide/index.html (original) +++ aurora/site/publish/documentation/latest/user-guide/index.html Sun Dec 13 00:49:43 2015 @@ -68,7 +68,7 @@ <p>This document gives an overview of how Aurora works under the hood. It assumes you’ve already worked through the “hello world” example -job in the <a href="/documentation/latest//">Aurora Tutorial</a>. Specifics of how to use Aurora are <strong>not</strong> +job in the <a href="/documentation/latest/tutorial/">Aurora Tutorial</a>. Specifics of how to use Aurora are <strong>not</strong> given here, but pointers to documentation about how to use Aurora are provided.</p> @@ -280,7 +280,7 @@ requests:</p> </tbody></table> <p>Please see the -<a href="/documentation/latest//">configuration reference</a> for +<a href="/documentation/latest/configuration-reference/#healthcheckconfig-objects">configuration reference</a> for configuration options for this feature.</p> <h4 id="snoozing-health-checks">Snoozing Health Checks</h4> @@ -363,8 +363,8 @@ Aurora configuration files. Their filena suffix, and you write them in Python making use of the Pystachio templating language, along with specific Aurora, Mesos, and Thermos commands and methods. See the -<a href="/documentation/latest//">Configuration Guide and Reference</a> and -<a href="/documentation/latest//">Configuration Tutorial</a>.</p> +<a href="/documentation/latest/configuration-reference/">Configuration Guide and Reference</a> and +<a href="/documentation/latest/configuration-tutorial/">Configuration Tutorial</a>.</p> <h2 id="service-discovery">Service Discovery</h2> @@ -380,13 +380,13 @@ of which there are several reference imp <p>These can also be used natively in Finagle using the <a href="https://github.com/twitter/finagle/blob/master/finagle-serversets/src/main/scala/com/twitter/finagle/zookeeper/ZookeeperServerSetCluster.scala";>ZookeeperServerSetCluster</a>.</p> -<p>For more information about how to configure announcing, see the <a href="/documentation/latest//">Configuration Reference</a>.</p> +<p>For more information about how to configure announcing, see the <a href="/documentation/latest/configuration-reference/">Configuration Reference</a>.</p> <h2 id="creating-jobs">Creating Jobs</h2> <p>You create and manipulate Aurora Jobs with the Aurora client, which starts all its command line commands with -<code>aurora</code>. See <a href="/documentation/latest//">Aurora Client Commands</a> for details +<code>aurora</code>. See <a href="/documentation/latest/client-commands/">Aurora Client Commands</a> for details about the Aurora Client.</p> <h2 id="interacting-with-jobs">Interacting With Jobs</h2> @@ -426,7 +426,7 @@ about the Aurora Client.</p> <li>The Aurora client</li> </ul> -<p>See <a href="/documentation/latest//">client commands</a>.</p> +<p>See <a href="/documentation/latest/client-commands/">client commands</a>.</p> </div> Modified: aurora/site/publish/documentation/latest/vagrant/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/vagrant/index.html?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/vagrant/index.html (original) +++ aurora/site/publish/documentation/latest/vagrant/index.html Sun Dec 13 00:49:43 2015 @@ -134,7 +134,7 @@ will use in client commands.</p> <h2 id="run-your-first-job">Run your first job</h2> <p>Now that your cluster is up and running, you are ready to define and run your first job in Aurora. -For more information, see the <a href="/documentation/latest//">Aurora Tutorial</a>.</p> +For more information, see the <a href="/documentation/latest/tutorial/">Aurora Tutorial</a>.</p> <h2 id="rebuild-components">Rebuild components</h2> Modified: aurora/site/publish/sitemap.xml URL: http://svn.apache.org/viewvc/aurora/site/publish/sitemap.xml?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/publish/sitemap.xml (original) +++ aurora/site/publish/sitemap.xml Sun Dec 13 00:49:43 2015 @@ -265,11 +265,11 @@ <lastmod>2015-12-13T00:00:00+00:00</lastmod> </url> <url> - <loc>http://aurora.apache.org/documentation/0.6.0-incubating/monitoring/</loc> + <loc>http://aurora.apache.org/documentation/0.6.0-incubating/</loc> <lastmod>2015-12-13T00:00:00+00:00</lastmod> </url> <url> - <loc>http://aurora.apache.org/documentation/0.6.0-incubating/README/</loc> + <loc>http://aurora.apache.org/documentation/0.6.0-incubating/monitoring/</loc> <lastmod>2015-12-13T00:00:00+00:00</lastmod> </url> <url> @@ -645,6 +645,10 @@ <lastmod>2015-12-13T00:00:00+00:00</lastmod> </url> <url> + <loc>http://aurora.apache.org/documentation/latest/</loc> + <lastmod>2015-12-13T00:00:00+00:00</lastmod> + </url> + <url> <loc>http://aurora.apache.org/documentation/latest/monitoring/</loc> <lastmod>2015-12-13T00:00:00+00:00</lastmod> </url> Modified: aurora/site/source/documentation/0.10.0/client-commands.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.10.0/client-commands.md?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/source/documentation/0.10.0/client-commands.md (original) +++ aurora/site/source/documentation/0.10.0/client-commands.md Sun Dec 13 00:49:43 2015 @@ -84,7 +84,7 @@ A configuration for a leader-elected sch ``` For more details on cluster configuration see the -[Client Cluster Configuration](/documentation/0.10.0//) documentation. +[Client Cluster Configuration](/documentation/0.10.0/client-cluster-configuration/) documentation. Job Keys -------- @@ -130,7 +130,7 @@ Hooks can be associated with these Auror - `job update` The process for writing and activating them is complex enough -that we explain it in a devoted document, [Hooks for Aurora Client API](/documentation/0.10.0//). +that we explain it in a devoted document, [Hooks for Aurora Client API](/documentation/0.10.0/hooks/). Regular Jobs ------------ @@ -203,7 +203,7 @@ pulsing an active coordinated job update [pulseJobUpdate RPC](https://github.com/apache/aurora/blob/#{git_tag}/api/src/main/thrift/org/apache/aurora/gen/api.thrift)). A coordinated update is defined by setting a positive -[pulse_interval_secs](/documentation/0.10.0//) value in job configuration +[pulse_interval_secs](/documentation/0.10.0/configuration-reference/#updateconfig-objects) value in job configuration file. If no pulses are received within specified interval the update will be blocked. A blocked update is unable to continue rolling forward (or rolling back) but retains its active status. It may only be unblocked by a fresh `pulseJobUpdate` call. @@ -294,7 +294,7 @@ Cron Jobs --------- You can manage cron jobs using the `aurora cron` command. Please see -[cron-jobs.md](/documentation/0.10.0//) for more details. +[cron-jobs.md](/documentation/0.10.0/cron-jobs/) for more details. You will see various commands and options relating to cron jobs in `aurora -h` and similar. Ignore them, as they're not yet implemented. @@ -332,8 +332,8 @@ configuration file, and displays the par aurora quota get CLUSTER/ROLE Prints the production quota allocated to the role's value at the given -cluster. Only non-[dedicated](/documentation/0.10.0//) -[production](/documentation/0.10.0//) jobs consume quota. +cluster. Only non-[dedicated](/documentation/0.10.0/deploying-aurora-scheduler/#dedicated-attribute) +[production](/documentation/0.10.0/configuration-reference/#job-objects) jobs consume quota. ### Finding a Job on Web UI Modified: aurora/site/source/documentation/0.10.0/configuration-reference.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.10.0/configuration-reference.md?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/source/documentation/0.10.0/configuration-reference.md (original) +++ aurora/site/source/documentation/0.10.0/configuration-reference.md Sun Dec 13 00:49:43 2015 @@ -49,8 +49,8 @@ powerful, and configurations can become cases. For examples of simple configurations to get something up and running -quickly, check out the [Tutorial](/documentation/0.10.0//). When you feel comfortable with the basics, move -on to the [Configuration Tutorial](/documentation/0.10.0//) for more in-depth coverage of +quickly, check out the [Tutorial](/documentation/0.10.0/tutorial/). When you feel comfortable with the basics, move +on to the [Configuration Tutorial](/documentation/0.10.0/configuration-tutorial/) for more in-depth coverage of configuration design. For additional basic configuration examples, see [the end of this document](#BasicExamples). @@ -301,7 +301,7 @@ ordering constraints. ### Resource Object Specifies the amount of CPU, Ram, and disk resources the task needs. See the -[Resource Isolation document](/documentation/0.10.0//) for suggested values and to understand how +[Resource Isolation document](/documentation/0.10.0/resources/) for suggested values and to understand how resources are allocated. param | type | description @@ -325,14 +325,14 @@ Job Schema ```environment``` | String | Job environment, default ```devel```. Must be one of ```prod```, ```devel```, ```test``` or ```staging<number>```. ```contact``` | String | Best email address to reach the owner of the job. For production jobs, this is usually a team mailing list. ```instances```| Integer | Number of instances (sometimes referred to as replicas or shards) of the task to create. (Default: 1) - ```cron_schedule``` | String | Cron schedule in cron format. May only be used with non-service jobs. See [Cron Jobs](/documentation/0.10.0//) for more information. Default: None (not a cron job.) + ```cron_schedule``` | String | Cron schedule in cron format. May only be used with non-service jobs. See [Cron Jobs](/documentation/0.10.0/cron-jobs/) for more information. Default: None (not a cron job.) ```cron_collision_policy``` | String | Policy to use when a cron job is triggered while a previous run is still active. KILL_EXISTING Kill the previous run, and schedule the new run CANCEL_NEW Let the previous run continue, and cancel the new run. (Default: KILL_EXISTING) ```update_config``` | ```UpdateConfig``` object | Parameters for controlling the rate and policy of rolling updates. ```constraints``` | dict | Scheduling constraints for the tasks. See the section on the [constraint specification language](#Specifying-Scheduling-Constraints) ```service``` | Boolean | If True, restart tasks regardless of success or failure. (Default: False) ```max_task_failures``` | Integer | Maximum number of failures after which the task is considered to have failed (Default: 1) Set to -1 to allow for infinite failures ```priority``` | Integer | Preemption priority to give the task (Default 0). Tasks with higher priorities may preempt tasks at lower priorities. - ```production``` | Boolean | Whether or not this is a production task that may [preempt](/documentation/0.10.0//) other tasks (Default: False). Production job role must have the appropriate [quota](/documentation/0.10.0//). + ```production``` | Boolean | Whether or not this is a production task that may [preempt](/documentation/0.10.0/resources/#task-preemption) other tasks (Default: False). Production job role must have the appropriate [quota](/documentation/0.10.0/resources/#resource-quota). ```health_check_config``` | ```HealthCheckConfig``` object | Parameters for controlling a task's health checks via HTTP. Only used if a health port was assigned with a command line wildcard. ```container``` | ```Container``` object | An optional container to run all processes inside of. ```lifecycle``` | ```LifecycleConfig``` object | An optional task lifecycle configuration that dictates commands to be executed on startup/teardown. HTTP lifecycle is enabled by default if the "health" port is requested. See [LifecycleConfig Objects](#lifecycleconfig-objects) for more information. @@ -359,7 +359,7 @@ value. More implementation details in this [ticket](https://issues.apache.org/jira/browse/AURORA-1343). -Scheduler must be [configured](/documentation/0.10.0//) +Scheduler must be [configured](/documentation/0.10.0/deploying-aurora-scheduler/#configuring-resource-oversubscription) to receive revocable offers from Mesos and accept revocable jobs. If not configured properly revocable tasks will never get assigned to hosts and will stay in PENDING. @@ -376,7 +376,7 @@ Parameters for controlling the rate and | ```max_total_failures``` | Integer | Maximum number of shard failures to be tolerated in total during an update. Cannot be greater than or equal to the total number of tasks in a job. (Default: 0) | ```rollback_on_failure``` | boolean | When False, prevents auto rollback of a failed update (Default: True) | ```wait_for_batch_completion```| boolean | When True, all threads from a given batch will be blocked from picking up new instances until the entire batch is updated. This essentially simulates the legacy sequential updater algorithm. (Default: False) -| ```pulse_interval_secs``` | Integer | Indicates a [coordinated update](/documentation/0.10.0//). If no pulses are received within the provided interval the update will be blocked. Beta-updater only. Will fail on submission when used with client updater. (Default: None) +| ```pulse_interval_secs``` | Integer | Indicates a [coordinated update](/documentation/0.10.0/client-commands/#coordinated-job-updates). If no pulses are received within the provided interval the update will be blocked. Beta-updater only. Will fail on submission when used with client updater. (Default: None) ### HealthCheckConfig Objects @@ -397,7 +397,7 @@ Parameters for controlling a task's heal If the `announce` field in the Job configuration is set, each task will be registered in the ServerSet `/aurora/role/environment/jobname` in the zookeeper ensemble configured by the executor. If no Announcer object is specified, -no announcement will take place. For more information about ServerSets, see the [User Guide](/documentation/0.10.0//). +no announcement will take place. For more information about ServerSets, see the [User Guide](/documentation/0.10.0/user-guide/). | object | type | description | ------- | :-------: | -------- Modified: aurora/site/source/documentation/0.10.0/configuration-tutorial.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.10.0/configuration-tutorial.md?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/source/documentation/0.10.0/configuration-tutorial.md (original) +++ aurora/site/source/documentation/0.10.0/configuration-tutorial.md Sun Dec 13 00:49:43 2015 @@ -7,7 +7,7 @@ and best practices. When writing a confi arguments as `aurora job create` or `aurora job update`. It first ensures the configuration parses, then outputs it in human-readable form. -You should read this after going through the general [Aurora Tutorial](/documentation/0.10.0//). +You should read this after going through the general [Aurora Tutorial](/documentation/0.10.0/tutorial/). - [Aurora Configuration Tutorial](#aurora-configuration-tutorial) - [The Basics](#the-basics) @@ -74,11 +74,11 @@ via {{}} surrounded templates. When writing your `.aurora` file, you may use any Pystachio datatypes, as well as any objects shown in the [*Aurora+Thermos Configuration -Reference*](/documentation/0.10.0//), without `import` statements - the +Reference*](/documentation/0.10.0/configuration-reference/), without `import` statements - the Aurora config loader injects them automatically. Other than that, an `.aurora` file works like any other Python script. -[*Aurora+Thermos Configuration Reference*](/documentation/0.10.0//) +[*Aurora+Thermos Configuration Reference*](/documentation/0.10.0/configuration-reference/) has a full reference of all Aurora/Thermos defined Pystachio objects. ### Use Bottom-To-Top Object Ordering @@ -236,7 +236,7 @@ above multiple `Process` definitions int run_task = SequentialTask(processes = [stage, run]) -`Process` also has optional attributes to customize its behaviour. Details can be found in the [*Aurora+Thermos Configuration Reference*](/documentation/0.10.0//). +`Process` also has optional attributes to customize its behaviour. Details can be found in the [*Aurora+Thermos Configuration Reference*](/documentation/0.10.0/configuration-reference/#process-objects). ## Getting Your Code Into The Sandbox @@ -297,7 +297,7 @@ A basic Task definition looks like: ram = 1*GB, disk = 1*GB)) -A Task has optional attributes to customize its behaviour. Details can be found in the [*Aurora+Thermos Configuration Reference*](/documentation/0.10.0//) +A Task has optional attributes to customize its behaviour. Details can be found in the [*Aurora+Thermos Configuration Reference*](/documentation/0.10.0/configuration-reference/#task-object) ### SequentialTask: Running Processes in Parallel or Sequentially @@ -454,7 +454,7 @@ default. For these four parameters, a Jo task = foo_task) In addition to the required attributes, there are several optional -attributes. Details can be found in the [Aurora+Thermos Configuration Reference](/documentation/0.10.0//). +attributes. Details can be found in the [Aurora+Thermos Configuration Reference](/documentation/0.10.0/configuration-reference/#job-objects). ## The jobs List @@ -472,7 +472,7 @@ The `.aurora` file format is just Python `Process`, and other classes are defined by a templating library called *Pystachio*, a powerful tool for configuration specification and reuse. -[Aurora+Thermos Configuration Reference](/documentation/0.10.0//) +[Aurora+Thermos Configuration Reference](/documentation/0.10.0/configuration-reference/) has a full reference of all Aurora/Thermos defined Pystachio objects. When writing your `.aurora` file, you may use any Pystachio datatypes, as Modified: aurora/site/source/documentation/0.10.0/cron-jobs.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.10.0/cron-jobs.md?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/source/documentation/0.10.0/cron-jobs.md (original) +++ aurora/site/source/documentation/0.10.0/cron-jobs.md Sun Dec 13 00:49:43 2015 @@ -22,11 +22,11 @@ Aurora supports execution of scheduled j A job is identified as a cron job by the presence of a `cron_schedule` attribute containing a cron-style schedule in the -[`Job`](/documentation/0.10.0//) object. Examples of cron schedules +[`Job`](/documentation/0.10.0/configuration-reference/#job-objects) object. Examples of cron schedules include "every 5 minutes" (`*/5 * * * *`), "Fridays at 17:00" (`* 17 * * FRI`), and "the 1st and 15th day of the month at 03:00" (`0 3 1,15 *`). -Example (available in the [Vagrant environment](/documentation/0.10.0//)): +Example (available in the [Vagrant environment](/documentation/0.10.0/vagrant/)): $ cat /vagrant/examples/job/cron_hello_world.aurora # cron_hello_world.aurora @@ -67,7 +67,7 @@ grow faster than they can process it. Unlike with services, which aurora will always re-execute regardless of exit status, instances of cron jobs retry according to the `max_task_failures` attribute of the -[Task](/documentation/0.10.0//) object. To get "run-until-success" semantics, +[Task](/documentation/0.10.0/configuration-reference/#task-objects) object. To get "run-until-success" semantics, set `max_task_failures` to `-1`. ## Interacting with cron jobs via the Aurora CLI Modified: aurora/site/source/documentation/0.10.0/deploying-aurora-scheduler.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.10.0/deploying-aurora-scheduler.md?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/source/documentation/0.10.0/deploying-aurora-scheduler.md (original) +++ aurora/site/source/documentation/0.10.0/deploying-aurora-scheduler.md Sun Dec 13 00:49:43 2015 @@ -117,7 +117,7 @@ should be set to `2`, and in a cluster o *Incorrectly setting this flag will cause data corruption to occur!* -See [this document](/documentation/0.10.0//) for more replicated +See [this document](/documentation/0.10.0/storage-config/#scheduler-storage-configuration-flags) for more replicated log and storage configuration options. ## Initializing the Replicated Log @@ -132,7 +132,7 @@ Failing to do this will result the follo ### Storage Performance Considerations -See [this document](/documentation/0.10.0//) for scheduler storage performance considerations. +See [this document](/documentation/0.10.0/scheduler-storage/) for scheduler storage performance considerations. ### Network considerations The Aurora scheduler listens on 2 ports - an HTTP port used for client RPCs and a web UI, @@ -189,12 +189,12 @@ assuming you set `-http_port=8081`. ## Security Considerations -See [security.md](/documentation/0.10.0//). +See [security.md](/documentation/0.10.0/security/). ## Configuring Resource Oversubscription **WARNING**: This feature is currently in alpha status. Do not use it in production clusters! -See [this document](/documentation/0.10.0//) for more feature details. +See [this document](/documentation/0.10.0/configuration-reference/#revocable-jobs) for more feature details. Set these scheduler flag to allow receiving revocable Mesos offers: @@ -209,7 +209,7 @@ Example [tier configuration file](https: ### Maintaining an Aurora Installation ### Monitoring -Please see our dedicated [monitoring guide](/documentation/0.10.0//) for in-depth discussion on monitoring. +Please see our dedicated [monitoring guide](/documentation/0.10.0/monitoring/) for in-depth discussion on monitoring. ### Running stateful services Aurora is best suited to run stateless applications, but it also accommodates for stateful services @@ -220,12 +220,12 @@ The Mesos slave has the `--attributes` c static attributes (not to be confused with `--resources`, which are dynamic and accounted). Aurora makes these attributes available for matching with scheduling -[constraints](/documentation/0.10.0//). Most of these +[constraints](/documentation/0.10.0/configuration-reference/#specifying-scheduling-constraints). Most of these constraints are arbitrary and available for custom use. There is one exception, though: the `dedicated` attribute. Aurora treats this specially, and only allows matching jobs to run on these machines, and will only schedule matching jobs on these machines. -See the [section](/documentation/0.10.0//) about resource quotas to learn how quotas apply to +See the [section](/documentation/0.10.0/resources/#resource-quota) about resource quotas to learn how quotas apply to dedicated jobs. ##### Syntax @@ -264,7 +264,7 @@ the mesos-slave with them as When it comes time to schedule jobs, Aurora will automatically spread them across the failure domains as specified in the -[job configuration](/documentation/0.10.0//). +[job configuration](/documentation/0.10.0/configuration-reference/#specifying-scheduling-constraints). Note: in virtualized environments like EC2, the only attribute that usually makes sense for this purpose is `host`. @@ -315,7 +315,7 @@ Since Aurora uses a Mesos replicated log [changing the mesos quorum size](http://mesos.apache.org/documentation/latest/operational-guide). ### Preparation -Increase [-native_log_quorum_size](/documentation/0.10.0//) on each +Increase [-native_log_quorum_size](/documentation/0.10.0/storage-config/#-native_log_quorum_size) on each existing scheduler and restart them. When updating from 3 to 5 schedulers, the quorum size would grow from 2 to 3. @@ -323,4 +323,4 @@ would grow from 2 to 3. Start the new schedulers with `-native_log_quorum_size` set to the new value. Failing to first increase the quorum size on running schedulers can in some cases result in corruption or truncating of the replicated log used by Aurora. In that case, see the documentation on -[recovering from backup](/documentation/0.10.0//). +[recovering from backup](/documentation/0.10.0/storage-config/#recovering-from-a-scheduler-backup). Modified: aurora/site/source/documentation/0.10.0/developing-aurora-client.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.10.0/developing-aurora-client.md?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/source/documentation/0.10.0/developing-aurora-client.md (original) +++ aurora/site/source/documentation/0.10.0/developing-aurora-client.md Sun Dec 13 00:49:43 2015 @@ -9,9 +9,9 @@ Client Configuration The client uses a configuration file that specifies available clusters. More information about the contents of this file can be found in the -[Client Cluster Configuration](/documentation/0.10.0//) documentation. Information about +[Client Cluster Configuration](/documentation/0.10.0/client-cluster-configuration/) documentation. Information about how the client locates this file can be found in the -[Client Commands](/documentation/0.10.0//) documentation. +[Client Commands](/documentation/0.10.0/client-commands/#cluster-configuration) documentation. Building and Testing the Client =============================== @@ -88,4 +88,4 @@ a Run configuration: Making thrift schema changes ============================ -See [this document](/documentation/0.10.0//) for any thrift related changes. +See [this document](/documentation/0.10.0/thrift-deprecation/) for any thrift related changes. Modified: aurora/site/source/documentation/0.10.0/developing-aurora-scheduler.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.10.0/developing-aurora-scheduler.md?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/source/documentation/0.10.0/developing-aurora-scheduler.md (original) +++ aurora/site/source/documentation/0.10.0/developing-aurora-scheduler.md Sun Dec 13 00:49:43 2015 @@ -128,4 +128,4 @@ repository root and commit the changed f Making thrift schema changes ============================ -See [this document](/documentation/0.10.0//) for any thrift related changes. +See [this document](/documentation/0.10.0/thrift-deprecation/) for any thrift related changes. Modified: aurora/site/source/documentation/0.10.0/index.html.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.10.0/index.html.md?rev=1719756&r1=1719755&r2=1719756&view=diff ============================================================================== --- aurora/site/source/documentation/0.10.0/index.html.md (original) +++ aurora/site/source/documentation/0.10.0/index.html.md Sun Dec 13 00:49:43 2015 @@ -8,30 +8,30 @@ Apache Aurora is a service scheduler tha We encourage you to ask questions on the [Aurora developer list](http://aurora.apache.org/community/) or the `#aurora` IRC channel on `irc.freenode.net`. ## Users - * [Install Aurora on virtual machines on your private machine](/documentation/0.10.0//) - * [Hello World Tutorial](/documentation/0.10.0//) - * [User Guide](/documentation/0.10.0//) - * [Configuration Tutorial](/documentation/0.10.0//) - * [Aurora + Thermos Reference](/documentation/0.10.0//) - * [Command Line Client](/documentation/0.10.0//) - * [Cron Jobs](/documentation/0.10.0//) + * [Install Aurora on virtual machines on your private machine](/documentation/0.10.0/vagrant/) + * [Hello World Tutorial](/documentation/0.10.0/tutorial/) + * [User Guide](/documentation/0.10.0/user-guide/) + * [Configuration Tutorial](/documentation/0.10.0/configuration-tutorial/) + * [Aurora + Thermos Reference](/documentation/0.10.0/configuration-reference/) + * [Command Line Client](/documentation/0.10.0/client-commands/) + * [Cron Jobs](/documentation/0.10.0/cron-jobs/) ## Operators - * [Deploy Aurora](/documentation/0.10.0//) - * [Monitoring](/documentation/0.10.0//) - * [Hooks for Aurora Client API](/documentation/0.10.0//) - * [Scheduler Storage](/documentation/0.10.0//) - * [Scheduler Storage and Maintenance](/documentation/0.10.0//) - * [SLA Measurement](/documentation/0.10.0//) - * [Resource Isolation and Sizing](/documentation/0.10.0//) - * [Generating test resources](/documentation/0.10.0//) + * [Deploy Aurora](/documentation/0.10.0/deploying-aurora-scheduler/) + * [Monitoring](/documentation/0.10.0/monitoring/) + * [Hooks for Aurora Client API](/documentation/0.10.0/hooks/) + * [Scheduler Storage](/documentation/0.10.0/storage/) + * [Scheduler Storage and Maintenance](/documentation/0.10.0/storage-config/) + * [SLA Measurement](/documentation/0.10.0/sla/) + * [Resource Isolation and Sizing](/documentation/0.10.0/resources/) + * [Generating test resources](/documentation/0.10.0/test-resource-generation/) ## Developers * [Contributing to the project](contributing/) - * [Developing the Aurora Scheduler](/documentation/0.10.0//) - * [Developing the Aurora Client](/documentation/0.10.0//) - * [Committers Guide](/documentation/0.10.0//) - * [Build System](/documentation/0.10.0//) + * [Developing the Aurora Scheduler](/documentation/0.10.0/developing-aurora-scheduler/) + * [Developing the Aurora Client](/documentation/0.10.0/developing-aurora-client/) + * [Committers Guide](/documentation/0.10.0/committers/) + * [Build System](/documentation/0.10.0/build-system/) ## Additional Resources - * [Presentation videos and slides](/documentation/0.10.0//) + * [Presentation videos and slides](/documentation/0.10.0/presentations/)
