aurora-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wfar...@apache.org
Subject svn commit: r1719620 - in /aurora/site: ./ publish/documentation/latest/client-commands/ publish/documentation/latest/configuration-reference/ publish/documentation/latest/configuration-tutorial/ publish/documentation/latest/cron-jobs/ publish/document...
Date Sat, 12 Dec 2015 02:40:37 GMT
Author: wfarner
Date: Sat Dec 12 02:40:36 2015
New Revision: 1719620

URL: http://svn.apache.org/viewvc?rev=1719620&view=rev
Log:
Site: fix regex to correct a bunch of broken links.

Modified:
    aurora/site/Rakefile
    aurora/site/publish/documentation/latest/client-commands/index.html
    aurora/site/publish/documentation/latest/configuration-reference/index.html
    aurora/site/publish/documentation/latest/configuration-tutorial/index.html
    aurora/site/publish/documentation/latest/cron-jobs/index.html
    aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html
    aurora/site/publish/documentation/latest/developing-aurora-client/index.html
    aurora/site/publish/documentation/latest/resources/index.html
    aurora/site/publish/documentation/latest/storage-config/index.html
    aurora/site/publish/documentation/latest/storage/index.html
    aurora/site/publish/documentation/latest/user-guide/index.html
    aurora/site/source/documentation/latest/client-commands.md
    aurora/site/source/documentation/latest/configuration-reference.md
    aurora/site/source/documentation/latest/configuration-tutorial.md
    aurora/site/source/documentation/latest/cron-jobs.md
    aurora/site/source/documentation/latest/deploying-aurora-scheduler.md
    aurora/site/source/documentation/latest/developing-aurora-client.md
    aurora/site/source/documentation/latest/resources.md
    aurora/site/source/documentation/latest/storage-config.md
    aurora/site/source/documentation/latest/storage.md
    aurora/site/source/documentation/latest/user-guide.md

Modified: aurora/site/Rakefile
URL: http://svn.apache.org/viewvc/aurora/site/Rakefile?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/Rakefile (original)
+++ aurora/site/Rakefile Sat Dec 12 02:40:36 2015
@@ -38,7 +38,7 @@ task :update_docs do
     Dir.glob('*.md').each { |doc|
       puts "working on: #{doc}"
       IO.write(doc, File.open(doc, :encoding => 'utf-8') { |f|
-        f.read.gsub(/\(([A-Za-z0-9-]+)(\.md)\)/, '(/documentation/latest/\1/)')
+        f.read.gsub(/\(([A-Za-z0-9-]+)\.md(#[^\)]+)?\)/, '(/documentation/latest/\1/\2)')
       })
 
       # Hack to fix anchor links and names, which GitHub prefixes with 'user-content-'

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=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/client-commands/index.html (original)
+++ aurora/site/publish/documentation/latest/client-commands/index.html Sat Dec 12 02:40:36
2015
@@ -247,7 +247,7 @@ pulsing an active coordinated job update
 <a href="../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="configuration-reference.md#updateconfig-objects">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>
@@ -372,8 +372,8 @@ configuration file, and displays the par
 </code></pre>
 
 <p>Prints the production quota allocated to the role&rsquo;s value at the given
-cluster. Only non-<a href="deploying-aurora-scheduler.md#dedicated-attribute">dedicated</a>
-<a href="configuration-reference.md#job-objects">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=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/configuration-reference/index.html (original)
+++ aurora/site/publish/documentation/latest/configuration-reference/index.html Sat Dec 12
02:40:36 2015
@@ -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="resources.md#task-preemption">preempt</a>
other tasks (Default: False). Production job role must have the appropriate <a href="resources.md#resource-quota">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="deploying-aurora-scheduler.md#configuring-resource-oversubscription">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="client-commands.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="/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>
 

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=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/configuration-tutorial/index.html (original)
+++ aurora/site/publish/documentation/latest/configuration-tutorial/index.html Sat Dec 12
02:40:36 2015
@@ -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="configuration-reference.md#process-objects"><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="configuration-reference.md#task-object"><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="configuration-reference.md#job-objects">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>
 

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=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/cron-jobs/index.html (original)
+++ aurora/site/publish/documentation/latest/cron-jobs/index.html Sat Dec 12 02:40:36 2015
@@ -74,7 +74,7 @@
 
 <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="configuration-reference.md#job-objects"><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 &ldquo;every 5 minutes&rdquo; (<code>*/5 * * * *</code>), &ldquo;Fridays
at 17:00&rdquo; (<code>* 17 * * FRI</code>), and
 &ldquo;the 1st and 15th day of the month at 03:00&rdquo; (<code>0 3 1,15 *</code>).</p>
 
@@ -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="configuration-reference.md#task-objects">Task</a> object. To get &ldquo;run-until-success&rdquo;
semantics,
+<a href="/documentation/latest/configuration-reference/#task-objects">Task</a>
object. To get &ldquo;run-until-success&rdquo; 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=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html (original)
+++ aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html Sat Dec
12 02:40:36 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="storage-config.md#scheduler-storage-configuration-flags">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>
@@ -284,7 +284,7 @@ restarted.</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="configuration-reference.md#revocable-jobs">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
@@ -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="configuration-reference.md#specifying-scheduling-constraints">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="resources.md#resource-quota">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="configuration-reference.md#specifying-scheduling-constraints">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="storage-config.md#-native_log_quorum_size">-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="storage-config.md#recovering-from-a-scheduler-backup">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=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/developing-aurora-client/index.html (original)
+++ aurora/site/publish/documentation/latest/developing-aurora-client/index.html Sat Dec 12
02:40:36 2015
@@ -50,7 +50,7 @@
 contents of this file can be found in the
 <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="client-commands.md#cluster-configuration">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>
 

Modified: aurora/site/publish/documentation/latest/resources/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/resources/index.html?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/resources/index.html (original)
+++ aurora/site/publish/documentation/latest/resources/index.html Sat Dec 12 02:40:36 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="configuration-reference.md#job-objects">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="deploying-aurora-scheduler.md#dedicated-attribute">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="configuration-reference.md#job-objects">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="configuration-reference.md#job-objects">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=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/storage-config/index.html (original)
+++ aurora/site/publish/documentation/latest/storage-config/index.html Sat Dec 12 02:40:36
2015
@@ -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="deploying-aurora-scheduler.md#replicated-log-configuration">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=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/storage/index.html (original)
+++ aurora/site/publish/documentation/latest/storage/index.html Sat Dec 12 02:40:36 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="storage-config.md#recovering-from-a-scheduler-backup">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/user-guide/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/user-guide/index.html?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/user-guide/index.html (original)
+++ aurora/site/publish/documentation/latest/user-guide/index.html Sat Dec 12 02:40:36 2015
@@ -280,7 +280,7 @@ requests:</p>
 </tbody></table>
 
 <p>Please see the
-<a href="configuration-reference.md#healthcheckconfig-objects">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>

Modified: aurora/site/source/documentation/latest/client-commands.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/client-commands.md?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/client-commands.md (original)
+++ aurora/site/source/documentation/latest/client-commands.md Sat Dec 12 02:40:36 2015
@@ -203,7 +203,7 @@ pulsing an active coordinated job update
 [pulseJobUpdate RPC](../api/src/main/thrift/org/apache/aurora/gen/api.thrift).
 
 A coordinated update is defined by setting a positive
-[pulse_interval_secs](configuration-reference.md#updateconfig-objects) value in job configuration
+[pulse_interval_secs](/documentation/latest/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.
@@ -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](deploying-aurora-scheduler.md#dedicated-attribute)
-[production](configuration-reference.md#job-objects) jobs consume quota.
+cluster. Only non-[dedicated](/documentation/latest/deploying-aurora-scheduler/#dedicated-attribute)
+[production](/documentation/latest/configuration-reference/#job-objects) jobs consume quota.
 
 ### Finding a Job on Web UI
 

Modified: aurora/site/source/documentation/latest/configuration-reference.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/configuration-reference.md?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/configuration-reference.md (original)
+++ aurora/site/source/documentation/latest/configuration-reference.md Sat Dec 12 02:40:36
2015
@@ -332,7 +332,7 @@ Job Schema
   ```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](resources.md#task-preemption)
other tasks (Default: False). Production job role must have the appropriate [quota](resources.md#resource-quota).
+  ```production``` | Boolean |  Whether or not this is a production task that may [preempt](/documentation/latest/resources/#task-preemption)
other tasks (Default: False). Production job role must have the appropriate [quota](/documentation/latest/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](deploying-aurora-scheduler.md#configuring-resource-oversubscription)
+Scheduler must be [configured](/documentation/latest/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](client-commands.md#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)
+| ```pulse_interval_secs```    | Integer  |  Indicates a [coordinated update](/documentation/latest/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
 

Modified: aurora/site/source/documentation/latest/configuration-tutorial.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/configuration-tutorial.md?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/configuration-tutorial.md (original)
+++ aurora/site/source/documentation/latest/configuration-tutorial.md Sat Dec 12 02:40:36
2015
@@ -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*](configuration-reference.md#process-objects).
+`Process` also has optional attributes to customize its behaviour. Details can be found in
the [*Aurora+Thermos Configuration Reference*](/documentation/latest/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*](configuration-reference.md#task-object)
+A Task has optional attributes to customize its behaviour. Details can be found in the [*Aurora+Thermos
Configuration Reference*](/documentation/latest/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](configuration-reference.md#job-objects).
+attributes. Details can be found in the [Aurora+Thermos Configuration Reference](/documentation/latest/configuration-reference/#job-objects).
 
 
 ## The jobs List

Modified: aurora/site/source/documentation/latest/cron-jobs.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/cron-jobs.md?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/cron-jobs.md (original)
+++ aurora/site/source/documentation/latest/cron-jobs.md Sat Dec 12 02:40:36 2015
@@ -22,7 +22,7 @@ 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`](configuration-reference.md#job-objects) object. Examples of cron schedules
+[`Job`](/documentation/latest/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 *`).
 
@@ -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](configuration-reference.md#task-objects) object. To get "run-until-success" semantics,
+[Task](/documentation/latest/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/latest/deploying-aurora-scheduler.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/deploying-aurora-scheduler.md?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/deploying-aurora-scheduler.md (original)
+++ aurora/site/source/documentation/latest/deploying-aurora-scheduler.md Sat Dec 12 02:40:36
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](storage-config.md#scheduler-storage-configuration-flags) for more replicated
+See [this document](/documentation/latest/storage-config/#scheduler-storage-configuration-flags)
for more replicated
 log and storage configuration options.
 
 ## Initializing the Replicated Log
@@ -194,7 +194,7 @@ See [security.md](/documentation/latest/
 ## Configuring Resource Oversubscription
 
 **WARNING**: This feature is currently in alpha status. Do not use it in production clusters!
-See [this document](configuration-reference.md#revocable-jobs) for more feature details.
+See [this document](/documentation/latest/configuration-reference/#revocable-jobs) for more
feature details.
 
 Set these scheduler flag to allow receiving revocable Mesos offers:
 
@@ -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](configuration-reference.md#specifying-scheduling-constraints).  Most of these
+[constraints](/documentation/latest/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](resources.md#resource-quota) about resource quotas to learn how quotas
apply to
+See the [section](/documentation/latest/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](configuration-reference.md#specifying-scheduling-constraints).
+[job configuration](/documentation/latest/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](storage-config.md#-native_log_quorum_size) on each
+Increase [-native_log_quorum_size](/documentation/latest/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](storage-config.md#recovering-from-a-scheduler-backup).
+[recovering from backup](/documentation/latest/storage-config/#recovering-from-a-scheduler-backup).

Modified: aurora/site/source/documentation/latest/developing-aurora-client.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/developing-aurora-client.md?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/developing-aurora-client.md (original)
+++ aurora/site/source/documentation/latest/developing-aurora-client.md Sat Dec 12 02:40:36
2015
@@ -11,7 +11,7 @@ The client uses a configuration file tha
 contents of this file can be found in the
 [Client Cluster Configuration](/documentation/latest/client-cluster-configuration/) documentation.
Information about
 how the client locates this file can be found in the
-[Client Commands](client-commands.md#cluster-configuration) documentation.
+[Client Commands](/documentation/latest/client-commands/#cluster-configuration) documentation.
 
 Building and Testing the Client
 ===============================

Modified: aurora/site/source/documentation/latest/resources.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/resources.md?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/resources.md (original)
+++ aurora/site/source/documentation/latest/resources.md Sat Dec 12 02:40:36 2015
@@ -147,18 +147,18 @@ the same host may cause contention.
 ## Resource Quota
 
 Aurora requires resource quotas for
-[production non-dedicated jobs](configuration-reference.md#job-objects). Quota is enforced
at
+[production non-dedicated jobs](/documentation/latest/configuration-reference/#job-objects).
Quota is enforced at
 the job role level and when set, defines a non-preemptible pool of compute resources within
 that role.
 
 To grant quota to a particular role in production use `aurora_admin set_quota` command.
 
 NOTE: all job types (service, adhoc or cron) require role resource quota unless a job has
-[dedicated constraint set](deploying-aurora-scheduler.md#dedicated-attribute).
+[dedicated constraint set](/documentation/latest/deploying-aurora-scheduler/#dedicated-attribute).
 
 ## Task preemption
 
 Under a particular resource shortage pressure, tasks from
-[production](configuration-reference.md#job-objects) jobs may preempt tasks from any non-production
+[production](/documentation/latest/configuration-reference/#job-objects) 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 [priority](configuration-reference.md#job-objects).
\ No newline at end of file
+higher [priority](/documentation/latest/configuration-reference/#job-objects).
\ No newline at end of file

Modified: aurora/site/source/documentation/latest/storage-config.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/storage-config.md?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/storage-config.md (original)
+++ aurora/site/source/documentation/latest/storage-config.md Sat Dec 12 02:40:36 2015
@@ -33,7 +33,7 @@ or require attention before deploying in
 
 #### -native_log_quorum_size
 Defines the Mesos replicated log quorum size. See
-[the replicated log configuration document](deploying-aurora-scheduler.md#replicated-log-configuration)
+[the replicated log configuration document](/documentation/latest/deploying-aurora-scheduler/#replicated-log-configuration)
 on how to choose the right value.
 
 #### -native_log_file_path

Modified: aurora/site/source/documentation/latest/storage.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/storage.md?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/storage.md (original)
+++ aurora/site/source/documentation/latest/storage.md Sat Dec 12 02:40:36 2015
@@ -33,7 +33,7 @@ is [thrift](https://github.com/apache/th
 This helps establishing periodic recovery checkpoints and speeds up volatile storage recovery
on
 restart.
 * Backup manager: as a precaution, snapshots are periodically written out into backup files.
-This solves a [disaster recovery problem](storage-config.md#recovering-from-a-scheduler-backup)
+This solves a [disaster recovery problem](/documentation/latest/storage-config/#recovering-from-a-scheduler-backup)
 in case of a complete loss or corruption of Mesos log files.
 
 ![Storage hierarchy](images/storage_hierarchy.png)

Modified: aurora/site/source/documentation/latest/user-guide.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/user-guide.md?rev=1719620&r1=1719619&r2=1719620&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/user-guide.md (original)
+++ aurora/site/source/documentation/latest/user-guide.md Sat Dec 12 02:40:36 2015
@@ -212,7 +212,7 @@ requests:
 | `POST /abortabortabort` | Final warning task is being killed.     |
 
 Please see the
-[configuration reference](configuration-reference.md#healthcheckconfig-objects) for
+[configuration reference](/documentation/latest/configuration-reference/#healthcheckconfig-objects)
for
 configuration options for this feature.
 
 #### Snoozing Health Checks




Mime
View raw message