Author: wfarner
Date: Thu Apr 21 15:07:18 2016
New Revision: 1740340
URL: http://svn.apache.org/viewvc?rev=1740340&view=rev
Log:
Generate 0.13.0 documentation under the 0.13.0 tag in addition to latest.
Added:
aurora/site/publish/documentation/0.13.0/contributing/
aurora/site/publish/documentation/0.13.0/contributing/index.html
aurora/site/source/documentation/0.13.0/contributing.md
Modified:
aurora/site/publish/documentation/0.13.0/additional-resources/tools/index.html
aurora/site/publish/documentation/0.13.0/development/db-migration/index.html
aurora/site/publish/documentation/0.13.0/development/design-documents/index.html
aurora/site/publish/documentation/0.13.0/development/thermos/index.html
aurora/site/publish/documentation/0.13.0/development/thrift/index.html
aurora/site/publish/documentation/0.13.0/features/constraints/index.html
aurora/site/publish/documentation/0.13.0/features/containers/index.html
aurora/site/publish/documentation/0.13.0/features/cron-jobs/index.html
aurora/site/publish/documentation/0.13.0/features/job-updates/index.html
aurora/site/publish/documentation/0.13.0/features/multitenancy/index.html
aurora/site/publish/documentation/0.13.0/features/resource-isolation/index.html
aurora/site/publish/documentation/0.13.0/features/service-discovery/index.html
aurora/site/publish/documentation/0.13.0/features/services/index.html
aurora/site/publish/documentation/0.13.0/features/sla-metrics/index.html
aurora/site/publish/documentation/0.13.0/getting-started/overview/index.html
aurora/site/publish/documentation/0.13.0/getting-started/tutorial/index.html
aurora/site/publish/documentation/0.13.0/getting-started/vagrant/index.html
aurora/site/publish/documentation/0.13.0/index.html
aurora/site/publish/documentation/0.13.0/operations/backup-restore/index.html
aurora/site/publish/documentation/0.13.0/operations/configuration/index.html
aurora/site/publish/documentation/0.13.0/operations/installation/index.html
aurora/site/publish/documentation/0.13.0/operations/storage/index.html
aurora/site/publish/documentation/0.13.0/reference/client-cluster-configuration/index.html
aurora/site/publish/documentation/0.13.0/reference/client-commands/index.html
aurora/site/publish/documentation/0.13.0/reference/configuration-best-practices/index.html
aurora/site/publish/documentation/0.13.0/reference/configuration-templating/index.html
aurora/site/publish/documentation/0.13.0/reference/configuration-tutorial/index.html
aurora/site/publish/documentation/0.13.0/reference/configuration/index.html
aurora/site/publish/documentation/0.13.0/reference/scheduler-configuration/index.html
aurora/site/publish/sitemap.xml
aurora/site/source/documentation/0.13.0/additional-resources/tools.md
aurora/site/source/documentation/0.13.0/development/db-migration.md
aurora/site/source/documentation/0.13.0/development/design-documents.md
aurora/site/source/documentation/0.13.0/development/thermos.md
aurora/site/source/documentation/0.13.0/development/thrift.md
aurora/site/source/documentation/0.13.0/features/constraints.md
aurora/site/source/documentation/0.13.0/features/containers.md
aurora/site/source/documentation/0.13.0/features/cron-jobs.md
aurora/site/source/documentation/0.13.0/features/job-updates.md
aurora/site/source/documentation/0.13.0/features/multitenancy.md
aurora/site/source/documentation/0.13.0/features/resource-isolation.md
aurora/site/source/documentation/0.13.0/features/service-discovery.md
aurora/site/source/documentation/0.13.0/features/services.md
aurora/site/source/documentation/0.13.0/features/sla-metrics.md
aurora/site/source/documentation/0.13.0/getting-started/overview.md
aurora/site/source/documentation/0.13.0/getting-started/tutorial.md
aurora/site/source/documentation/0.13.0/getting-started/vagrant.md
aurora/site/source/documentation/0.13.0/index.html.md
aurora/site/source/documentation/0.13.0/operations/backup-restore.md
aurora/site/source/documentation/0.13.0/operations/configuration.md
aurora/site/source/documentation/0.13.0/operations/installation.md
aurora/site/source/documentation/0.13.0/operations/storage.md
aurora/site/source/documentation/0.13.0/reference/client-cluster-configuration.md
aurora/site/source/documentation/0.13.0/reference/client-commands.md
aurora/site/source/documentation/0.13.0/reference/configuration-best-practices.md
aurora/site/source/documentation/0.13.0/reference/configuration-templating.md
aurora/site/source/documentation/0.13.0/reference/configuration-tutorial.md
aurora/site/source/documentation/0.13.0/reference/configuration.md
aurora/site/source/documentation/0.13.0/reference/scheduler-configuration.md
Modified:
aurora/site/publish/documentation/0.13.0/additional-resources/tools/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/additional-resources/tools/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/additional-resources/tools/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/additional-resources/tools/index.html
Thu Apr 21 15:07:18 2016
@@ -92,7 +92,7 @@
<li><a href="https://github.com/tellapart/aurproxy";>aurproxy</a> based on
nginx</li>
<li><a href="https://github.com/benley/aurora-jobhopper";>jobhopper</a>
performs HTTP redirects for easy developer and administrator access</li>
</ul></li>
-<li><p>RPC libraries that integrate with the Aurora’s <a
href="../features/service-discovery.md">service discovery mechanism</a>:</p>
+<li><p>RPC libraries that integrate with the Aurora’s <a
href="../../features/service-discovery/">service discovery mechanism</a>:</p>
<ul>
<li><a href="https://linkerd.io/";>linkerd</a> RPC proxy</li>
Added: aurora/site/publish/documentation/0.13.0/contributing/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/contributing/index.html?rev=1740340&view=auto
==============================================================================
--- aurora/site/publish/documentation/0.13.0/contributing/index.html (added)
+++ aurora/site/publish/documentation/0.13.0/contributing/index.html Thu Apr 21
15:07:18 2016
@@ -0,0 +1,209 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <title>Apache Aurora</title>
+ <link rel="stylesheet"
href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css";>
+ <link href="/assets/css/main.css" rel="stylesheet">
+ <!-- Analytics -->
+ <script type="text/javascript">
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-45879646-1']);
+ _gaq.push(['_setDomainName', 'apache.org']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type =
'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ?
'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(ga, s);
+ })();
+ </script>
+ </head>
+ <body>
+ <div class="container-fluid section-header">
+ <div class="container">
+ <div class="nav nav-bar">
+ <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300"
alt="Transparent Apache Aurora logo with dark background"/></a>
+ <ul class="nav navbar-nav navbar-right">
+ <li><a href="/documentation/latest/">Documentation</a></li>
+ <li><a href="/community/">Community</a></li>
+ <li><a href="/downloads/">Downloads</a></li>
+ <li><a href="/blog/">Blog</a></li>
+ </ul>
+ </div>
+ </div>
+</div>
+
+ <div class="container-fluid">
+ <div class="container content">
+ <div class="col-md-12 documentation">
+<h5 class="page-header text-uppercase">Documentation
+<select onChange="window.location.href='/documentation/' + this.value +
'/contributing/'"
+ value="0.13.0">
+ <option value="0.13.0"
+ selected="selected">
+ 0.13.0
+ (latest)
+ </option>
+ <option value="0.12.0"
+ >
+ 0.12.0
+ </option>
+ <option value="0.11.0"
+ >
+ 0.11.0
+ </option>
+ <option value="0.10.0"
+ >
+ 0.10.0
+ </option>
+ <option value="0.9.0"
+ >
+ 0.9.0
+ </option>
+ <option value="0.8.0"
+ >
+ 0.8.0
+ </option>
+ <option value="0.7.0-incubating"
+ >
+ 0.7.0-incubating
+ </option>
+ <option value="0.6.0-incubating"
+ >
+ 0.6.0-incubating
+ </option>
+ <option value="0.5.0-incubating"
+ >
+ 0.5.0-incubating
+ </option>
+</select>
+</h5>
+<h2 id="get-the-source-code">Get the Source Code</h2>
+
+<p>First things first, you’ll need the source! The Aurora source is
available from Apache git:</p>
+<pre class="highlight plaintext"><code>git clone
https://git-wip-us.apache.org/repos/asf/aurora
+</code></pre>
+
+<h2 id="read-the-style-guides">Read the Style Guides</h2>
+
+<p>Aurora’s codebase is primarily Java and Python and conforms to the
Twitter Commons styleguides for
+both languages.</p>
+
+<ul>
+<li><a
href="https://github.com/twitter/commons/blob/master/src/java/com/twitter/common/styleguide.md";>Java
Style Guide</a></li>
+<li><a
href="https://github.com/twitter/commons/blob/master/src/python/twitter/common/styleguide.md";>Python
Style Guide</a></li>
+</ul>
+
+<h2 id="find-something-to-do">Find Something to Do</h2>
+
+<p>There are issues in <a
href="https://issues.apache.org/jira/browse/AURORA";>Jira</a> with the
+<a
href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20AURORA%20AND%20labels%20%3D%20newbie%20and%20resolution%3Dunresolved";>“newbie”
label</a>
+that are good starting places for new Aurora contributors; pick one of these
and dive in! Once
+you’ve got a patch, the next step is to post a review.</p>
+
+<h2 id="getting-your-reviewboard-account">Getting your ReviewBoard Account</h2>
+
+<p>Go to <a href="https://reviews.apache.org";>https://reviews.apache.org</a>
and create an account.</p>
+
+<h2 id="setting-up-your-reviewboard-environment">Setting up your ReviewBoard
Environment</h2>
+
+<p>Run <code>./rbt status</code>. The first time this runs it will bootstrap
and you will be asked to login.
+Subsequent runs will cache your login credentials.</p>
+
+<h2 id="submitting-a-patch-for-review">Submitting a Patch for Review</h2>
+
+<p>Post a review with <code>rbt</code>, fill out the fields in your browser
and hit Publish.</p>
+<pre class="highlight plaintext"><code>./rbt post -o
+</code></pre>
+
+<p>If you’re unsure about who to add as a reviewer, you can default to
adding Bill Farner (wfarner) and
+Joshua Cohen (jcohen). They will take care of finding an appropriate reviewer
for the patch.</p>
+
+<p>Once you’ve done this, you probably want to mark the associated Jira
issue as Reviewable.</p>
+
+<h2 id="updating-an-existing-review">Updating an Existing Review</h2>
+
+<p>Incorporate review feedback, make some more commits, update your existing
review, fill out the
+fields in your browser and hit Publish.</p>
+<pre class="highlight plaintext"><code>./rbt post -o -r <RB_ID>
+</code></pre>
+
+<h2 id="getting-your-review-merged">Getting Your Review Merged</h2>
+
+<p>If you’re not an Aurora committer, one of the committers will merge
your change in as described
+below. Generally, the last reviewer to give the review a ‘Ship
It!’ will be responsible.</p>
+
+<h3 id="merging-your-own-review-committers">Merging Your Own Review
(Committers)</h3>
+
+<p>Once you have shipits from the right committers, merge your changes in a
single commit and mark
+the review as submitted. The typical workflow is:</p>
+<pre class="highlight plaintext"><code>git checkout master
+git pull origin master
+./rbt patch -c <RB_ID> # Verify the automatically-generated commit
message looks sane,
+ # editing if necessary.
+git show master # Verify everything looks sane
+git push origin master
+./rbt close <RB_ID>
+</code></pre>
+
+<p>Note that even if you’re developing using feature branches you will
not use <code>git merge</code> - each
+commit will be an atomic change accompanied by a ReviewBoard entry.</p>
+
+<h3 id="merging-someone-else-39-s-review">Merging Someone Else’s
Review</h3>
+
+<p>Sometimes you’ll need to merge someone else’s RB. The typical
workflow for this is</p>
+<pre class="highlight plaintext"><code>git checkout master
+git pull origin master
+./rbt patch -c <RB_ID>
+git show master # Verify everything looks sane, author is correct
+git push origin master
+</code></pre>
+
+<p>Note for committers: while we generally use the commit message generated by
<code>./rbt patch</code> some
+changes are often required:</p>
+
+<ol>
+<li>Ensure the the commit message does not exceed 100 characters per line.</li>
+<li>Remove the “Testing Done” section. It’s generally
redundant (can be seen by checking the linked
+review) or entirely irrelevant to the commit itself.</li>
+</ol>
+
+<h2 id="cleaning-up">Cleaning Up</h2>
+
+<p>Your patch has landed, congratulations! The last thing you’ll want to
do before moving on to your
+next fix is to clean up your Jira and Reviewboard. The former of which should
be marked as
+“Resolved” while the latter should be marked as
“Submitted”.</p>
+
+</div>
+
+ </div>
+ </div>
+ <div class="container-fluid section-footer buffer">
+ <div class="container">
+ <div class="row">
+ <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
+ <ul>
+ <li><a href="/downloads/">Downloads</a></li>
+ <li><a href="/community/">Mailing Lists</a></li>
+ <li><a
href="http://issues.apache.org/jira/browse/AURORA";>Issue Tracking</a></li>
+ <li><a href="/documentation/latest/contributing/">How
To Contribute</a></li>
+ </ul>
+ </div>
+ <div class="col-md-2"><h3>The ASF</h3>
+ <ul>
+ <li><a href="http://www.apache.org/licenses/";>License</a></li>
+ <li><a
href="http://www.apache.org/foundation/sponsorship.html";>Sponsorship</a></li>
+ <li><a
href="http://www.apache.org/foundation/thanks.html";>Thanks</a></li>
+ <li><a href="http://www.apache.org/security/";>Security</a></li>
+ </ul>
+ </div>
+ <div class="col-md-6">
+ <p class="disclaimer">Copyright 2014 <a
href="http://www.apache.org/";>Apache Software Foundation</a>. Licensed under
the <a href="http://www.apache.org/licenses/";>Apache License v2.0</a>. The <a
href="https://www.flickr.com/photos/trondk/12706051375/";>Aurora Borealis IX
photo</a> displayed on the homepage is available under a <a
href="https://creativecommons.org/licenses/by-nc-nd/2.0/";>Creative Commons
BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo
are trademarks of The Apache Software Foundation.</p>
+ </div>
+ </div>
+ </div>
+
+ </body>
+</html>
Modified:
aurora/site/publish/documentation/0.13.0/development/db-migration/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/development/db-migration/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/development/db-migration/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/development/db-migration/index.html
Thu Apr 21 15:07:18 2016
@@ -94,7 +94,7 @@ a snapshot is restored, no manual intera
<p>When adding or altering tables or changing data, a new migration class
should be created under the
org.apache.aurora.scheduler.storage.db.migration package. The class should
implement the
<a
href="https://github.com/mybatis/migrations/blob/master/src/main/java/org/apache/ibatis/migration/MigrationScript.java";>MigrationScript</a>
-interface (see <a
href="../../src/test/java/org/apache/aurora/scheduler/storage/db/testmigration/V001_TestMigration.java">V001_TestMigration</a>
+interface (see <a
href="https://github.com/apache/aurora/blob/rel/0.13.0/src/test/java/org/apache/aurora/scheduler/storage/db/testmigration/V001_TestMigration.java";>V001_TestMigration</a>
as an example). The upgrade and downgrade scripts are defined in this class.
When restoring a
snapshot the list of migrations on the classpath is compared to the list of
applied changes in the
DB. Any changes that have not yet been applied are executed and their
downgrade script is stored
Modified:
aurora/site/publish/documentation/0.13.0/development/design-documents/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/development/design-documents/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/development/design-documents/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/development/design-documents/index.html
Thu Apr 21 15:07:18 2016
@@ -90,7 +90,7 @@ in the proposed form.</p>
<p>Current and past documents:</p>
<ul>
-<li><a href="design/command-hooks.md">Command Hooks for the Aurora
Client</a></li>
+<li><a href="../design/command-hooks/">Command Hooks for the Aurora
Client</a></li>
<li><a
href="https://docs.google.com/document/d/1ZdgW8S4xMhvKW7iQUX99xZm10NXSxEWR0a-21FP5d94/edit";>Health
Checks for Updates</a></li>
<li><a
href="https://docs.google.com/document/d/1Fc_YhhV7fc4D9Xv6gJzpfooxbK4YWZcvzw6Bd3qVTL8/edit";>JobUpdateDiff
thrift API</a></li>
<li><a
href="https://docs.google.com/document/d/11_lAsYIRlD5ETRzF2eSd3oa8LXAHYFD8rSetspYXaf4/edit";>REST
API RFC</a></li>
Modified:
aurora/site/publish/documentation/0.13.0/development/thermos/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/development/thermos/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/development/thermos/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/development/thermos/index.html Thu
Apr 21 15:07:18 2016
@@ -196,7 +196,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="../reference/configuration.md">job configuration</a> that exercises
the feature, and
+<a href="../../reference/configuration/">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.13.0/development/thrift/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/development/thrift/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/development/thrift/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/development/thrift/index.html Thu
Apr 21 15:07:18 2016
@@ -87,7 +87,7 @@ client/server RPC protocol as well as fo
correctly handling additions and renames of the existing members, field
removals must be done
carefully to ensure backwards compatibility and provide predictable
deprecation cycle. This
document describes general guidelines for making Thrift schema changes to the
existing fields in
-<a
href="../../api/src/main/thrift/org/apache/aurora/gen/api.thrift">api.thrift</a>.</p>
+<a
href="https://github.com/apache/aurora/blob/rel/0.13.0/api/src/main/thrift/org/apache/aurora/gen/api.thrift";>api.thrift</a>.</p>
<p>It is highly recommended to go through the
<a href="http://diwakergupta.github.io/thrift-missing-guide/";>Thrift: The
Missing Guide</a> first to refresh on
@@ -115,9 +115,9 @@ communicate with scheduler/client from v
* Add a new field as an eventual replacement of the old one and implement a
dual read/write
anywhere the old field is used. If a thrift struct is mapped in the DB store
make sure both columns
are marked as <code>NOT NULL</code>
-* Check <a
href="../../api/src/main/thrift/org/apache/aurora/gen/storage.thrift">storage.thrift</a>
to see if
+* Check <a
href="https://github.com/apache/aurora/blob/rel/0.13.0/api/src/main/thrift/org/apache/aurora/gen/storage.thrift";>storage.thrift</a>
to see if
the affected struct is stored in Aurora scheduler storage. If so, it’s
almost certainly also
-necessary to perform a <a href="db-migration.md">DB migration</a>.
+necessary to perform a <a href="../db-migration/">DB migration</a>.
* Add a deprecation jira ticket into the vCurrent+1 release candidate
* Add a TODO for the deprecated field mentioning the jira ticket</p>
@@ -132,7 +132,7 @@ necessary to perform a <a href="db-migra
<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="../getting-started/vagrant.md">this document</a>
+client/scheduler versions by playing with <code>aurorabuild</code> command.
See <a href="../../getting-started/vagrant/">this document</a>
for more.</p>
</div>
Modified:
aurora/site/publish/documentation/0.13.0/features/constraints/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/constraints/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/features/constraints/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/features/constraints/index.html
Thu Apr 21 15:07:18 2016
@@ -126,7 +126,7 @@ most one task per rack:</p>
<p>Use these constraints sparingly as they can dramatically reduce
Tasks’ schedulability.
Further details are available in the reference documentation on
-<a
href="../reference/configuration.md#specifying-scheduling-constraints">Scheduling
Constraints</a>.</p>
+<a
href="../../reference/configuration/#specifying-scheduling-constraints">Scheduling
Constraints</a>.</p>
<h2 id="value-constraints">Value Constraints</h2>
@@ -144,7 +144,7 @@ scheduled on nodes that claim to have an
</code></pre>
<p>Further details are available in the reference documentation on
-<a
href="../reference/configuration.md#specifying-scheduling-constraints">Scheduling
Constraints</a>.</p>
+<a
href="../../reference/configuration/#specifying-scheduling-constraints">Scheduling
Constraints</a>.</p>
<h2 id="running-stateful-services">Running stateful services</h2>
Modified:
aurora/site/publish/documentation/0.13.0/features/containers/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/containers/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/features/containers/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/features/containers/index.html Thu
Apr 21 15:07:18 2016
@@ -84,9 +84,9 @@
<h2 id="docker">Docker</h2>
-<p>Aurora has optional support for launching Docker containers, if correctly
<a href="../operations/configuration.md#docker-containers">configured by an
Operator</a>.</p>
+<p>Aurora has optional support for launching Docker containers, if correctly
<a href="../../operations/configuration/#docker-containers">configured by an
Operator</a>.</p>
-<p>Example (available in the <a href="../getting-started/vagrant.md">Vagrant
environment</a>):</p>
+<p>Example (available in the <a href="../../getting-started/vagrant/">Vagrant
environment</a>):</p>
<pre class="highlight plaintext"><code>$ cat
/vagrant/examples/jobs/docker/hello_docker.aurora
hello_docker = Process(
name = 'hello',
@@ -117,7 +117,7 @@ jobs = [
<p>In order to correctly execute processes inside a job, the docker container
must have Python 2.7
installed. Further details of how to use Docker can be found in the
-<a href="../reference/configuration.md#docker-object">Reference
Documentation</a>.</p>
+<a href="../../reference/configuration/#docker-object">Reference
Documentation</a>.</p>
</div>
Modified: aurora/site/publish/documentation/0.13.0/features/cron-jobs/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/cron-jobs/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/features/cron-jobs/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/features/cron-jobs/index.html Thu
Apr 21 15:07:18 2016
@@ -110,11 +110,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="../reference/configuration.md#job-objects"><code>Job</code></a>
object. Examples of cron schedules
+<a href="../../reference/configuration/#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="../getting-started/vagrant.md">Vagrant
environment</a>):</p>
+<p>Example (available in the <a href="../../getting-started/vagrant/">Vagrant
environment</a>):</p>
<pre class="highlight plaintext"><code>$ cat
/vagrant/examples/jobs/cron_hello_world.aurora
# A cron job that runs every 5 minutes.
jobs = [
@@ -150,7 +150,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="../reference/configuration.md#task-object">Task</a> object. To get
“run-until-success” semantics,
+<a href="../../reference/configuration/#task-object">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.13.0/features/job-updates/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/job-updates/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/features/job-updates/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/features/job-updates/index.html
Thu Apr 21 15:07:18 2016
@@ -141,7 +141,7 @@ from the point where the update failed.
8-FAIL) results in a rollback in order (8,7,6) (5,4,3) (2,1,0).</p>
<p>For details how to control a job update, please see the
-<a href="../reference/configuration.md#updateconfig-objects">UpdateConfig</a>
configuration object.</p>
+<a href="../../reference/configuration/#updateconfig-objects">UpdateConfig</a>
configuration object.</p>
<h2 id="coordinated-job-updates">Coordinated Job Updates</h2>
@@ -150,10 +150,10 @@ acknowledging (“heartbeating&rdquo
service updates where explicit job health monitoring is vital during the
entire job update
lifecycle. Such job updates would rely on an external service (or a custom
client) periodically
pulsing an active coordinated job update via a
-<a
href="../../api/src/main/thrift/org/apache/aurora/gen/api.thrift">pulseJobUpdate
RPC</a>.</p>
+<a
href="https://github.com/apache/aurora/blob/rel/0.13.0/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="../reference/configuration.md#updateconfig-objects">pulse<em>interval</em>secs</a>
value in job configuration
+<a
href="../../reference/configuration/#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>
Modified:
aurora/site/publish/documentation/0.13.0/features/multitenancy/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/multitenancy/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/features/multitenancy/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/features/multitenancy/index.html
Thu Apr 21 15:07:18 2016
@@ -83,7 +83,7 @@
<h1 id="multitenancy">Multitenancy</h1>
<p>Aurora is a multi-tenant system that can run jobs of multiple
clients/tenants.
-Going beyond the <a href="resource-isolation.md">resource isolation on an
individual host</a>, it is
+Going beyond the <a href="../resource-isolation/">resource isolation on an
individual host</a>, it is
crucial to prevent those jobs from stepping on each others toes.</p>
<h2 id="job-namespaces">Job Namespaces</h2>
@@ -100,7 +100,7 @@ to differentiate between different jobs.
</ul>
<p>Role names correspond to user accounts. They are used for
-<a href="../operations/security.md">authentication</a>, as the linux user used
to run jobs, and for the
+<a href="../../operations/security/">authentication</a>, as the linux user
used to run jobs, and for the
assignment of <a href="#preemption">quota</a>. If you don’t know what
accounts are available, contact your
sysadmin.</p>
@@ -124,20 +124,20 @@ prevents this. Active tasks can become t
<ul>
<li>both candidate and victim are owned by the same role and the
-<a href="../reference/configuration.md#job-objects">priority</a> of a victim
is lower than the
-<a href="../reference/configuration.md#job-objects">priority</a> of the
candidate.</li>
-<li>OR a victim is non-<a
href="../reference/configuration.md#job-objects">production</a> and the
candidate is
-<a href="../reference/configuration.md#job-objects">production</a>.</li>
+<a href="../../reference/configuration/#job-objects">priority</a> of a victim
is lower than the
+<a href="../../reference/configuration/#job-objects">priority</a> of the
candidate.</li>
+<li>OR a victim is non-<a
href="../../reference/configuration/#job-objects">production</a> and the
candidate is
+<a href="../../reference/configuration/#job-objects">production</a>.</li>
</ul>
-<p>In other words, tasks from <a
href="../reference/configuration.md#job-objects">production</a> jobs may preempt
+<p>In other words, tasks from <a
href="../../reference/configuration/#job-objects">production</a> jobs may
preempt
tasks from any non-production job. However, a production task may only be
preempted by tasks from
-production jobs in the same role with higher <a
href="../reference/configuration.md#job-objects">priority</a>.</p>
+production jobs in the same role with higher <a
href="../../reference/configuration/#job-objects">priority</a>.</p>
-<p>Aurora requires resource quotas for <a
href="../reference/configuration.md#job-objects">production non-dedicated
jobs</a>.
+<p>Aurora requires resource quotas for <a
href="../../reference/configuration/#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. All job types (service, adhoc or cron) require role resource quota
unless a job has
-<a href="constraints.md#dedicated-attribute">dedicated constraint set</a>.</p>
+<a href="../constraints/#dedicated-attribute">dedicated constraint set</a>.</p>
<p>To grant quota to a particular role in production, an operator can use the
command
<code>aurora_admin set_quota</code>.</p>
Modified:
aurora/site/publish/documentation/0.13.0/features/resource-isolation/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/resource-isolation/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/features/resource-isolation/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/features/resource-isolation/index.html
Thu Apr 21 15:07:18 2016
@@ -237,11 +237,11 @@ jobs. If not configured properly revocab
<pre class="highlight plaintext"><code>-receive_revocable_resources=true
</code></pre>
-<p>Specify a tier configuration file path (unless you want to use the <a
href="../../src/main/resources/org/apache/aurora/scheduler/tiers.json">default</a>):</p>
+<p>Specify a tier configuration file path (unless you want to use the <a
href="https://github.com/apache/aurora/blob/rel/0.13.0/src/main/resources/org/apache/aurora/scheduler/tiers.json";>default</a>):</p>
<pre class="highlight plaintext"><code>-tier_config=path/to/tiers/config.json
</code></pre>
-<p>See the <a href="../references/configuration.md">Configuration
Reference</a> for details on how to mark a job
+<p>See the <a href="../../references/configuration/">Configuration
Reference</a> for details on how to mark a job
as being revocable.</p>
</div>
Modified:
aurora/site/publish/documentation/0.13.0/features/service-discovery/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/service-discovery/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/features/service-discovery/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/features/service-discovery/index.html
Thu Apr 21 15:07:18 2016
@@ -94,7 +94,7 @@ 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="../reference/configuration.md">Configuration Reference</a>.</p>
+<p>For more information about how to configure announcing, see the <a
href="../../reference/configuration/">Configuration Reference</a>.</p>
<h2 id="using-mesos-discoveryinfo">Using Mesos DiscoveryInfo</h2>
Modified: aurora/site/publish/documentation/0.13.0/features/services/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/services/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/features/services/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/features/services/index.html Thu
Apr 21 15:07:18 2016
@@ -89,10 +89,10 @@ such as webservices that should always b
<h2 id="service-specification">Service Specification</h2>
<p>A job is identified as a service by the presence of the flag
-`<code>service=True</code> in the <a
href="../reference/configuration.md#job-objects"><code>Job</code></a> object.
+`<code>service=True</code> in the <a
href="../../reference/configuration/#job-objects"><code>Job</code></a> object.
The <code>Service</code> alias can be used as shorthand for <code>Job</code>
with <code>service=True</code>.</p>
-<p>Example (available in the <a href="../getting-started/vagrant.md">Vagrant
environment</a>):</p>
+<p>Example (available in the <a href="../../getting-started/vagrant/">Vagrant
environment</a>):</p>
<pre class="highlight plaintext"><code>$ cat
/vagrant/examples/jobs/hello_world.aurora
hello = Process(
name = 'hello',
@@ -121,12 +121,12 @@ jobs = [
<p>Jobs without the service bit set only restart up to
<code>max_task_failures</code> times and only if they
terminated unsuccessfully either due to human error or machine failure (see the
-<a href="../reference/configuration.md#job-objects"><code>Job</code></a>
object for details).</p>
+<a href="../../reference/configuration/#job-objects"><code>Job</code></a>
object for details).</p>
<h2 id="ports">Ports</h2>
<p>In order to be useful, most services have to bind to one or more ports.
Aurora enables this
-usecase via the <a
href="../reference/configuration.md#thermos-namespace"><code>thermos.ports</code>
namespace</a> that
+usecase via the <a
href="../../reference/configuration/#thermos-namespace"><code>thermos.ports</code>
namespace</a> that
allows to request arbitrarily named ports:</p>
<pre class="highlight plaintext"><code>nginx = Process(
name = 'nginx',
@@ -142,7 +142,7 @@ will be replaced with something like:</p
<p>Where 42816 happens to be the allocated port.</p>
<p>For details on how to enable clients to discover this dynamically assigned
port, see our
-<a href="service-discovery.md">Service Discovery</a> documentation.</p>
+<a href="../service-discovery/">Service Discovery</a> documentation.</p>
<h2 id="health-checking">Health Checking</h2>
@@ -159,7 +159,7 @@ via repeated calls to the <code>/health<
</code></pre>
<p>Please see the
-<a
href="../reference/configuration.md#user-content-healthcheckconfig-objects">configuration
reference</a>
+<a
href="../../reference/configuration/#healthcheckconfig-objects">configuration
reference</a>
for configuration options for this feature.</p>
<p>You can pause health checking by touching a file inside of your sandbox,
named <code>.healthchecksnooze</code>.
Modified:
aurora/site/publish/documentation/0.13.0/features/sla-metrics/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/sla-metrics/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/features/sla-metrics/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/features/sla-metrics/index.html
Thu Apr 21 15:07:18 2016
@@ -149,7 +149,7 @@ relevant to uptime calculations. By appl
transition records, we can build a deterministic downtime trace for every
given service instance.</p>
<p>A task going through a state transition carries one of three possible SLA
meanings
-(see <a
href="../../src/main/java/org/apache/aurora/scheduler/sla/SlaAlgorithm.java">SlaAlgorithm.java</a>
for
+(see <a
href="https://github.com/apache/aurora/blob/rel/0.13.0/src/main/java/org/apache/aurora/scheduler/sla/SlaAlgorithm.java";>SlaAlgorithm.java</a>
for
sla-to-task-state mapping):</p>
<ul>
@@ -199,7 +199,7 @@ metric that helps track the dependency o
<li>Per job - <code>sla_<job_key>_mtta_ms</code></li>
<li>Per cluster - <code>sla_cluster_mtta_ms</code></li>
<li>Per instance size (small, medium, large, x-large, xx-large). Size are
defined in:
-<a
href="../../src/main/java/org/apache/aurora/scheduler/base/ResourceAggregates.java">ResourceAggregates.java</a>
+<a
href="https://github.com/apache/aurora/blob/rel/0.13.0/src/main/java/org/apache/aurora/scheduler/base/ResourceAggregates.java";>ResourceAggregates.java</a>
<ul>
<li>By CPU:</li>
@@ -240,7 +240,7 @@ reflecting on the overall time it takes
<li>Per job - <code>sla_<job_key>_mttr_ms</code></li>
<li>Per cluster - <code>sla_cluster_mttr_ms</code></li>
<li>Per instance size (small, medium, large, x-large, xx-large). Size are
defined in:
-<a
href="../../src/main/java/org/apache/aurora/scheduler/base/ResourceAggregates.java">ResourceAggregates.java</a>
+<a
href="https://github.com/apache/aurora/blob/rel/0.13.0/src/main/java/org/apache/aurora/scheduler/base/ResourceAggregates.java";>ResourceAggregates.java</a>
<ul>
<li>By CPU:</li>
Modified:
aurora/site/publish/documentation/0.13.0/getting-started/overview/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/getting-started/overview/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/getting-started/overview/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/getting-started/overview/index.html
Thu Apr 21 15:07:18 2016
@@ -120,7 +120,7 @@ directories.</p></li>
<li><p><strong>ZooKeeper</strong>
<a href="http://zookeeper.apache.org";>ZooKeeper</a> is a distributed consensus
system. In an Aurora cluster
it is used for reliable election of the leading Aurora scheduler and Mesos
master. It is also
-used as a vehicle for service discovery, see <a
href="../features/service-discovery.md">Service Discovery</a></p></li>
+used as a vehicle for service discovery, see <a
href="../../features/service-discovery/">Service Discovery</a></p></li>
<li><p><strong>Mesos master</strong>
The master is responsible for tracking worker machines and performing
accounting of their
resources. The scheduler interfaces with the master to control the
cluster.</p></li>
Modified:
aurora/site/publish/documentation/0.13.0/getting-started/tutorial/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/getting-started/tutorial/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/getting-started/tutorial/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/getting-started/tutorial/index.html
Thu Apr 21 15:07:18 2016
@@ -98,9 +98,9 @@ to start getting up to speed on the syst
<h2 id="prerequisite">Prerequisite</h2>
-<p>This tutorial assumes you are running <a href="vagrant.md">Aurora locally
using Vagrant</a>.
+<p>This tutorial assumes you are running <a href="../vagrant/">Aurora locally
using Vagrant</a>.
However, in general the instructions are also applicable to any other
-<a href="../operations/installation.md">Aurora installation</a>.</p>
+<a href="../../operations/installation/">Aurora installation</a>.</p>
<p>Unless otherwise stated, all commands are to be run from the root of the
aurora
repository clone.</p>
@@ -186,8 +186,8 @@ local sandbox in which it will run. It t
actually run once the second Process starts.</p></li>
</ol>
-<p>For more about Aurora configuration files, see the <a
href="../reference/configuration-tutorial.md">Configuration
-Tutorial</a> and the <a href="../reference/configuration.md">Configuration
+<p>For more about Aurora configuration files, see the <a
href="../../reference/configuration-tutorial/">Configuration
+Tutorial</a> and the <a href="../../reference/configuration/">Configuration
Reference</a> (preferably after finishing this
tutorial).</p>
@@ -214,7 +214,7 @@ don’t know what accounts are avail
its counterpart in the other key, then the two job keys identify two separate
jobs. If all four values are identical, the job keys identify the same job.</p>
-<p>The <code>clusters.json</code> <a
href="../reference/client-cluster-configuration.md">client configuration</a>
+<p>The <code>clusters.json</code> <a
href="../../reference/client-cluster-configuration/">client configuration</a>
for the Aurora scheduler defines the available cluster names.
For Vagrant, from the top-level of your Aurora repository clone, do:</p>
<pre class="highlight plaintext"><code>$ vagrant ssh
@@ -331,11 +331,11 @@ Job killall succeeded
<p>Now that you’ve finished this Tutorial, you should read or do the
following:</p>
<ul>
-<li><a href="../reference/configuration-tutorial.md">The Aurora Configuration
Tutorial</a>, which provides more examples
+<li><a href="../../reference/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="../reference/configuration.md">Aurora Configuration
Reference</a>.</li>
+the <a href="../../reference/configuration/">Aurora Configuration
Reference</a>.</li>
<li>Explore the Aurora Client - use <code>aurora -h</code>, and read the
-<a href="../reference/client-commands.md">Aurora Client Commands</a>
document.</li>
+<a href="../../reference/client-commands/">Aurora Client Commands</a>
document.</li>
</ul>
</div>
Modified:
aurora/site/publish/documentation/0.13.0/getting-started/vagrant/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/getting-started/vagrant/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/getting-started/vagrant/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/getting-started/vagrant/index.html
Thu Apr 21 15:07:18 2016
@@ -89,15 +89,15 @@ the steps outlined here, you will be rea
<p>The following sections describe these steps in detail:</p>
<ol>
-<li><a href="#user-content-overview">Overview</a></li>
-<li><a href="#user-content-install-virtualbox-and-vagrant">Install VirtualBox
and Vagrant</a></li>
-<li><a href="#user-content-clone-the-aurora-repository">Clone the Aurora
repository</a></li>
-<li><a href="#user-content-start-the-local-cluster">Start the local
cluster</a></li>
-<li><a href="#user-content-log-onto-the-vm">Log onto the VM</a></li>
-<li><a href="#user-content-run-your-first-job">Run your first job</a></li>
-<li><a href="#user-content-rebuild-components">Rebuild components</a></li>
-<li><a href="#user-content-shut-down-or-delete-your-local-cluster">Shut down
or delete your local cluster</a></li>
-<li><a href="#user-content-troubleshooting">Troubleshooting</a></li>
+<li><a href="#overview">Overview</a></li>
+<li><a href="#install-virtualbox-and-vagrant">Install VirtualBox and
Vagrant</a></li>
+<li><a href="#clone-the-aurora-repository">Clone the Aurora repository</a></li>
+<li><a href="#start-the-local-cluster">Start the local cluster</a></li>
+<li><a href="#log-onto-the-vm">Log onto the VM</a></li>
+<li><a href="#run-your-first-job">Run your first job</a></li>
+<li><a href="#rebuild-components">Rebuild components</a></li>
+<li><a href="#shut-down-or-delete-your-local-cluster">Shut down or delete your
local cluster</a></li>
+<li><a href="#troubleshooting">Troubleshooting</a></li>
</ol>
<h2 id="overview">Overview</h2>
@@ -175,7 +175,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="tutorial.md">Aurora Tutorial</a>.</p>
+For more information, see the <a href="../tutorial/">Aurora Tutorial</a>.</p>
<h2 id="rebuild-components">Rebuild components</h2>
Modified: aurora/site/publish/documentation/0.13.0/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/index.html Thu Apr 21 15:07:18 2016
@@ -94,9 +94,9 @@ the <code>#aurora</code> IRC channel on
<p>Information for everyone new to Apache Aurora.</p>
<ul>
-<li><a href="getting-started/overview.md">Aurora System Overview</a></li>
-<li><a href="getting-started/tutorial.md">Hello World Tutorial</a></li>
-<li><a href="getting-started/vagrant.md">Local cluster with Vagrant</a></li>
+<li><a href="getting-started/overview/">Aurora System Overview</a></li>
+<li><a href="getting-started/tutorial/">Hello World Tutorial</a></li>
+<li><a href="getting-started/vagrant/">Local cluster with Vagrant</a></li>
</ul>
<h2 id="features">Features</h2>
@@ -104,15 +104,15 @@ the <code>#aurora</code> IRC channel on
<p>Description of important Aurora features.</p>
<ul>
-<li><a href="features/containers.md">Containers</a></li>
-<li><a href="features/cron-jobs.md">Cron Jobs</a></li>
-<li><a href="features/job-updates.md">Job Updates</a></li>
-<li><a href="features/multitenancy.md">Multitenancy</a></li>
-<li><a href="features/resource-isolation.md">Resource Isolation</a></li>
-<li><a href="features/constraints.md">Scheduling Constraints</a></li>
-<li><a href="features/services.md">Services</a></li>
-<li><a href="features/service-discovery.md">Service Discovery</a></li>
-<li><a href="features/sla-metrics.md">SLA Metrics</a></li>
+<li><a href="features/containers/">Containers</a></li>
+<li><a href="features/cron-jobs/">Cron Jobs</a></li>
+<li><a href="features/job-updates/">Job Updates</a></li>
+<li><a href="features/multitenancy/">Multitenancy</a></li>
+<li><a href="features/resource-isolation/">Resource Isolation</a></li>
+<li><a href="features/constraints/">Scheduling Constraints</a></li>
+<li><a href="features/services/">Services</a></li>
+<li><a href="features/service-discovery/">Service Discovery</a></li>
+<li><a href="features/sla-metrics/">SLA Metrics</a></li>
</ul>
<h2 id="operators">Operators</h2>
@@ -120,12 +120,12 @@ the <code>#aurora</code> IRC channel on
<p>For those that wish to manage and fine-tune an Aurora cluster.</p>
<ul>
-<li><a href="operations/installation.md">Installation</a></li>
-<li><a href="operations/configuration.md">Configuration</a></li>
-<li><a href="operations/monitoring.md">Monitoring</a></li>
-<li><a href="operations/security.md">Security</a></li>
-<li><a href="operations/storage.md">Storage</a></li>
-<li><a href="operations/backup-restore.md">Backup</a></li>
+<li><a href="operations/installation/">Installation</a></li>
+<li><a href="operations/configuration/">Configuration</a></li>
+<li><a href="operations/monitoring/">Monitoring</a></li>
+<li><a href="operations/security/">Security</a></li>
+<li><a href="operations/storage/">Storage</a></li>
+<li><a href="operations/backup-restore/">Backup</a></li>
</ul>
<h2 id="reference">Reference</h2>
@@ -133,30 +133,30 @@ the <code>#aurora</code> IRC channel on
<p>The complete reference of commands, configuration options, and scheduler
internals.</p>
<ul>
-<li><a href="reference/task-lifecycle.md">Task lifecycle</a></li>
+<li><a href="reference/task-lifecycle/">Task lifecycle</a></li>
<li>Configuration (<code>.aurora</code> files)
<ul>
-<li><a href="reference/configuration.md">Configuration Reference</a></li>
-<li><a href="reference/configuration-tutorial.md">Configuration
Tutorial</a></li>
-<li><a href="reference/configuration-best-practices.md">Configuration Best
Practices</a></li>
-<li><a href="reference/configuration-templating.md">Configuration
Templating</a></li>
+<li><a href="reference/configuration/">Configuration Reference</a></li>
+<li><a href="reference/configuration-tutorial/">Configuration Tutorial</a></li>
+<li><a href="reference/configuration-best-practices/">Configuration Best
Practices</a></li>
+<li><a href="reference/configuration-templating/">Configuration
Templating</a></li>
</ul></li>
<li>Aurora Client
<ul>
-<li><a href="reference/client-commands.md">Client Commands</a></li>
-<li><a href="reference/client-hooks.md">Client Hooks</a></li>
-<li><a href="reference/client-cluster-configuration.md">Client Cluster
Configuration</a></li>
+<li><a href="reference/client-commands/">Client Commands</a></li>
+<li><a href="reference/client-hooks/">Client Hooks</a></li>
+<li><a href="reference/client-cluster-configuration/">Client Cluster
Configuration</a></li>
</ul></li>
-<li><a href="reference/scheduler-configuration.md">Scheduler
Configuration</a></li>
+<li><a href="reference/scheduler-configuration/">Scheduler
Configuration</a></li>
</ul>
<h2 id="additional-resources">Additional Resources</h2>
<ul>
-<li><a href="additional-resources/tools.md">Tools integrating with
Aurora</a></li>
-<li><a href="additional-resources/presentations.md">Presentation videos and
slides</a></li>
+<li><a href="additional-resources/tools/">Tools integrating with
Aurora</a></li>
+<li><a href="additional-resources/presentations/">Presentation videos and
slides</a></li>
</ul>
<h2 id="developers">Developers</h2>
@@ -165,16 +165,16 @@ the <code>#aurora</code> IRC channel on
<ul>
<li><a href="contributing/">Contributing to the project</a></li>
-<li><a href="development/committers-guide.md">Committer’s Guide</a></li>
-<li><a href="development/design-documents.md">Design Documents</a></li>
+<li><a href="development/committers-guide/">Committer’s Guide</a></li>
+<li><a href="development/design-documents/">Design Documents</a></li>
<li>Developing the Aurora components:
<ul>
-<li><a href="development/client.md">Client</a></li>
-<li><a href="development/scheduler.md">Scheduler</a></li>
-<li><a href="development/ui.md">Scheduler UI</a></li>
-<li><a href="development/thermos.md">Thermos</a></li>
-<li><a href="development/thrift.md">Thrift structures</a></li>
+<li><a href="development/client/">Client</a></li>
+<li><a href="development/scheduler/">Scheduler</a></li>
+<li><a href="development/ui/">Scheduler UI</a></li>
+<li><a href="development/thermos/">Thermos</a></li>
+<li><a href="development/thrift/">Thrift structures</a></li>
</ul></li>
</ul>
Modified:
aurora/site/publish/documentation/0.13.0/operations/backup-restore/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/operations/backup-restore/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/operations/backup-restore/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/operations/backup-restore/index.html
Thu Apr 21 15:07:18 2016
@@ -97,7 +97,7 @@ be killed shortly after the cluster rest
hours). This is because the scheduler will expect the cluster to look exactly
as the backup does,
so any tasks that have been rescheduled since the backup was taken will be
killed.</p>
-<p>Instructions below have been verified in <a
href="../getting-started/vagrant.md">Vagrant environment</a> and with minor
+<p>Instructions below have been verified in <a
href="../../getting-started/vagrant/">Vagrant environment</a> and with minor
syntax/path changes should be applicable to any Aurora cluster.</p>
<h1 id="preparation">Preparation</h1>
@@ -114,7 +114,7 @@ be erased after the backup snapshot is r
<a href="#restore-from-backup">Restore from backup</a> section locally on the
leading scheduler:</p>
<ul>
-<li>Make sure the <a
href="../reference/client-cluster-configuration.md">clusters.json</a> file
configured to
+<li>Make sure the <a
href="../../reference/client-cluster-configuration/">clusters.json</a> file
configured to
access scheduler directly. Set <code>scheduler_uri</code> setting and remove
<code>zk</code>. Since leader can get
re-elected during the restore steps, consider doing it on all scheduler
replicas.</li>
<li><p>Depending on your particular security approach you will need to either
turn off scheduler
Modified:
aurora/site/publish/documentation/0.13.0/operations/configuration/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/operations/configuration/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/operations/configuration/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/operations/configuration/index.html
Thu Apr 21 15:07:18 2016
@@ -84,7 +84,7 @@
<p>The Aurora scheduler can take a variety of configuration options through
command-line arguments.
Examples are available under <code>examples/scheduler/</code>. For a list of
available Aurora flags and their
-documentation, see <a href="../reference/scheduler-configuration.md">Scheduler
Configuration Reference</a>.</p>
+documentation, see <a
href="../../reference/scheduler-configuration/">Scheduler Configuration
Reference</a>.</p>
<h2 id="a-note-on-configuration">A Note on Configuration</h2>
@@ -170,7 +170,7 @@ for Mesos replicated log files to ensure
<p>ZooKeeper path used for Mesos replicated log quorum discovery.</p>
-<p>See <a
href="../../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.13.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>
@@ -185,7 +185,7 @@ When updating from 3 to 5 schedulers, th
<p>When starting the new schedulers, use the
<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="backup-restore.md">recovering from backup</a>.</p>
+<a href="../backup-restore/">recovering from backup</a>.</p>
<h2 id="backup-configuration">Backup Configuration</h2>
@@ -216,7 +216,7 @@ argument to the Aurora scheduler):</p>
<p><code>both</code> configuration will send logs to files and stream to
parent stdout/stderr outputs.</p>
-<p>See <a href="../reference/configuration.md#logger">Configuration
Reference</a> for all destination options.</p>
+<p>See <a href="../../reference/configuration/#logger">Configuration
Reference</a> for all destination options.</p>
<h3 id="log-rotation">Log rotation</h3>
Modified:
aurora/site/publish/documentation/0.13.0/operations/installation/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/operations/installation/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/operations/installation/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/operations/installation/index.html
Thu Apr 21 15:07:18 2016
@@ -323,7 +323,7 @@ brew install aurora-cli
them. By default this file is at <code>/etc/aurora/clusters.json</code>.</p>
<p>Jobs may be submitted to the scheduler using the client, and are described
with
-<a href="../reference/configuration.md">job configurations</a> expressed in
<code>.aurora</code> files. Typically you will
+<a href="../../reference/configuration/">job configurations</a> expressed in
<code>.aurora</code> files. Typically you will
maintain a single job configuration file to describe one or more deployment
environments (e.g.
dev, test, prod) for a production job.</p>
Modified: aurora/site/publish/documentation/0.13.0/operations/storage/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/operations/storage/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/operations/storage/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/operations/storage/index.html Thu
Apr 21 15:07:18 2016
@@ -126,7 +126,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="backup-restore.md">disaster recovery problem</a>
+This solves a <a href="../backup-restore/">disaster recovery problem</a>
in case of a complete loss or corruption of Mesos log files.</li>
</ul>
Modified:
aurora/site/publish/documentation/0.13.0/reference/client-cluster-configuration/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/client-cluster-configuration/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/reference/client-cluster-configuration/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/reference/client-cluster-configuration/index.html
Thu Apr 21 15:07:18 2016
@@ -211,7 +211,7 @@ URL of your VIP in a loadbalancer or a r
<p>The identifier of an authentication mechanism that the client should use
when communicating with the
scheduler. Support for values other than <code>UNAUTHENTICATED</code> requires
a matching scheduler-side
-<a href="../operations/security.md">security configuration</a>.</p>
+<a href="../../operations/security/">security configuration</a>.</p>
</div>
Modified:
aurora/site/publish/documentation/0.13.0/reference/client-commands/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/client-commands/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/reference/client-commands/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/reference/client-commands/index.html
Thu Apr 21 15:07:18 2016
@@ -97,7 +97,7 @@
<li><a href="#updating-a-job">Updating a Job</a>
<ul>
-<li><a href="#user-content-coordinated-job-updates">Coordinated job
updates</a></li>
+<li><a href="#coordinated-job-updates">Coordinated job updates</a></li>
</ul></li>
<li><a href="#renaming-a-job">Renaming a Job</a></li>
<li><a href="#restarting-jobs">Restarting Jobs</a></li>
@@ -154,7 +154,7 @@ environment variable is not set. The sec
<code>~/.aurora/clusters.json</code>.</p>
<p>For more details on cluster configuration see the
-<a href="client-cluster-configuration.md">Client Cluster Configuration</a>
documentation.</p>
+<a href="../client-cluster-configuration/">Client Cluster Configuration</a>
documentation.</p>
<h2 id="job-keys">Job Keys</h2>
@@ -198,7 +198,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="client-hooks.md">Hooks for
Aurora Client API</a>.</p>
+that we explain it in a devoted document, <a href="../client-hooks/">Hooks for
Aurora Client API</a>.</p>
<h2 id="regular-jobs">Regular Jobs</h2>
@@ -246,7 +246,7 @@ already exists. Use <code>aurora update
<h3 id="updating-a-job">Updating a Job</h3>
<p>You can manage job updates using the <code>aurora update</code> command.
Please see
-<a href="../features/job-updates.md">the Job Update documentation</a> for more
details.</p>
+<a href="../../features/job-updates/">the Job Update documentation</a> for
more details.</p>
<h3 id="renaming-a-job">Renaming a Job</h3>
@@ -298,7 +298,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="../features/cron-jobs.md">the Cron Jobs Feature</a> for more
details.</p>
+<a href="../../features/cron-jobs/">the Cron Jobs Feature</a> for more
details.</p>
<h2 id="comparing-jobs">Comparing Jobs</h2>
<pre class="highlight plaintext"><code>aurora job diff CLUSTER/ROLE/ENV/NAME
<job configuration>
@@ -331,8 +331,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="../features/constraints.md#dedicated-attribute">dedicated</a>
-<a href="configuration.md#job-objects">production</a> jobs consume quota.</p>
+cluster. Only non-<a
href="../../features/constraints/#dedicated-attribute">dedicated</a>
+<a href="../configuration/#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/0.13.0/reference/configuration-best-practices/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/configuration-best-practices/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/reference/configuration-best-practices/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/reference/configuration-best-practices/index.html
Thu Apr 21 15:07:18 2016
@@ -135,7 +135,7 @@ limit to 5 and a <code>min_duration</cod
into a common process template.</p>
<p>Furthermore, the Python version is repeated everywhere. This can be
-bound via structural templating as described in the <a
href="configuration-templating.md#AdvancedBinding">Advanced Binding</a>
+bound via structural templating as described in the <a
href="../configuration-templating/#AdvancedBinding">Advanced Binding</a>
section.</p>
<p><code>less_redundant.aurora</code> contains:</p>
Modified:
aurora/site/publish/documentation/0.13.0/reference/configuration-templating/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/configuration-templating/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/reference/configuration-templating/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/reference/configuration-templating/index.html
Thu Apr 21 15:07:18 2016
@@ -86,7 +86,7 @@
<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="configuration.md">Aurora Configuration Reference</a>
+<p><a href="../configuration/">Aurora 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.13.0/reference/configuration-tutorial/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/configuration-tutorial/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/reference/configuration-tutorial/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/reference/configuration-tutorial/index.html
Thu Apr 21 15:07:18 2016
@@ -88,26 +88,26 @@ and best practices. When writing a confi
arguments as <code>aurora job create</code> or <code>aurora update
start</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="../getting-started/tutorial.md">Aurora Tutorial</a>.</p>
+<p>You should read this after going through the general <a
href="../../getting-started/tutorial/">Aurora Tutorial</a>.</p>
<ul>
-<li><a href="#user-content-the-basics">The Basics</a>
+<li><a href="#the-basics">The Basics</a>
<ul>
-<li><a href="#user-content-use-bottom-to-top-object-ordering">Use
Bottom-To-Top Object Ordering</a></li>
+<li><a href="#use-bottom-to-top-object-ordering">Use Bottom-To-Top Object
Ordering</a></li>
</ul></li>
-<li><a href="#user-content-an-example-configuration-file">An Example
Configuration File</a></li>
-<li><a href="#user-content-defining-process-objects">Defining Process
Objects</a></li>
-<li><a href="#user-content-getting-your-code-into-the-sandbox">Getting Your
Code Into The Sandbox</a></li>
-<li><a href="#user-content-defining-task-objects">Defining Task Objects</a>
+<li><a href="#an-example-configuration-file">An Example Configuration
File</a></li>
+<li><a href="#defining-process-objects">Defining Process Objects</a></li>
+<li><a href="#getting-your-code-into-the-sandbox">Getting Your Code Into The
Sandbox</a></li>
+<li><a href="#defining-task-objects">Defining Task Objects</a>
<ul>
-<li><a
href="#user-content-sequentialtask-running-processes-in-parallel-or-sequentially">SequentialTask:
Running Processes in Parallel or Sequentially</a></li>
-<li><a href="#user-content-simpletask">SimpleTask</a></li>
-<li><a href="#user-content-combining-tasks">Combining tasks</a></li>
+<li><a
href="#sequentialtask-running-processes-in-parallel-or-sequentially">SequentialTask:
Running Processes in Parallel or Sequentially</a></li>
+<li><a href="#simpletask">SimpleTask</a></li>
+<li><a href="#combining-tasks">Combining tasks</a></li>
</ul></li>
-<li><a href="#user-content-defining-job-objects">Defining Job Objects</a></li>
-<li><a href="#user-content-the-jobs-list">The jobs List</a></li>
+<li><a href="#defining-job-objects">Defining Job Objects</a></li>
+<li><a href="#the-jobs-list">The jobs List</a></li>
<li><a href="#basic-examples">Basic Examples</a></li>
</ul>
@@ -143,12 +143,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="configuration.md"><em>Aurora
Configuration
+well as any objects shown in the <a href="../configuration/"><em>Aurora
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="configuration.md"><em>Aurora Configuration Reference</em></a>
+<p><a href="../configuration/"><em>Aurora 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>
@@ -307,7 +307,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="configuration.md#process-objects">Aurora Configuration Reference</a>.</p>
+<p><code>Process</code> also has optional attributes to customize its
behaviour. Details can be found in the <a
href="../configuration/#process-objects">Aurora Configuration Reference</a>.</p>
<h2 id="getting-your-code-into-the-sandbox">Getting Your Code Into The
Sandbox</h2>
@@ -367,7 +367,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="configuration.md#task-object">Aurora Configuration
Reference</a></p>
+<p>A Task has optional attributes to customize its behaviour. Details can be
found in the <a href="../configuration/#task-object">Aurora Configuration
Reference</a></p>
<h3
id="sequentialtask-running-processes-in-parallel-or-sequentially">SequentialTask:
Running Processes in Parallel or Sequentially</h3>
@@ -524,7 +524,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="configuration.md#job-objects">Aurora Configuration Reference</a>.</p>
+attributes. Details can be found in the <a
href="../configuration/#job-objects">Aurora Configuration Reference</a>.</p>
<h2 id="the-jobs-list">The jobs List</h2>
Modified:
aurora/site/publish/documentation/0.13.0/reference/configuration/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/configuration/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/reference/configuration/index.html
(original)
+++ aurora/site/publish/documentation/0.13.0/reference/configuration/index.html
Thu Apr 21 15:07:18 2016
@@ -87,8 +87,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="../getting-started/tutorial.md">Tutorial</a>.
When you feel comfortable with the basics, move
-on to the <a href="configuration-tutorial.md">Configuration Tutorial</a> for
more in-depth coverage of
+quickly, check out the <a href="../../getting-started/tutorial/">Tutorial</a>.
When you feel comfortable with the basics, move
+on to the <a href="../configuration-tutorial/">Configuration Tutorial</a> for
more in-depth coverage of
configuration design.</p>
<ul>
@@ -520,7 +520,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="../features/resource-isolation.md">Resource Isolation document</a>
for suggested values and to understand how
+<a href="../../features/resource-isolation/">Resource Isolation document</a>
for suggested values and to understand how
resources are allocated.</p>
<table><thead>
@@ -596,7 +596,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="../features/cron-jobs.md">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="../../features/cron-jobs/">Cron Jobs</a> for more information.
Default: None (not a cron job.)</td>
</tr>
<tr>
<td><code>cron_collision_policy</code></td>
@@ -631,7 +631,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.md#preemption">preempt</a> other tasks (Default:
False). Production job role must have the appropriate <a
href="../features/multitenancy.md#preemption">quota</a>.</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>
</tr>
<tr>
<td><code>health_check_config</code></td>
@@ -699,7 +699,7 @@ resources are allocated.</p>
<tr>
<td><code>pulse_interval_secs</code></td>
<td style="text-align: center">Integer</td>
-<td>Indicates a <a
href="../features/job-updates.md#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>
+<td>Indicates a <a
href="../../features/job-updates/#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>
@@ -812,13 +812,13 @@ resources are allocated.</p>
registered in the ServerSet <code>/aurora/role/environment/jobname</code> in
the
zookeeper ensemble configured by the executor (which can be optionally
overriden by specifying
<code>zk_path</code> parameter). If no Announcer object is specified,
-no announcement will take place. For more information about ServerSets, see
the <a href="../features/service-discovery.md">Service Discover</a>
+no announcement will take place. For more information about ServerSets, see
the <a href="../../features/service-discovery/">Service Discover</a>
documentation.</p>
<p>By default, the hostname in the registered endpoints will be the
<code>--hostname</code> parameter
that is passed to the mesos slave. To override the hostname value, the
executor can be started
with <code>--announcer-hostname=<overriden_value></code>. If you decide
to use <code>--announcer-hostname</code> and if
-the overriden value needs to change for every executor, then the executor has
to be started inside a wrapper, see <a
href="../operations/configuration.md#thermos-executor-wrapper">Executor
Wrapper</a>.</p>
+the overriden value needs to change for every executor, then the executor has
to be started inside a wrapper, see <a
href="../../operations/configuration/#thermos-executor-wrapper">Executor
Wrapper</a>.</p>
<p>For example, if you want the hostname in the endpoint to be an IP address
instead of the hostname,
the <code>--hostname</code> parameter to the mesos slave can be set to the
machine IP or the executor can
@@ -1025,7 +1025,7 @@ constraints</em>.</p>
</tr>
</tbody></table>
-<p>Further details can be found in the <a
href="../features/constraints.md">Scheduling Constraints</a> feature
+<p>Further details can be found in the <a
href="../../features/constraints/">Scheduling Constraints</a> feature
description.</p>
<h1 id="template-namespaces">Template Namespaces</h1>
Modified:
aurora/site/publish/documentation/0.13.0/reference/scheduler-configuration/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/scheduler-configuration/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
---
aurora/site/publish/documentation/0.13.0/reference/scheduler-configuration/index.html
(original)
+++
aurora/site/publish/documentation/0.13.0/reference/scheduler-configuration/index.html
Thu Apr 21 15:07:18 2016
@@ -85,7 +85,7 @@
<p>The Aurora scheduler can take a variety of configuration options through
command-line arguments.
A list of the available options can be seen by running <code>aurora-scheduler
-help</code>.</p>
-<p>Please refer to the <a href="../operations/configuration.md">Operator
Configuration Guide</a> for details on how
+<p>Please refer to the <a href="../../operations/configuration/">Operator
Configuration Guide</a> for details on how
to properly set the most important options.</p>
<pre class="highlight plaintext"><code>$ aurora-scheduler -help
-------------------------------------------------------------------------
