You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@aurora.apache.org by wf...@apache.org on 2016/04/21 17:07:18 UTC
svn commit: r1740340 [3/3] - in /aurora/site: publish/
publish/documentation/0.13.0/
publish/documentation/0.13.0/additional-resources/tools/
publish/documentation/0.13.0/contributing/
publish/documentation/0.13.0/development/db-migration/ publish/docu...
Modified: aurora/site/source/documentation/0.13.0/development/db-migration.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/development/db-migration.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/development/db-migration.md (original)
+++ aurora/site/source/documentation/0.13.0/development/db-migration.md Thu Apr 21 15:07:18 2016
@@ -13,7 +13,7 @@ Upgrades
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
[MigrationScript](https://github.com/mybatis/migrations/blob/master/src/main/java/org/apache/ibatis/migration/MigrationScript.java)
-interface (see [V001_TestMigration](../../src/test/java/org/apache/aurora/scheduler/storage/db/testmigration/V001_TestMigration.java)
+interface (see [V001_TestMigration](https://github.com/apache/aurora/blob/rel/0.13.0/src/test/java/org/apache/aurora/scheduler/storage/db/testmigration/V001_TestMigration.java)
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/source/documentation/0.13.0/development/design-documents.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/development/design-documents.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/development/design-documents.md (original)
+++ aurora/site/source/documentation/0.13.0/development/design-documents.md Thu Apr 21 15:07:18 2016
@@ -8,7 +8,7 @@ in the proposed form.
Current and past documents:
-* [Command Hooks for the Aurora Client](design/command-hooks.md)
+* [Command Hooks for the Aurora Client](../design/command-hooks/)
* [Health Checks for Updates](https://docs.google.com/document/d/1ZdgW8S4xMhvKW7iQUX99xZm10NXSxEWR0a-21FP5d94/edit)
* [JobUpdateDiff thrift API](https://docs.google.com/document/d/1Fc_YhhV7fc4D9Xv6gJzpfooxbK4YWZcvzw6Bd3qVTL8/edit)
* [REST API RFC](https://docs.google.com/document/d/11_lAsYIRlD5ETRzF2eSd3oa8LXAHYFD8rSetspYXaf4/edit)
Modified: aurora/site/source/documentation/0.13.0/development/thermos.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/development/thermos.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/development/thermos.md (original)
+++ aurora/site/source/documentation/0.13.0/development/thermos.md Thu Apr 21 15:07:18 2016
@@ -121,6 +121,6 @@ that would undermine the goal of ensurin
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
-[job configuration](../reference/configuration.md) that exercises the feature, and
+[job configuration](../../reference/configuration/) that exercises the feature, and
copying the checkpoint file from the sandbox directory, by default this is
`/var/run/thermos/checkpoints/<aurora task id>`.
Modified: aurora/site/source/documentation/0.13.0/development/thrift.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/development/thrift.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/development/thrift.md (original)
+++ aurora/site/source/documentation/0.13.0/development/thrift.md Thu Apr 21 15:07:18 2016
@@ -6,7 +6,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
-[api.thrift](../../api/src/main/thrift/org/apache/aurora/gen/api.thrift).
+[api.thrift](https://github.com/apache/aurora/blob/rel/0.13.0/api/src/main/thrift/org/apache/aurora/gen/api.thrift).
It is highly recommended to go through the
[Thrift: The Missing Guide](http://diwakergupta.github.io/thrift-missing-guide/) first to refresh on
@@ -33,9 +33,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 `NOT NULL`
-* Check [storage.thrift](../../api/src/main/thrift/org/apache/aurora/gen/storage.thrift) to see if
+* Check [storage.thrift](https://github.com/apache/aurora/blob/rel/0.13.0/api/src/main/thrift/org/apache/aurora/gen/storage.thrift) to see if
the affected struct is stored in Aurora scheduler storage. If so, it's almost certainly also
-necessary to perform a [DB migration](db-migration.md).
+necessary to perform a [DB migration](../db-migration/).
* Add a deprecation jira ticket into the vCurrent+1 release candidate
* Add a TODO for the deprecated field mentioning the jira ticket
@@ -49,6 +49,6 @@ Testing
-------
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 `aurorabuild` command. See [this document](../getting-started/vagrant.md)
+client/scheduler versions by playing with `aurorabuild` command. See [this document](../../getting-started/vagrant/)
for more.
Modified: aurora/site/source/documentation/0.13.0/features/constraints.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/features/constraints.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/features/constraints.md (original)
+++ aurora/site/source/documentation/0.13.0/features/constraints.md Thu Apr 21 15:07:18 2016
@@ -50,7 +50,7 @@ most one task per rack:
Use these constraints sparingly as they can dramatically reduce Tasks' schedulability.
Further details are available in the reference documentation on
-[Scheduling Constraints](../reference/configuration.md#specifying-scheduling-constraints).
+[Scheduling Constraints](../../reference/configuration/#specifying-scheduling-constraints).
@@ -72,7 +72,7 @@ scheduled on nodes that claim to have an
Further details are available in the reference documentation on
-[Scheduling Constraints](../reference/configuration.md#specifying-scheduling-constraints).
+[Scheduling Constraints](../../reference/configuration/#specifying-scheduling-constraints).
Running stateful services
Modified: aurora/site/source/documentation/0.13.0/features/containers.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/features/containers.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/features/containers.md (original)
+++ aurora/site/source/documentation/0.13.0/features/containers.md Thu Apr 21 15:07:18 2016
@@ -5,9 +5,9 @@ Containers
Docker
------
-Aurora has optional support for launching Docker containers, if correctly [configured by an Operator](../operations/configuration.md#docker-containers).
+Aurora has optional support for launching Docker containers, if correctly [configured by an Operator](../../operations/configuration/#docker-containers).
-Example (available in the [Vagrant environment](../getting-started/vagrant.md)):
+Example (available in the [Vagrant environment](../../getting-started/vagrant/)):
$ cat /vagrant/examples/jobs/docker/hello_docker.aurora
@@ -40,4 +40,4 @@ Example (available in the [Vagrant envir
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
-[Reference Documentation](../reference/configuration.md#docker-object).
+[Reference Documentation](../../reference/configuration/#docker-object).
Modified: aurora/site/source/documentation/0.13.0/features/cron-jobs.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/features/cron-jobs.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/features/cron-jobs.md (original)
+++ aurora/site/source/documentation/0.13.0/features/cron-jobs.md Thu Apr 21 15:07:18 2016
@@ -20,11 +20,11 @@ Aurora supports execution of scheduled j
A job is identified as a cron job by the presence of a
`cron_schedule` attribute containing a cron-style schedule in the
-[`Job`](../reference/configuration.md#job-objects) object. Examples of cron schedules
+[`Job`](../../reference/configuration/#job-objects) object. Examples of cron schedules
include "every 5 minutes" (`*/5 * * * *`), "Fridays at 17:00" (`* 17 * * FRI`), and
"the 1st and 15th day of the month at 03:00" (`0 3 1,15 *`).
-Example (available in the [Vagrant environment](../getting-started/vagrant.md)):
+Example (available in the [Vagrant environment](../../getting-started/vagrant/)):
$ cat /vagrant/examples/jobs/cron_hello_world.aurora
# A cron job that runs every 5 minutes.
@@ -58,7 +58,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](../reference/configuration.md#task-object) object. To get "run-until-success" semantics,
+[Task](../../reference/configuration/#task-object) object. To get "run-until-success" semantics,
set `max_task_failures` to `-1`.
## Interacting with cron jobs via the Aurora CLI
Modified: aurora/site/source/documentation/0.13.0/features/job-updates.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/features/job-updates.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/features/job-updates.md (original)
+++ aurora/site/source/documentation/0.13.0/features/job-updates.md Thu Apr 21 15:07:18 2016
@@ -60,7 +60,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).
For details how to control a job update, please see the
-[UpdateConfig](../reference/configuration.md#updateconfig-objects) configuration object.
+[UpdateConfig](../../reference/configuration/#updateconfig-objects) configuration object.
Coordinated Job Updates
@@ -71,10 +71,10 @@ acknowledging ("heartbeating") job updat
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
-[pulseJobUpdate RPC](../../api/src/main/thrift/org/apache/aurora/gen/api.thrift).
+[pulseJobUpdate RPC](https://github.com/apache/aurora/blob/rel/0.13.0/api/src/main/thrift/org/apache/aurora/gen/api.thrift).
A coordinated update is defined by setting a positive
-[pulse_interval_secs](../reference/configuration.md#updateconfig-objects) value in job configuration
+[pulse_interval_secs](../../reference/configuration/#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.
Modified: aurora/site/source/documentation/0.13.0/features/multitenancy.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/features/multitenancy.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/features/multitenancy.md (original)
+++ aurora/site/source/documentation/0.13.0/features/multitenancy.md Thu Apr 21 15:07:18 2016
@@ -2,7 +2,7 @@ Multitenancy
============
Aurora is a multi-tenant system that can run jobs of multiple clients/tenants.
-Going beyond the [resource isolation on an individual host](resource-isolation.md), it is
+Going beyond the [resource isolation on an individual host](../resource-isolation/), it is
crucial to prevent those jobs from stepping on each others toes.
@@ -19,7 +19,7 @@ to differentiate between different jobs.
* Jobname is the custom name of your job.
Role names correspond to user accounts. They are used for
-[authentication](../operations/security.md), as the linux user used to run jobs, and for the
+[authentication](../../operations/security/), as the linux user used to run jobs, and for the
assignment of [quota](#preemption). If you don't know what accounts are available, contact your
sysadmin.
@@ -44,19 +44,19 @@ Let's consider we have a pending job tha
prevents this. Active tasks can become the victim of preemption, if:
- both candidate and victim are owned by the same role and the
- [priority](../reference/configuration.md#job-objects) of a victim is lower than the
- [priority](../reference/configuration.md#job-objects) of the candidate.
- - OR a victim is non-[production](../reference/configuration.md#job-objects) and the candidate is
- [production](../reference/configuration.md#job-objects).
+ [priority](../../reference/configuration/#job-objects) of a victim is lower than the
+ [priority](../../reference/configuration/#job-objects) of the candidate.
+ - OR a victim is non-[production](../../reference/configuration/#job-objects) and the candidate is
+ [production](../../reference/configuration/#job-objects).
-In other words, tasks from [production](../reference/configuration.md#job-objects) jobs may preempt
+In other words, tasks from [production](../../reference/configuration/#job-objects) 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 [priority](../reference/configuration.md#job-objects).
+production jobs in the same role with higher [priority](../../reference/configuration/#job-objects).
-Aurora requires resource quotas for [production non-dedicated jobs](../reference/configuration.md#job-objects).
+Aurora requires resource quotas for [production non-dedicated jobs](../../reference/configuration/#job-objects).
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
-[dedicated constraint set](constraints.md#dedicated-attribute).
+[dedicated constraint set](../constraints/#dedicated-attribute).
To grant quota to a particular role in production, an operator can use the command
`aurora_admin set_quota`.
Modified: aurora/site/source/documentation/0.13.0/features/resource-isolation.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/features/resource-isolation.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/features/resource-isolation.md (original)
+++ aurora/site/source/documentation/0.13.0/features/resource-isolation.md Thu Apr 21 15:07:18 2016
@@ -158,10 +158,10 @@ jobs. If not configured properly revocab
-receive_revocable_resources=true
-Specify a tier configuration file path (unless you want to use the [default](../../src/main/resources/org/apache/aurora/scheduler/tiers.json)):
+Specify a tier configuration file path (unless you want to use the [default](https://github.com/apache/aurora/blob/rel/0.13.0/src/main/resources/org/apache/aurora/scheduler/tiers.json)):
-tier_config=path/to/tiers/config.json
-See the [Configuration Reference](../references/configuration.md) for details on how to mark a job
+See the [Configuration Reference](../../references/configuration/) for details on how to mark a job
as being revocable.
Modified: aurora/site/source/documentation/0.13.0/features/service-discovery.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/features/service-discovery.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/features/service-discovery.md (original)
+++ aurora/site/source/documentation/0.13.0/features/service-discovery.md Thu Apr 21 15:07:18 2016
@@ -11,7 +11,7 @@ of which there are several reference imp
These can also be used natively in Finagle using the [ZookeeperServerSetCluster](https://github.com/twitter/finagle/blob/master/finagle-serversets/src/main/scala/com/twitter/finagle/zookeeper/ZookeeperServerSetCluster.scala).
-For more information about how to configure announcing, see the [Configuration Reference](../reference/configuration.md).
+For more information about how to configure announcing, see the [Configuration Reference](../../reference/configuration/).
Using Mesos DiscoveryInfo
-------------------------
Modified: aurora/site/source/documentation/0.13.0/features/services.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/features/services.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/features/services.md (original)
+++ aurora/site/source/documentation/0.13.0/features/services.md Thu Apr 21 15:07:18 2016
@@ -10,10 +10,10 @@ Service Specification
---------------------
A job is identified as a service by the presence of the flag
-``service=True` in the [`Job`](../reference/configuration.md#job-objects) object.
+``service=True` in the [`Job`](../../reference/configuration/#job-objects) object.
The `Service` alias can be used as shorthand for `Job` with `service=True`.
-Example (available in the [Vagrant environment](../getting-started/vagrant.md)):
+Example (available in the [Vagrant environment](../../getting-started/vagrant/)):
$ cat /vagrant/examples/jobs/hello_world.aurora
hello = Process(
@@ -43,14 +43,14 @@ Example (available in the [Vagrant envir
Jobs without the service bit set only restart up to `max_task_failures` times and only if they
terminated unsuccessfully either due to human error or machine failure (see the
-[`Job`](../reference/configuration.md#job-objects) object for details).
+[`Job`](../../reference/configuration/#job-objects) object for details).
Ports
-----
In order to be useful, most services have to bind to one or more ports. Aurora enables this
-usecase via the [`thermos.ports` namespace](../reference/configuration.md#thermos-namespace) that
+usecase via the [`thermos.ports` namespace](../../reference/configuration/#thermos-namespace) that
allows to request arbitrarily named ports:
@@ -68,7 +68,7 @@ will be replaced with something like:
Where 42816 happens to be the allocated port.
For details on how to enable clients to discover this dynamically assigned port, see our
-[Service Discovery](service-discovery.md) documentation.
+[Service Discovery](../service-discovery/) documentation.
Health Checking
@@ -87,7 +87,7 @@ via repeated calls to the `/health` endp
)
Please see the
-[configuration reference](../reference/configuration.md#user-content-healthcheckconfig-objects)
+[configuration reference](../../reference/configuration/#healthcheckconfig-objects)
for configuration options for this feature.
You can pause health checking by touching a file inside of your sandbox, named `.healthchecksnooze`.
Modified: aurora/site/source/documentation/0.13.0/features/sla-metrics.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/features/sla-metrics.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/features/sla-metrics.md (original)
+++ aurora/site/source/documentation/0.13.0/features/sla-metrics.md Thu Apr 21 15:07:18 2016
@@ -62,7 +62,7 @@ relevant to uptime calculations. By appl
transition records, we can build a deterministic downtime trace for every given service instance.
A task going through a state transition carries one of three possible SLA meanings
-(see [SlaAlgorithm.java](../../src/main/java/org/apache/aurora/scheduler/sla/SlaAlgorithm.java) for
+(see [SlaAlgorithm.java](https://github.com/apache/aurora/blob/rel/0.13.0/src/main/java/org/apache/aurora/scheduler/sla/SlaAlgorithm.java) for
sla-to-task-state mapping):
* Task is UP: starts a period where the task is considered to be up and running from the Aurora
@@ -109,7 +109,7 @@ metric that helps track the dependency o
* Per job - `sla_<job_key>_mtta_ms`
* Per cluster - `sla_cluster_mtta_ms`
* Per instance size (small, medium, large, x-large, xx-large). Size are defined in:
-[ResourceAggregates.java](../../src/main/java/org/apache/aurora/scheduler/base/ResourceAggregates.java)
+[ResourceAggregates.java](https://github.com/apache/aurora/blob/rel/0.13.0/src/main/java/org/apache/aurora/scheduler/base/ResourceAggregates.java)
* By CPU:
* `sla_cpu_small_mtta_ms`
* `sla_cpu_medium_mtta_ms`
@@ -145,7 +145,7 @@ reflecting on the overall time it takes
* Per job - `sla_<job_key>_mttr_ms`
* Per cluster - `sla_cluster_mttr_ms`
* Per instance size (small, medium, large, x-large, xx-large). Size are defined in:
-[ResourceAggregates.java](../../src/main/java/org/apache/aurora/scheduler/base/ResourceAggregates.java)
+[ResourceAggregates.java](https://github.com/apache/aurora/blob/rel/0.13.0/src/main/java/org/apache/aurora/scheduler/base/ResourceAggregates.java)
* By CPU:
* `sla_cpu_small_mttr_ms`
* `sla_cpu_medium_mttr_ms`
Modified: aurora/site/source/documentation/0.13.0/getting-started/overview.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/getting-started/overview.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/getting-started/overview.md (original)
+++ aurora/site/source/documentation/0.13.0/getting-started/overview.md Thu Apr 21 15:07:18 2016
@@ -41,7 +41,7 @@ a functioning Aurora cluster.
* **ZooKeeper**
[ZooKeeper](http://zookeeper.apache.org) 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 [Service Discovery](../features/service-discovery.md)
+ used as a vehicle for service discovery, see [Service Discovery](../../features/service-discovery/)
* **Mesos master**
The master is responsible for tracking worker machines and performing accounting of their
Modified: aurora/site/source/documentation/0.13.0/getting-started/tutorial.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/getting-started/tutorial.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/getting-started/tutorial.md (original)
+++ aurora/site/source/documentation/0.13.0/getting-started/tutorial.md Thu Apr 21 15:07:18 2016
@@ -15,9 +15,9 @@ to start getting up to speed on the syst
## Prerequisite
-This tutorial assumes you are running [Aurora locally using Vagrant](vagrant.md).
+This tutorial assumes you are running [Aurora locally using Vagrant](../vagrant/).
However, in general the instructions are also applicable to any other
-[Aurora installation](../operations/installation.md).
+[Aurora installation](../../operations/installation/).
Unless otherwise stated, all commands are to be run from the root of the aurora
repository clone.
@@ -106,8 +106,8 @@ local sandbox in which it will run. It t
actually run once the second Process starts.
For more about Aurora configuration files, see the [Configuration
-Tutorial](../reference/configuration-tutorial.md) and the [Configuration
-Reference](../reference/configuration.md) (preferably after finishing this
+Tutorial](../../reference/configuration-tutorial/) and the [Configuration
+Reference](../../reference/configuration/) (preferably after finishing this
tutorial).
@@ -132,7 +132,7 @@ When comparing two job keys, if any of t
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.
-The `clusters.json` [client configuration](../reference/client-cluster-configuration.md)
+The `clusters.json` [client configuration](../../reference/client-cluster-configuration/)
for the Aurora scheduler defines the available cluster names.
For Vagrant, from the top-level of your Aurora repository clone, do:
@@ -251,8 +251,8 @@ The job page now shows the `hello_world`
Now that you've finished this Tutorial, you should read or do the following:
-- [The Aurora Configuration Tutorial](../reference/configuration-tutorial.md), which provides more examples
+- [The Aurora Configuration Tutorial](../../reference/configuration-tutorial/), which provides more examples
and best practices for writing Aurora configurations. You should also look at
- the [Aurora Configuration Reference](../reference/configuration.md).
+ the [Aurora Configuration Reference](../../reference/configuration/).
- Explore the Aurora Client - use `aurora -h`, and read the
- [Aurora Client Commands](../reference/client-commands.md) document.
+ [Aurora Client Commands](../../reference/client-commands/) document.
Modified: aurora/site/source/documentation/0.13.0/getting-started/vagrant.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/getting-started/vagrant.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/getting-started/vagrant.md (original)
+++ aurora/site/source/documentation/0.13.0/getting-started/vagrant.md Thu Apr 21 15:07:18 2016
@@ -7,15 +7,15 @@ the steps outlined here, you will be rea
The following sections describe these steps in detail:
-1. [Overview](#user-content-overview)
-1. [Install VirtualBox and Vagrant](#user-content-install-virtualbox-and-vagrant)
-1. [Clone the Aurora repository](#user-content-clone-the-aurora-repository)
-1. [Start the local cluster](#user-content-start-the-local-cluster)
-1. [Log onto the VM](#user-content-log-onto-the-vm)
-1. [Run your first job](#user-content-run-your-first-job)
-1. [Rebuild components](#user-content-rebuild-components)
-1. [Shut down or delete your local cluster](#user-content-shut-down-or-delete-your-local-cluster)
-1. [Troubleshooting](#user-content-troubleshooting)
+1. [Overview](#overview)
+1. [Install VirtualBox and Vagrant](#install-virtualbox-and-vagrant)
+1. [Clone the Aurora repository](#clone-the-aurora-repository)
+1. [Start the local cluster](#start-the-local-cluster)
+1. [Log onto the VM](#log-onto-the-vm)
+1. [Run your first job](#run-your-first-job)
+1. [Rebuild components](#rebuild-components)
+1. [Shut down or delete your local cluster](#shut-down-or-delete-your-local-cluster)
+1. [Troubleshooting](#troubleshooting)
Overview
@@ -100,7 +100,7 @@ Run your first job
------------------
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 [Aurora Tutorial](tutorial.md).
+For more information, see the [Aurora Tutorial](../tutorial/).
Rebuild components
Modified: aurora/site/source/documentation/0.13.0/index.html.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/index.html.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/index.html.md (original)
+++ aurora/site/source/documentation/0.13.0/index.html.md Thu Apr 21 15:07:18 2016
@@ -11,63 +11,63 @@ the `#aurora` IRC channel on `irc.freeno
## Getting Started
Information for everyone new to Apache Aurora.
- * [Aurora System Overview](getting-started/overview.md)
- * [Hello World Tutorial](getting-started/tutorial.md)
- * [Local cluster with Vagrant](getting-started/vagrant.md)
+ * [Aurora System Overview](getting-started/overview/)
+ * [Hello World Tutorial](getting-started/tutorial/)
+ * [Local cluster with Vagrant](getting-started/vagrant/)
## Features
Description of important Aurora features.
- * [Containers](features/containers.md)
- * [Cron Jobs](features/cron-jobs.md)
- * [Job Updates](features/job-updates.md)
- * [Multitenancy](features/multitenancy.md)
- * [Resource Isolation](features/resource-isolation.md)
- * [Scheduling Constraints](features/constraints.md)
- * [Services](features/services.md)
- * [Service Discovery](features/service-discovery.md)
- * [SLA Metrics](features/sla-metrics.md)
+ * [Containers](features/containers/)
+ * [Cron Jobs](features/cron-jobs/)
+ * [Job Updates](features/job-updates/)
+ * [Multitenancy](features/multitenancy/)
+ * [Resource Isolation](features/resource-isolation/)
+ * [Scheduling Constraints](features/constraints/)
+ * [Services](features/services/)
+ * [Service Discovery](features/service-discovery/)
+ * [SLA Metrics](features/sla-metrics/)
## Operators
For those that wish to manage and fine-tune an Aurora cluster.
- * [Installation](operations/installation.md)
- * [Configuration](operations/configuration.md)
- * [Monitoring](operations/monitoring.md)
- * [Security](operations/security.md)
- * [Storage](operations/storage.md)
- * [Backup](operations/backup-restore.md)
+ * [Installation](operations/installation/)
+ * [Configuration](operations/configuration/)
+ * [Monitoring](operations/monitoring/)
+ * [Security](operations/security/)
+ * [Storage](operations/storage/)
+ * [Backup](operations/backup-restore/)
## Reference
The complete reference of commands, configuration options, and scheduler internals.
- * [Task lifecycle](reference/task-lifecycle.md)
+ * [Task lifecycle](reference/task-lifecycle/)
* Configuration (`.aurora` files)
- - [Configuration Reference](reference/configuration.md)
- - [Configuration Tutorial](reference/configuration-tutorial.md)
- - [Configuration Best Practices](reference/configuration-best-practices.md)
- - [Configuration Templating](reference/configuration-templating.md)
+ - [Configuration Reference](reference/configuration/)
+ - [Configuration Tutorial](reference/configuration-tutorial/)
+ - [Configuration Best Practices](reference/configuration-best-practices/)
+ - [Configuration Templating](reference/configuration-templating/)
* Aurora Client
- - [Client Commands](reference/client-commands.md)
- - [Client Hooks](reference/client-hooks.md)
- - [Client Cluster Configuration](reference/client-cluster-configuration.md)
- * [Scheduler Configuration](reference/scheduler-configuration.md)
+ - [Client Commands](reference/client-commands/)
+ - [Client Hooks](reference/client-hooks/)
+ - [Client Cluster Configuration](reference/client-cluster-configuration/)
+ * [Scheduler Configuration](reference/scheduler-configuration/)
## Additional Resources
- * [Tools integrating with Aurora](additional-resources/tools.md)
- * [Presentation videos and slides](additional-resources/presentations.md)
+ * [Tools integrating with Aurora](additional-resources/tools/)
+ * [Presentation videos and slides](additional-resources/presentations/)
## Developers
All the information you need to start modifying Aurora and contributing back to the project.
* [Contributing to the project](contributing/)
- * [Committer's Guide](development/committers-guide.md)
- * [Design Documents](development/design-documents.md)
+ * [Committer's Guide](development/committers-guide/)
+ * [Design Documents](development/design-documents/)
* Developing the Aurora components:
- - [Client](development/client.md)
- - [Scheduler](development/scheduler.md)
- - [Scheduler UI](development/ui.md)
- - [Thermos](development/thermos.md)
- - [Thrift structures](development/thrift.md)
+ - [Client](development/client/)
+ - [Scheduler](development/scheduler/)
+ - [Scheduler UI](development/ui/)
+ - [Thermos](development/thermos/)
+ - [Thrift structures](development/thrift/)
Modified: aurora/site/source/documentation/0.13.0/operations/backup-restore.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/operations/backup-restore.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/operations/backup-restore.md (original)
+++ aurora/site/source/documentation/0.13.0/operations/backup-restore.md Thu Apr 21 15:07:18 2016
@@ -15,7 +15,7 @@ Usually, it is a bad idea to restore a b
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.
-Instructions below have been verified in [Vagrant environment](../getting-started/vagrant.md) and with minor
+Instructions below have been verified in [Vagrant environment](../../getting-started/vagrant/) and with minor
syntax/path changes should be applicable to any Aurora cluster.
# Preparation
@@ -31,7 +31,7 @@ be erased after the backup snapshot is r
* Configure `aurora_admin` access to run all commands listed in
[Restore from backup](#restore-from-backup) section locally on the leading scheduler:
- * Make sure the [clusters.json](../reference/client-cluster-configuration.md) file configured to
+ * Make sure the [clusters.json](../../reference/client-cluster-configuration/) file configured to
access scheduler directly. Set `scheduler_uri` setting and remove `zk`. Since leader can get
re-elected during the restore steps, consider doing it on all scheduler replicas.
* Depending on your particular security approach you will need to either turn off scheduler
Modified: aurora/site/source/documentation/0.13.0/operations/configuration.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/operations/configuration.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/operations/configuration.md (original)
+++ aurora/site/source/documentation/0.13.0/operations/configuration.md Thu Apr 21 15:07:18 2016
@@ -2,7 +2,7 @@
The Aurora scheduler can take a variety of configuration options through command-line arguments.
Examples are available under `examples/scheduler/`. For a list of available Aurora flags and their
-documentation, see [Scheduler Configuration Reference](../reference/scheduler-configuration.md).
+documentation, see [Scheduler Configuration Reference](../../reference/scheduler-configuration/).
## A Note on Configuration
@@ -69,7 +69,7 @@ for Mesos replicated log files to ensure
### `-native_log_zk_group_path`
ZooKeeper path used for Mesos replicated log quorum discovery.
-See [code](../../src/main/java/org/apache/aurora/scheduler/log/mesos/MesosLogStreamModule.java) for
+See [code](https://github.com/apache/aurora/blob/rel/0.13.0/src/main/java/org/apache/aurora/scheduler/log/mesos/MesosLogStreamModule.java) for
other available Mesos replicated log configuration options and default values.
### Changing the Quorum Size
@@ -83,7 +83,7 @@ When updating from 3 to 5 schedulers, th
When starting the new schedulers, use the `-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](backup-restore.md).
+[recovering from backup](../backup-restore/).
## Backup Configuration
@@ -112,7 +112,7 @@ argument to the Aurora scheduler):
`both` configuration will send logs to files and stream to parent stdout/stderr outputs.
-See [Configuration Reference](../reference/configuration.md#logger) for all destination options.
+See [Configuration Reference](../../reference/configuration/#logger) for all destination options.
### Log rotation
By default, Thermos will not rotate the stdout/stderr logs from child processes and they will grow
Modified: aurora/site/source/documentation/0.13.0/operations/installation.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/operations/installation.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/operations/installation.md (original)
+++ aurora/site/source/documentation/0.13.0/operations/installation.md Thu Apr 21 15:07:18 2016
@@ -231,7 +231,7 @@ Client configuration lives in a json fil
them. By default this file is at `/etc/aurora/clusters.json`.
Jobs may be submitted to the scheduler using the client, and are described with
-[job configurations](../reference/configuration.md) expressed in `.aurora` files. Typically you will
+[job configurations](../../reference/configuration/) expressed in `.aurora` 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.
Modified: aurora/site/source/documentation/0.13.0/operations/storage.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/operations/storage.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/operations/storage.md (original)
+++ aurora/site/source/documentation/0.13.0/operations/storage.md Thu Apr 21 15:07:18 2016
@@ -37,7 +37,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](backup-restore.md)
+This solves a [disaster recovery problem](../backup-restore/)
in case of a complete loss or corruption of Mesos log files.
Modified: aurora/site/source/documentation/0.13.0/reference/client-cluster-configuration.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/reference/client-cluster-configuration.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/reference/client-cluster-configuration.md (original)
+++ aurora/site/source/documentation/0.13.0/reference/client-cluster-configuration.md Thu Apr 21 15:07:18 2016
@@ -90,4 +90,4 @@ URL of your VIP in a loadbalancer or a r
The identifier of an authentication mechanism that the client should use when communicating with the
scheduler. Support for values other than `UNAUTHENTICATED` requires a matching scheduler-side
-[security configuration](../operations/security.md).
+[security configuration](../../operations/security/).
Modified: aurora/site/source/documentation/0.13.0/reference/client-commands.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/reference/client-commands.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/reference/client-commands.md (original)
+++ aurora/site/source/documentation/0.13.0/reference/client-commands.md Thu Apr 21 15:07:18 2016
@@ -11,7 +11,7 @@ Aurora Client Commands
- [Killing a Job](#killing-a-job)
- [Adding Instances](#adding-instances)
- [Updating a Job](#updating-a-job)
- - [Coordinated job updates](#user-content-coordinated-job-updates)
+ - [Coordinated job updates](#coordinated-job-updates)
- [Renaming a Job](#renaming-a-job)
- [Restarting Jobs](#restarting-jobs)
- [Cron Jobs](#cron-jobs)
@@ -64,7 +64,7 @@ environment variable is not set. The sec
`~/.aurora/clusters.json`.
For more details on cluster configuration see the
-[Client Cluster Configuration](client-cluster-configuration.md) documentation.
+[Client Cluster Configuration](../client-cluster-configuration/) documentation.
Job Keys
--------
@@ -108,7 +108,7 @@ Hooks can be associated with these Auror
- `job restart`
The process for writing and activating them is complex enough
-that we explain it in a devoted document, [Hooks for Aurora Client API](client-hooks.md).
+that we explain it in a devoted document, [Hooks for Aurora Client API](../client-hooks/).
Regular Jobs
------------
@@ -157,7 +157,7 @@ already exists. Use `aurora update start
### Updating a Job
You can manage job updates using the `aurora update` command. Please see
-[the Job Update documentation](../features/job-updates.md) for more details.
+[the Job Update documentation](../../features/job-updates/) for more details.
### Renaming a Job
@@ -212,7 +212,7 @@ Cron Jobs
---------
You can manage cron jobs using the `aurora cron` command. Please see
-[the Cron Jobs Feature](../features/cron-jobs.md) for more details.
+[the Cron Jobs Feature](../../features/cron-jobs/) for more details.
Comparing Jobs
--------------
@@ -247,8 +247,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](../features/constraints.md#dedicated-attribute)
-[production](configuration.md#job-objects) jobs consume quota.
+cluster. Only non-[dedicated](../../features/constraints/#dedicated-attribute)
+[production](../configuration/#job-objects) jobs consume quota.
### Finding a Job on Web UI
Modified: aurora/site/source/documentation/0.13.0/reference/configuration-best-practices.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/reference/configuration-best-practices.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/reference/configuration-best-practices.md (original)
+++ aurora/site/source/documentation/0.13.0/reference/configuration-best-practices.md Thu Apr 21 15:07:18 2016
@@ -57,7 +57,7 @@ limit to 5 and a `min_duration` to 1. Th
into a common process template.
Furthermore, the Python version is repeated everywhere. This can be
-bound via structural templating as described in the [Advanced Binding](configuration-templating.md#AdvancedBinding)
+bound via structural templating as described in the [Advanced Binding](../configuration-templating/#AdvancedBinding)
section.
`less_redundant.aurora` contains:
Modified: aurora/site/source/documentation/0.13.0/reference/configuration-templating.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/reference/configuration-templating.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/reference/configuration-templating.md (original)
+++ aurora/site/source/documentation/0.13.0/reference/configuration-templating.md Thu Apr 21 15:07:18 2016
@@ -5,7 +5,7 @@ The `.aurora` file format is just Python
`Process`, and other classes are defined by a templating library called
*Pystachio*, a powerful tool for configuration specification and reuse.
-[Aurora Configuration Reference](configuration.md)
+[Aurora Configuration Reference](../configuration/)
has a full reference of all Aurora/Thermos defined Pystachio objects.
When writing your `.aurora` file, you may use any Pystachio datatypes, as
Modified: aurora/site/source/documentation/0.13.0/reference/configuration-tutorial.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/reference/configuration-tutorial.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/reference/configuration-tutorial.md (original)
+++ aurora/site/source/documentation/0.13.0/reference/configuration-tutorial.md Thu Apr 21 15:07:18 2016
@@ -7,19 +7,19 @@ and best practices. When writing a confi
arguments as `aurora job create` or `aurora update start`. It first ensures the
configuration parses, then outputs it in human-readable form.
-You should read this after going through the general [Aurora Tutorial](../getting-started/tutorial.md).
+You should read this after going through the general [Aurora Tutorial](../../getting-started/tutorial/).
-- [The Basics](#user-content-the-basics)
- - [Use Bottom-To-Top Object Ordering](#user-content-use-bottom-to-top-object-ordering)
-- [An Example Configuration File](#user-content-an-example-configuration-file)
-- [Defining Process Objects](#user-content-defining-process-objects)
-- [Getting Your Code Into The Sandbox](#user-content-getting-your-code-into-the-sandbox)
-- [Defining Task Objects](#user-content-defining-task-objects)
- - [SequentialTask: Running Processes in Parallel or Sequentially](#user-content-sequentialtask-running-processes-in-parallel-or-sequentially)
- - [SimpleTask](#user-content-simpletask)
- - [Combining tasks](#user-content-combining-tasks)
-- [Defining Job Objects](#user-content-defining-job-objects)
-- [The jobs List](#user-content-the-jobs-list)
+- [The Basics](#the-basics)
+ - [Use Bottom-To-Top Object Ordering](#use-bottom-to-top-object-ordering)
+- [An Example Configuration File](#an-example-configuration-file)
+- [Defining Process Objects](#defining-process-objects)
+- [Getting Your Code Into The Sandbox](#getting-your-code-into-the-sandbox)
+- [Defining Task Objects](#defining-task-objects)
+ - [SequentialTask: Running Processes in Parallel or Sequentially](#sequentialtask-running-processes-in-parallel-or-sequentially)
+ - [SimpleTask](#simpletask)
+ - [Combining tasks](#combining-tasks)
+- [Defining Job Objects](#defining-job-objects)
+- [The jobs List](#the-jobs-list)
- [Basic Examples](#basic-examples)
@@ -53,11 +53,11 @@ via {{}} surrounded templates.
When writing your `.aurora` file, you may use any Pystachio datatypes, as
well as any objects shown in the [*Aurora Configuration
-Reference*](configuration.md), without `import` statements - the
+Reference*](../configuration/), without `import` statements - the
Aurora config loader injects them automatically. Other than that, an `.aurora`
file works like any other Python script.
-[*Aurora Configuration Reference*](configuration.md)
+[*Aurora Configuration Reference*](../configuration/)
has a full reference of all Aurora/Thermos defined Pystachio objects.
### Use Bottom-To-Top Object Ordering
@@ -215,7 +215,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 Configuration Reference](configuration.md#process-objects).
+`Process` also has optional attributes to customize its behaviour. Details can be found in the [Aurora Configuration Reference](../configuration/#process-objects).
## Getting Your Code Into The Sandbox
@@ -276,7 +276,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 Configuration Reference](configuration.md#task-object)
+A Task has optional attributes to customize its behaviour. Details can be found in the [Aurora Configuration Reference](../configuration/#task-object)
### SequentialTask: Running Processes in Parallel or Sequentially
@@ -433,7 +433,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 Configuration Reference](configuration.md#job-objects).
+attributes. Details can be found in the [Aurora Configuration Reference](../configuration/#job-objects).
## The jobs List
Modified: aurora/site/source/documentation/0.13.0/reference/configuration.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/reference/configuration.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/reference/configuration.md (original)
+++ aurora/site/source/documentation/0.13.0/reference/configuration.md Thu Apr 21 15:07:18 2016
@@ -6,8 +6,8 @@ powerful, and configurations can become
cases.
For examples of simple configurations to get something up and running
-quickly, check out the [Tutorial](../getting-started/tutorial.md). When you feel comfortable with the basics, move
-on to the [Configuration Tutorial](configuration-tutorial.md) for more in-depth coverage of
+quickly, check out the [Tutorial](../../getting-started/tutorial/). When you feel comfortable with the basics, move
+on to the [Configuration Tutorial](../configuration-tutorial/) for more in-depth coverage of
configuration design.
- [Process Schema](#process-schema)
@@ -313,7 +313,7 @@ ordering constraints.
### Resource Object
Specifies the amount of CPU, Ram, and disk resources the task needs. See the
-[Resource Isolation document](../features/resource-isolation.md) for suggested values and to understand how
+[Resource Isolation document](../../features/resource-isolation/) for suggested values and to understand how
resources are allocated.
param | type | description
@@ -337,14 +337,14 @@ Job Schema
```environment``` | String | Job environment, default ```devel```. Must be one of ```prod```, ```devel```, ```test``` or ```staging<number>```.
```contact``` | String | Best email address to reach the owner of the job. For production jobs, this is usually a team mailing list.
```instances```| Integer | Number of instances (sometimes referred to as replicas or shards) of the task to create. (Default: 1)
- ```cron_schedule``` | String | Cron schedule in cron format. May only be used with non-service jobs. See [Cron Jobs](../features/cron-jobs.md) for more information. Default: None (not a cron job.)
+ ```cron_schedule``` | String | Cron schedule in cron format. May only be used with non-service jobs. See [Cron Jobs](../../features/cron-jobs/) for more information. Default: None (not a cron job.)
```cron_collision_policy``` | String | Policy to use when a cron job is triggered while a previous run is still active. KILL_EXISTING Kill the previous run, and schedule the new run CANCEL_NEW Let the previous run continue, and cancel the new run. (Default: KILL_EXISTING)
```update_config``` | ```UpdateConfig``` object | Parameters for controlling the rate and policy of rolling updates.
```constraints``` | dict | Scheduling constraints for the tasks. See the section on the [constraint specification language](#specifying-scheduling-constraints)
```service``` | Boolean | If True, restart tasks regardless of success or failure. (Default: False)
```max_task_failures``` | Integer | Maximum number of failures after which the task is considered to have failed (Default: 1) Set to -1 to allow for infinite failures
```priority``` | Integer | Preemption priority to give the task (Default 0). Tasks with higher priorities may preempt tasks at lower priorities.
- ```production``` | Boolean | Whether or not this is a production task that may [preempt](../features/multitenancy.md#preemption) other tasks (Default: False). Production job role must have the appropriate [quota](../features/multitenancy.md#preemption).
+ ```production``` | Boolean | Whether or not this is a production task that may [preempt](../../features/multitenancy/#preemption) other tasks (Default: False). Production job role must have the appropriate [quota](../../features/multitenancy/#preemption).
```health_check_config``` | ```HealthCheckConfig``` object | Parameters for controlling a task's health checks. HTTP health check is 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.
@@ -363,7 +363,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](../features/job-updates.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](../../features/job-updates/#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
@@ -404,13 +404,13 @@ If the `announce` field in the Job confi
registered in the ServerSet `/aurora/role/environment/jobname` in the
zookeeper ensemble configured by the executor (which can be optionally overriden by specifying
`zk_path` parameter). If no Announcer object is specified,
-no announcement will take place. For more information about ServerSets, see the [Service Discover](../features/service-discovery.md)
+no announcement will take place. For more information about ServerSets, see the [Service Discover](../../features/service-discovery/)
documentation.
By default, the hostname in the registered endpoints will be the `--hostname` parameter
that is passed to the mesos slave. To override the hostname value, the executor can be started
with `--announcer-hostname=<overriden_value>`. If you decide to use `--announcer-hostname` and if
-the overriden value needs to change for every executor, then the executor has to be started inside a wrapper, see [Executor Wrapper](../operations/configuration.md#thermos-executor-wrapper).
+the overriden value needs to change for every executor, then the executor has to be started inside a wrapper, see [Executor Wrapper](../../operations/configuration/#thermos-executor-wrapper).
For example, if you want the hostname in the endpoint to be an IP address instead of the hostname,
the `--hostname` parameter to the mesos slave can be set to the machine IP or the executor can
@@ -524,7 +524,7 @@ constraints*.
| Limit | A string that specifies a limit for a constraint. Starts with <code>'limit:</code> followed by an Integer and closing single quote, such as ```'limit:1'```.
| Value | A string that specifies a value for a constraint. To include a list of values, separate the values using commas. To negate the values of a constraint, start with a ```!``` ```.```
-Further details can be found in the [Scheduling Constraints](../features/constraints.md) feature
+Further details can be found in the [Scheduling Constraints](../../features/constraints/) feature
description.
Modified: aurora/site/source/documentation/0.13.0/reference/scheduler-configuration.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/0.13.0/reference/scheduler-configuration.md?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/source/documentation/0.13.0/reference/scheduler-configuration.md (original)
+++ aurora/site/source/documentation/0.13.0/reference/scheduler-configuration.md Thu Apr 21 15:07:18 2016
@@ -3,7 +3,7 @@
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 `aurora-scheduler -help`.
-Please refer to the [Operator Configuration Guide](../operations/configuration.md) for details on how
+Please refer to the [Operator Configuration Guide](../../operations/configuration/) for details on how
to properly set the most important options.
```