Return-Path: X-Original-To: apmail-aurora-commits-archive@minotaur.apache.org Delivered-To: apmail-aurora-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C67C219B8C for ; Thu, 21 Apr 2016 15:07:34 +0000 (UTC) Received: (qmail 86535 invoked by uid 500); 21 Apr 2016 15:07:34 -0000 Delivered-To: apmail-aurora-commits-archive@aurora.apache.org Received: (qmail 86499 invoked by uid 500); 21 Apr 2016 15:07:34 -0000 Mailing-List: contact commits-help@aurora.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.apache.org Delivered-To: mailing list commits@aurora.apache.org Received: (qmail 86489 invoked by uid 99); 21 Apr 2016 15:07:34 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Apr 2016 15:07:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 08A61180505 for ; Thu, 21 Apr 2016 15:07:34 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.809 X-Spam-Level: * X-Spam-Status: No, score=1.809 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id drJmjcxY_VRF for ; Thu, 21 Apr 2016 15:07:21 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTP id 428DF5F1D5 for ; Thu, 21 Apr 2016 15:07:21 +0000 (UTC) Received: from svn01-us-west.apache.org (svn.apache.org [10.41.0.6]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5D093E0316 for ; Thu, 21 Apr 2016 15:07:20 +0000 (UTC) Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id B517B3A01D7 for ; Thu, 21 Apr 2016 15:07:19 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1740340 [1/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... Date: Thu, 21 Apr 2016 15:07:18 -0000 To: commits@aurora.apache.org From: wfarner@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20160421150719.B517B3A01D7@svn01-us-west.apache.org> Author: wfarner Date: Thu Apr 21 15:07:18 2016 New Revision: 1740340 URL: http://svn.apache.org/viewvc?rev=1740340&view=rev Log: Generate 0.13.0 documentation under the 0.13.0 tag in addition to latest. Added: aurora/site/publish/documentation/0.13.0/contributing/ aurora/site/publish/documentation/0.13.0/contributing/index.html aurora/site/source/documentation/0.13.0/contributing.md Modified: aurora/site/publish/documentation/0.13.0/additional-resources/tools/index.html aurora/site/publish/documentation/0.13.0/development/db-migration/index.html aurora/site/publish/documentation/0.13.0/development/design-documents/index.html aurora/site/publish/documentation/0.13.0/development/thermos/index.html aurora/site/publish/documentation/0.13.0/development/thrift/index.html aurora/site/publish/documentation/0.13.0/features/constraints/index.html aurora/site/publish/documentation/0.13.0/features/containers/index.html aurora/site/publish/documentation/0.13.0/features/cron-jobs/index.html aurora/site/publish/documentation/0.13.0/features/job-updates/index.html aurora/site/publish/documentation/0.13.0/features/multitenancy/index.html aurora/site/publish/documentation/0.13.0/features/resource-isolation/index.html aurora/site/publish/documentation/0.13.0/features/service-discovery/index.html aurora/site/publish/documentation/0.13.0/features/services/index.html aurora/site/publish/documentation/0.13.0/features/sla-metrics/index.html aurora/site/publish/documentation/0.13.0/getting-started/overview/index.html aurora/site/publish/documentation/0.13.0/getting-started/tutorial/index.html aurora/site/publish/documentation/0.13.0/getting-started/vagrant/index.html aurora/site/publish/documentation/0.13.0/index.html aurora/site/publish/documentation/0.13.0/operations/backup-restore/index.html aurora/site/publish/documentation/0.13.0/operations/configuration/index.html aurora/site/publish/documentation/0.13.0/operations/installation/index.html aurora/site/publish/documentation/0.13.0/operations/storage/index.html aurora/site/publish/documentation/0.13.0/reference/client-cluster-configuration/index.html aurora/site/publish/documentation/0.13.0/reference/client-commands/index.html aurora/site/publish/documentation/0.13.0/reference/configuration-best-practices/index.html aurora/site/publish/documentation/0.13.0/reference/configuration-templating/index.html aurora/site/publish/documentation/0.13.0/reference/configuration-tutorial/index.html aurora/site/publish/documentation/0.13.0/reference/configuration/index.html aurora/site/publish/documentation/0.13.0/reference/scheduler-configuration/index.html aurora/site/publish/sitemap.xml aurora/site/source/documentation/0.13.0/additional-resources/tools.md aurora/site/source/documentation/0.13.0/development/db-migration.md aurora/site/source/documentation/0.13.0/development/design-documents.md aurora/site/source/documentation/0.13.0/development/thermos.md aurora/site/source/documentation/0.13.0/development/thrift.md aurora/site/source/documentation/0.13.0/features/constraints.md aurora/site/source/documentation/0.13.0/features/containers.md aurora/site/source/documentation/0.13.0/features/cron-jobs.md aurora/site/source/documentation/0.13.0/features/job-updates.md aurora/site/source/documentation/0.13.0/features/multitenancy.md aurora/site/source/documentation/0.13.0/features/resource-isolation.md aurora/site/source/documentation/0.13.0/features/service-discovery.md aurora/site/source/documentation/0.13.0/features/services.md aurora/site/source/documentation/0.13.0/features/sla-metrics.md aurora/site/source/documentation/0.13.0/getting-started/overview.md aurora/site/source/documentation/0.13.0/getting-started/tutorial.md aurora/site/source/documentation/0.13.0/getting-started/vagrant.md aurora/site/source/documentation/0.13.0/index.html.md aurora/site/source/documentation/0.13.0/operations/backup-restore.md aurora/site/source/documentation/0.13.0/operations/configuration.md aurora/site/source/documentation/0.13.0/operations/installation.md aurora/site/source/documentation/0.13.0/operations/storage.md aurora/site/source/documentation/0.13.0/reference/client-cluster-configuration.md aurora/site/source/documentation/0.13.0/reference/client-commands.md aurora/site/source/documentation/0.13.0/reference/configuration-best-practices.md aurora/site/source/documentation/0.13.0/reference/configuration-templating.md aurora/site/source/documentation/0.13.0/reference/configuration-tutorial.md aurora/site/source/documentation/0.13.0/reference/configuration.md aurora/site/source/documentation/0.13.0/reference/scheduler-configuration.md Modified: aurora/site/publish/documentation/0.13.0/additional-resources/tools/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/additional-resources/tools/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff ============================================================================== --- aurora/site/publish/documentation/0.13.0/additional-resources/tools/index.html (original) +++ aurora/site/publish/documentation/0.13.0/additional-resources/tools/index.html Thu Apr 21 15:07:18 2016 @@ -92,7 +92,7 @@
  • aurproxy based on nginx
  • jobhopper performs HTTP redirects for easy developer and administrator access
    • -

  • RPC libraries that integrate with the Aurora’s service discovery mechanism:

    +

  • RPC libraries that integrate with the Aurora’s service discovery mechanism:

    • linkerd RPC proxy
      • Added: aurora/site/publish/documentation/0.13.0/contributing/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/contributing/index.html?rev=1740340&view=auto ============================================================================== --- aurora/site/publish/documentation/0.13.0/contributing/index.html (added) +++ aurora/site/publish/documentation/0.13.0/contributing/index.html Thu Apr 21 15:07:18 2016 @@ -0,0 +1,209 @@ + + + + + + Apache Aurora + + + + + + +
      +
      +
      + Transparent Apache Aurora logo with dark background + +
      +
      +
      + +
      +
      +
      +
      Documentation + +
      +

      Get the Source Code

      + +

      First things first, you’ll need the source! The Aurora source is available from Apache git:

      +
      git clone https://git-wip-us.apache.org/repos/asf/aurora
+
      + +

      Read the Style Guides

      + +

      Aurora’s codebase is primarily Java and Python and conforms to the Twitter Commons styleguides for +both languages.

      + + + +

      Find Something to Do

      + +

      There are issues in Jira with the +“newbie” label +that are good starting places for new Aurora contributors; pick one of these and dive in! Once +you’ve got a patch, the next step is to post a review.

      + +

      Getting your ReviewBoard Account

      + +

      Go to https://reviews.apache.org and create an account.

      + +

      Setting up your ReviewBoard Environment

      + +

      Run ./rbt status. The first time this runs it will bootstrap and you will be asked to login. +Subsequent runs will cache your login credentials.

      + +

      Submitting a Patch for Review

      + +

      Post a review with rbt, fill out the fields in your browser and hit Publish.

      +
      ./rbt post -o
+
      + +

      If you’re unsure about who to add as a reviewer, you can default to adding Bill Farner (wfarner) and +Joshua Cohen (jcohen). They will take care of finding an appropriate reviewer for the patch.

      + +

      Once you’ve done this, you probably want to mark the associated Jira issue as Reviewable.

      + +

      Updating an Existing Review

      + +

      Incorporate review feedback, make some more commits, update your existing review, fill out the +fields in your browser and hit Publish.

      +
      ./rbt post -o -r <RB_ID>
+
      + +

      Getting Your Review Merged

      + +

      If you’re not an Aurora committer, one of the committers will merge your change in as described +below. Generally, the last reviewer to give the review a ‘Ship It!’ will be responsible.

      + +

      Merging Your Own Review (Committers)

      + +

      Once you have shipits from the right committers, merge your changes in a single commit and mark +the review as submitted. The typical workflow is:

      +
      git checkout master
+git pull origin master
+./rbt patch -c <RB_ID>  # Verify the automatically-generated commit message looks sane,
+                        # editing if necessary.
+git show master         # Verify everything looks sane
+git push origin master
+./rbt close <RB_ID>
+
      + +

      Note that even if you’re developing using feature branches you will not use git merge - each +commit will be an atomic change accompanied by a ReviewBoard entry.

      + +

      Merging Someone Else’s Review

      + +

      Sometimes you’ll need to merge someone else’s RB. The typical workflow for this is

      +
      git checkout master
+git pull origin master
+./rbt patch -c <RB_ID>
+git show master  # Verify everything looks sane, author is correct
+git push origin master
+
      + +

      Note for committers: while we generally use the commit message generated by ./rbt patch some +changes are often required:

      + +
        +
      1. Ensure the the commit message does not exceed 100 characters per line.
        2. +
      2. Remove the “Testing Done” section. It’s generally redundant (can be seen by checking the linked +review) or entirely irrelevant to the commit itself.
        3. +
      + +

      Cleaning Up

      + +

      Your patch has landed, congratulations! The last thing you’ll want to do before moving on to your +next fix is to clean up your Jira and Reviewboard. The former of which should be marked as +“Resolved” while the latter should be marked as “Submitted”.

      + +
      + +
      +
      +
      +
      +
      +

      Quick Links

      + +
      +

      The ASF

      + +
      +
      +

      Copyright 2014 Apache Software Foundation. Licensed under the Apache License v2.0. The Aurora Borealis IX photo displayed on the homepage is available under a Creative Commons BY-NC-ND 2.0 license. Apache, Apache Aurora, and the Apache feather logo are trademarks of The Apache Software Foundation.

      +
      +
      +
      + + + Modified: aurora/site/publish/documentation/0.13.0/development/db-migration/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/development/db-migration/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff ============================================================================== --- aurora/site/publish/documentation/0.13.0/development/db-migration/index.html (original) +++ aurora/site/publish/documentation/0.13.0/development/db-migration/index.html Thu Apr 21 15:07:18 2016 @@ -94,7 +94,7 @@ a snapshot is restored, no manual intera

      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 -interface (see V001_TestMigration +interface (see V001_TestMigration as an example). The upgrade and downgrade scripts are defined in this class. When restoring a snapshot the list of migrations on the classpath is compared to the list of applied changes in the DB. Any changes that have not yet been applied are executed and their downgrade script is stored Modified: aurora/site/publish/documentation/0.13.0/development/design-documents/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/development/design-documents/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff ============================================================================== --- aurora/site/publish/documentation/0.13.0/development/design-documents/index.html (original) +++ aurora/site/publish/documentation/0.13.0/development/design-documents/index.html Thu Apr 21 15:07:18 2016 @@ -90,7 +90,7 @@ in the proposed form.

      Current and past documents:

        -
      • Command Hooks for the Aurora Client
        • +
      • Command Hooks for the Aurora Client
      • Health Checks for Updates
      • JobUpdateDiff thrift API
      • REST API RFC
        • Modified: aurora/site/publish/documentation/0.13.0/development/thermos/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/development/thermos/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff ============================================================================== --- aurora/site/publish/documentation/0.13.0/development/thermos/index.html (original) +++ aurora/site/publish/documentation/0.13.0/development/thermos/index.html Thu Apr 21 15:07:18 2016 @@ -196,7 +196,7 @@ that would undermine the goal of ensurin

        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 that exercises the feature, and +job 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/publish/documentation/0.13.0/development/thrift/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/development/thrift/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff ============================================================================== --- aurora/site/publish/documentation/0.13.0/development/thrift/index.html (original) +++ aurora/site/publish/documentation/0.13.0/development/thrift/index.html Thu Apr 21 15:07:18 2016 @@ -87,7 +87,7 @@ client/server RPC protocol as well as fo correctly handling additions and renames of the existing members, field removals must be done carefully to ensure backwards compatibility and provide predictable deprecation cycle. This document describes general guidelines for making Thrift schema changes to the existing fields in -api.thrift.

        +api.thrift.

        It is highly recommended to go through the Thrift: The Missing Guide first to refresh on @@ -115,9 +115,9 @@ communicate with scheduler/client from v * Add a new field as an eventual replacement of the old one and implement a dual read/write anywhere the old field is used. If a thrift struct is mapped in the DB store make sure both columns are marked as NOT NULL -* Check storage.thrift to see if +* Check 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. +necessary to perform a DB migration. * Add a deprecation jira ticket into the vCurrent+1 release candidate * Add a TODO for the deprecated field mentioning the jira ticket

        @@ -132,7 +132,7 @@ necessary to perform a this document +client/scheduler versions by playing with aurorabuild command. See this document for more.

      Modified: aurora/site/publish/documentation/0.13.0/features/constraints/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/constraints/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff ============================================================================== --- aurora/site/publish/documentation/0.13.0/features/constraints/index.html (original) +++ aurora/site/publish/documentation/0.13.0/features/constraints/index.html Thu Apr 21 15:07:18 2016 @@ -126,7 +126,7 @@ most one task per rack:

      Use these constraints sparingly as they can dramatically reduce Tasks’ schedulability. Further details are available in the reference documentation on -Scheduling Constraints.

      +Scheduling Constraints.

      Value Constraints

      @@ -144,7 +144,7 @@ scheduled on nodes that claim to have an

      Further details are available in the reference documentation on -Scheduling Constraints.

      +Scheduling Constraints.

      Running stateful services

      Modified: aurora/site/publish/documentation/0.13.0/features/containers/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/containers/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff ============================================================================== --- aurora/site/publish/documentation/0.13.0/features/containers/index.html (original) +++ aurora/site/publish/documentation/0.13.0/features/containers/index.html Thu Apr 21 15:07:18 2016 @@ -84,9 +84,9 @@

      Docker

      -

      Aurora has optional support for launching Docker containers, if correctly configured by an Operator.

      +

      Aurora has optional support for launching Docker containers, if correctly configured by an Operator.

      -

      Example (available in the Vagrant environment):

      +

      Example (available in the Vagrant environment):

      $ cat /vagrant/examples/jobs/docker/hello_docker.aurora
 hello_docker = Process(
   name = 'hello',
@@ -117,7 +117,7 @@ jobs = [
 
 
      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 Documentation.
      
 
 
 

Modified: aurora/site/publish/documentation/0.13.0/features/cron-jobs/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/cron-jobs/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/features/cron-jobs/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/features/cron-jobs/index.html Thu Apr 21 15:07:18 2016
@@ -110,11 +110,11 @@
 
 
      A job is identified as a cron job by the presence of a
 cron_schedule attribute containing a cron-style schedule in the
-Job object. Examples of cron schedules
+Job 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):
      
+
      Example (available in the Vagrant environment):
      
 
      $ cat /vagrant/examples/jobs/cron_hello_world.aurora
 # A cron job that runs every 5 minutes.
 jobs = [
@@ -150,7 +150,7 @@ grow faster than they can process it.
      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 object. To get “run-until-success” semantics,
+Task object. To get “run-until-success” semantics,
 set max_task_failures to -1.
      
 
 
      Interacting with cron jobs via the Aurora CLI
      

Modified: aurora/site/publish/documentation/0.13.0/features/job-updates/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/job-updates/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/features/job-updates/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/features/job-updates/index.html Thu Apr 21 15:07:18 2016
@@ -141,7 +141,7 @@ from the point where the update failed.
 8-FAIL) results in a rollback in order (8,7,6) (5,4,3) (2,1,0).
      
 
 
      For details how to control a job update, please see the
-UpdateConfig configuration object.
      
+UpdateConfig configuration object.
      
 
 
      Coordinated Job Updates
      
 
@@ -150,10 +150,10 @@ acknowledging (“heartbeating&rdquo
 service updates where explicit job health monitoring is vital during the entire job update
 lifecycle. Such job updates would rely on an external service (or a custom client) periodically
 pulsing an active coordinated job update via a
-pulseJobUpdate RPC.
      
+pulseJobUpdate RPC.
      
 
 
      A coordinated update is defined by setting a positive
-pulseintervalsecs value in job configuration
+pulseintervalsecs 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/publish/documentation/0.13.0/features/multitenancy/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/multitenancy/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/features/multitenancy/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/features/multitenancy/index.html Thu Apr 21 15:07:18 2016
@@ -83,7 +83,7 @@
 
      Multitenancy
      
 
 
      Aurora is a multi-tenant system that can run jobs of multiple clients/tenants.
-Going beyond the resource isolation on an individual host, it is
+Going beyond the resource isolation on an individual host, it is
 crucial to prevent those jobs from stepping on each others toes.
      
 
 
      Job Namespaces
      
@@ -100,7 +100,7 @@ to differentiate between different jobs.

    Role names correspond to user accounts. They are used for -authentication, as the linux user used to run jobs, and for the +authentication, as the linux user used to run jobs, and for the assignment of quota. If you don’t know what accounts are available, contact your sysadmin.

    @@ -124,20 +124,20 @@ prevents this. Active tasks can become t -

    In other words, tasks from production jobs may preempt +

    In other words, tasks from production 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.

    +production jobs in the same role with higher priority.

    -

    Aurora requires resource quotas for production non-dedicated jobs. +

    Aurora requires resource quotas for production non-dedicated jobs. 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.

    +dedicated constraint set.

    To grant quota to a particular role in production, an operator can use the command aurora_admin set_quota.

    Modified: aurora/site/publish/documentation/0.13.0/features/resource-isolation/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/resource-isolation/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff ============================================================================== --- aurora/site/publish/documentation/0.13.0/features/resource-isolation/index.html (original) +++ aurora/site/publish/documentation/0.13.0/features/resource-isolation/index.html Thu Apr 21 15:07:18 2016 @@ -237,11 +237,11 @@ jobs. If not configured properly revocab 
    -receive_revocable_resources=true
    -

    Specify a tier configuration file path (unless you want to use the default):

    +

    Specify a tier configuration file path (unless you want to use the default):

    -tier_config=path/to/tiers/config.json
    -

    See the Configuration Reference for details on how to mark a job +

    See the Configuration Reference for details on how to mark a job as being revocable.

    Modified: aurora/site/publish/documentation/0.13.0/features/service-discovery/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/service-discovery/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff ============================================================================== --- aurora/site/publish/documentation/0.13.0/features/service-discovery/index.html (original) +++ aurora/site/publish/documentation/0.13.0/features/service-discovery/index.html Thu Apr 21 15:07:18 2016 @@ -94,7 +94,7 @@ of which there are several reference imp

    These can also be used natively in Finagle using the ZookeeperServerSetCluster.

    -

    For more information about how to configure announcing, see the Configuration Reference.

    +

    For more information about how to configure announcing, see the Configuration Reference.

    Using Mesos DiscoveryInfo

    Modified: aurora/site/publish/documentation/0.13.0/features/services/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/services/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff ============================================================================== --- aurora/site/publish/documentation/0.13.0/features/services/index.html (original) +++ aurora/site/publish/documentation/0.13.0/features/services/index.html Thu Apr 21 15:07:18 2016 @@ -89,10 +89,10 @@ such as webservices that should always b

    Service Specification

    A job is identified as a service by the presence of the flag -`service=True in the Job object. +`service=True in the Job object. The Service alias can be used as shorthand for Job with service=True.

    -

    Example (available in the Vagrant environment):

    +

    Example (available in the Vagrant environment):

    $ cat /vagrant/examples/jobs/hello_world.aurora
 hello = Process(
   name = 'hello',
@@ -121,12 +121,12 @@ jobs = [
 
 
    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 object for details).
    
+Job 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 that
+usecase via the thermos.ports namespace that
 allows to request arbitrarily named ports:
    
 
    nginx = Process(
   name = 'nginx',
@@ -142,7 +142,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 documentation.
    
+Service Discovery documentation.
    
 
 
    Health Checking
    
 
@@ -159,7 +159,7 @@ via repeated calls to the /health<
 
    
 
 
    Please see the
-configuration reference
+configuration reference
 for configuration options for this feature.
    
 
 
    You can pause health checking by touching a file inside of your sandbox, named .healthchecksnooze.

Modified: aurora/site/publish/documentation/0.13.0/features/sla-metrics/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/features/sla-metrics/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/features/sla-metrics/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/features/sla-metrics/index.html Thu Apr 21 15:07:18 2016
@@ -149,7 +149,7 @@ relevant to uptime calculations. By appl
 transition records, we can build a deterministic downtime trace for every given service instance.
    
 
 
    A task going through a state transition carries one of three possible SLA meanings
-(see SlaAlgorithm.java for
+(see SlaAlgorithm.java for
 sla-to-task-state mapping):
    
 
 
      
@@ -199,7 +199,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
+ResourceAggregates.java
 
 
        
 
      • By CPU:
        • 
@@ -240,7 +240,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
+ResourceAggregates.java
 
 
          
 
        • By CPU:
          • 

Modified: aurora/site/publish/documentation/0.13.0/getting-started/overview/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/getting-started/overview/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/getting-started/overview/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/getting-started/overview/index.html Thu Apr 21 15:07:18 2016
@@ -120,7 +120,7 @@ directories.
          
 
        • ZooKeeper
 ZooKeeper 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
          • 
+used as a vehicle for service discovery, see Service Discovery
          
 
        • Mesos master
 The master is responsible for tracking worker machines and performing accounting of their
 resources.  The scheduler interfaces with the master to control the cluster.
          • 

Modified: aurora/site/publish/documentation/0.13.0/getting-started/tutorial/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/getting-started/tutorial/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/getting-started/tutorial/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/getting-started/tutorial/index.html Thu Apr 21 15:07:18 2016
@@ -98,9 +98,9 @@ to start getting up to speed on the syst
 
 
          Prerequisite
          
 
-
          This tutorial assumes you are running Aurora locally using Vagrant.
+
          This tutorial assumes you are running Aurora locally using Vagrant.
 However, in general the instructions are also applicable to any other
-Aurora installation.
          
+Aurora installation.
          
 
 
          Unless otherwise stated, all commands are to be run from the root of the aurora
 repository clone.
          
@@ -186,8 +186,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 and the Configuration
+
          For more about Aurora configuration files, see the Configuration
+Tutorial and the Configuration
 Reference (preferably after finishing this
 tutorial).
          
 
@@ -214,7 +214,7 @@ don’t know what accounts are avail
 its counterpart in the other key, then the two job keys identify two separate
 jobs. If all four values are identical, the job keys identify the same job.
          
 
-
          The clusters.json client configuration
+
          The clusters.json client configuration
 for the Aurora scheduler defines the available cluster names.
 For Vagrant, from the top-level of your Aurora repository clone, do:
          
 
          $ vagrant ssh
@@ -331,11 +331,11 @@ Job killall succeeded
 
          Now that you’ve finished this Tutorial, you should read or do the following:
          
 
 
 
 

Modified: aurora/site/publish/documentation/0.13.0/getting-started/vagrant/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/getting-started/vagrant/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/getting-started/vagrant/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/getting-started/vagrant/index.html Thu Apr 21 15:07:18 2016
@@ -89,15 +89,15 @@ the steps outlined here, you will be rea
 
          The following sections describe these steps in detail:
          
 
 
            
-
          1. Overview
            2. 
-
          2. Install VirtualBox and Vagrant
            3. 
-
          3. Clone the Aurora repository
            4. 
-
          4. Start the local cluster
            5. 
-
          5. Log onto the VM
            6. 
-
          6. Run your first job
            7. 
-
          7. Rebuild components
            8. 
-
          8. Shut down or delete your local cluster
            9. 
-
          9. Troubleshooting
            10. 
+
          10. Overview
            11. 
+
          11. Install VirtualBox and Vagrant
            12. 
+
          12. Clone the Aurora repository
            13. 
+
          13. Start the local cluster
            14. 
+
          14. Log onto the VM
            15. 
+
          15. Run your first job
            16. 
+
          16. Rebuild components
            17. 
+
          17. Shut down or delete your local cluster
            18. 
+
          18. Troubleshooting
            19. 
 
          
 
 
          Overview
          
@@ -175,7 +175,7 @@ will use in client commands.
          
 
          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.
          
+For more information, see the Aurora Tutorial.
          
 
 
          Rebuild components
          
 

Modified: aurora/site/publish/documentation/0.13.0/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/index.html Thu Apr 21 15:07:18 2016
@@ -94,9 +94,9 @@ the #aurora IRC channel on
 
          Information for everyone new to Apache Aurora.
          
 
 
 
 
          Features
          
@@ -104,15 +104,15 @@ the #aurora IRC channel on
 
          Description of important Aurora features.
          
 
 
 
 
          Operators
          
@@ -120,12 +120,12 @@ the #aurora IRC channel on
 
          For those that wish to manage and fine-tune an Aurora cluster.
          
 
 
 
 
          Reference
          
@@ -133,30 +133,30 @@ the #aurora IRC channel on
 
          The complete reference of commands, configuration options, and scheduler internals.
          
 
 
 
 
          Additional Resources
          
 
 
 
 
          Developers
          
@@ -165,16 +165,16 @@ the #aurora IRC channel on
 
 
 

Modified: aurora/site/publish/documentation/0.13.0/operations/backup-restore/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/operations/backup-restore/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/operations/backup-restore/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/operations/backup-restore/index.html Thu Apr 21 15:07:18 2016
@@ -97,7 +97,7 @@ be killed shortly after the cluster rest
 hours). This is because the scheduler will expect the cluster to look exactly as the backup does,
 so any tasks that have been rescheduled since the backup was taken will be killed.
          
 
-
          Instructions below have been verified in Vagrant environment and with minor
+
          Instructions below have been verified in Vagrant environment and with minor
 syntax/path changes should be applicable to any Aurora cluster.
          
 
 
          Preparation
          
@@ -114,7 +114,7 @@ be erased after the backup snapshot is r
 Restore from backup section locally on the leading scheduler:
          
 
 
            
-
          • Make sure the clusters.json file configured to
+
          • Make sure the clusters.json 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/publish/documentation/0.13.0/operations/configuration/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/operations/configuration/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/operations/configuration/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/operations/configuration/index.html Thu Apr 21 15:07:18 2016
@@ -84,7 +84,7 @@
 
 
            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.
            
+documentation, see Scheduler Configuration Reference.
            
 
 
            A Note on Configuration
            
 
@@ -170,7 +170,7 @@ for Mesos replicated log files to ensure
 
 
            ZooKeeper path used for Mesos replicated log quorum discovery.
            
 
-
            See code for
+
            See code for
 other available Mesos replicated log configuration options and default values.
            
 
 
            Changing the Quorum Size
            
@@ -185,7 +185,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.
            
+recovering from backup.
            
 
 
            Backup Configuration
            
 
@@ -216,7 +216,7 @@ argument to the Aurora scheduler):
            
 
 
            both configuration will send logs to files and stream to parent stdout/stderr outputs.
            
 
-
            See Configuration Reference for all destination options.
            
+
            See Configuration Reference for all destination options.
            
 
 
            Log rotation
            
 

Modified: aurora/site/publish/documentation/0.13.0/operations/installation/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/operations/installation/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/operations/installation/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/operations/installation/index.html Thu Apr 21 15:07:18 2016
@@ -323,7 +323,7 @@ brew install aurora-cli
 them.  By default this file is at /etc/aurora/clusters.json.
            
 
 
            Jobs may be submitted to the scheduler using the client, and are described with
-job configurations expressed in .aurora files.  Typically you will
+job configurations 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/publish/documentation/0.13.0/operations/storage/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/operations/storage/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/operations/storage/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/operations/storage/index.html Thu Apr 21 15:07:18 2016
@@ -126,7 +126,7 @@ is disaster recovery problem
+This solves a disaster recovery problem
 in case of a complete loss or corruption of Mesos log files.
            • 
 
          
 

Modified: aurora/site/publish/documentation/0.13.0/reference/client-cluster-configuration/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/client-cluster-configuration/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/reference/client-cluster-configuration/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/reference/client-cluster-configuration/index.html Thu Apr 21 15:07:18 2016
@@ -211,7 +211,7 @@ URL of your VIP in a loadbalancer or a r
 
 
          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.
          
+security configuration.
          
 
 
 

Modified: aurora/site/publish/documentation/0.13.0/reference/client-commands/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/client-commands/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/reference/client-commands/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/reference/client-commands/index.html Thu Apr 21 15:07:18 2016
@@ -97,7 +97,7 @@
 
        • Updating a Job
 
 
          • 
 
        • Renaming a Job
          • 
 
        • Restarting Jobs
          • 
@@ -154,7 +154,7 @@ environment variable is not set. The sec
 ~/.aurora/clusters.json.
          
 
 
          For more details on cluster configuration see the
-Client Cluster Configuration documentation.
          
+Client Cluster Configuration documentation.
          
 
 
          Job Keys
          
 
@@ -198,7 +198,7 @@ the machine executing Aurora commands.
 
 
          The process for writing and activating them is complex enough
-that we explain it in a devoted document, Hooks for Aurora Client API.
          
+that we explain it in a devoted document, Hooks for Aurora Client API.
          
 
 
          Regular Jobs
          
 
@@ -246,7 +246,7 @@ already exists. Use aurora update
 
          Updating a Job
          
 
 
          You can manage job updates using the aurora update command.  Please see
-the Job Update documentation for more details.
          
+the Job Update documentation for more details.
          
 
 
          Renaming a Job
          
 
@@ -298,7 +298,7 @@ if it contains hook definitions and acti
 
          Cron Jobs
          
 
 
          You can manage cron jobs using the aurora cron command.  Please see
-the Cron Jobs Feature for more details.
          
+the Cron Jobs Feature for more details.
          
 
 
          Comparing Jobs
          
 
          aurora job diff CLUSTER/ROLE/ENV/NAME <job configuration>
@@ -331,8 +331,8 @@ configuration file, and displays the par
 
          
 
 
          Prints the production quota allocated to the role’s value at the given
-cluster. Only non-dedicated
-production jobs consume quota.
          
+cluster. Only non-dedicated
+production jobs consume quota.
          
 
 
          Finding a Job on Web UI
          
 

Modified: aurora/site/publish/documentation/0.13.0/reference/configuration-best-practices/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/configuration-best-practices/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/reference/configuration-best-practices/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/reference/configuration-best-practices/index.html Thu Apr 21 15:07:18 2016
@@ -135,7 +135,7 @@ limit to 5 and a min_duration
 
 
          Furthermore, the Python version is repeated everywhere. This can be
-bound via structural templating as described in the Advanced Binding
+bound via structural templating as described in the Advanced Binding
 section.
          
 
 
          less_redundant.aurora contains:
          

Modified: aurora/site/publish/documentation/0.13.0/reference/configuration-templating/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/configuration-templating/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/reference/configuration-templating/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/reference/configuration-templating/index.html Thu Apr 21 15:07:18 2016
@@ -86,7 +86,7 @@
 Process, and other classes are defined by a templating library called
 Pystachio, a powerful tool for configuration specification and reuse.
          
 
-
          Aurora Configuration Reference
+
          Aurora Configuration Reference
 has a full reference of all Aurora/Thermos defined Pystachio objects.
          
 
 
          When writing your .aurora file, you may use any Pystachio datatypes, as

Modified: aurora/site/publish/documentation/0.13.0/reference/configuration-tutorial/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/configuration-tutorial/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff
==============================================================================
--- aurora/site/publish/documentation/0.13.0/reference/configuration-tutorial/index.html (original)
+++ aurora/site/publish/documentation/0.13.0/reference/configuration-tutorial/index.html Thu Apr 21 15:07:18 2016
@@ -88,26 +88,26 @@ and best practices. When writing a confi
 arguments as 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.
          
+
          You should read this after going through the general Aurora Tutorial.
          
 
 
 
@@ -143,12 +143,12 @@ configuration specification and reuse. P
 via {{}} surrounded templates.
          
 
 
          When writing your .aurora file, you may use any Pystachio datatypes, as
-well as any objects shown in the Aurora Configuration
+well as any objects shown in the Aurora Configuration
 Reference, without import statements - the
 Aurora config loader injects them automatically. Other than that, an .aurora
 file works like any other Python script.
          
 
-
          Aurora Configuration Reference
+
          Aurora Configuration Reference
 has a full reference of all Aurora/Thermos defined Pystachio objects.
          
 
 
          Use Bottom-To-Top Object Ordering
          
@@ -307,7 +307,7 @@ run = Process(name = 'app', cmdline = 'j
 run_task = SequentialTask(processes = [stage, run])
 
          
 
-
          Process also has optional attributes to customize its behaviour. Details can be found in the Aurora Configuration Reference.
          
+
          Process also has optional attributes to customize its behaviour. Details can be found in the Aurora Configuration Reference.
          
 
 
          Getting Your Code Into The Sandbox
          
 
@@ -367,7 +367,7 @@ the processes run in parallel or sequent
                         disk = 1*GB))
    -

    A Task has optional attributes to customize its behaviour. Details can be found in the Aurora Configuration Reference

    +

    A Task has optional attributes to customize its behaviour. Details can be found in the Aurora Configuration Reference

    SequentialTask: Running Processes in Parallel or Sequentially

    @@ -524,7 +524,7 @@ default. For these four parameters, a Jo

    In addition to the required attributes, there are several optional -attributes. Details can be found in the Aurora Configuration Reference.

    +attributes. Details can be found in the Aurora Configuration Reference.

    The jobs List

    Modified: aurora/site/publish/documentation/0.13.0/reference/configuration/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/configuration/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff ============================================================================== --- aurora/site/publish/documentation/0.13.0/reference/configuration/index.html (original) +++ aurora/site/publish/documentation/0.13.0/reference/configuration/index.html Thu Apr 21 15:07:18 2016 @@ -87,8 +87,8 @@ powerful, and configurations can become cases.

    For examples of simple configurations to get something up and running -quickly, check out the Tutorial. When you feel comfortable with the basics, move -on to the Configuration Tutorial for more in-depth coverage of +quickly, check out the Tutorial. When you feel comfortable with the basics, move +on to the Configuration Tutorial for more in-depth coverage of configuration design.

      @@ -520,7 +520,7 @@ ordering constraints.

      Resource Object

      Specifies the amount of CPU, Ram, and disk resources the task needs. See the -Resource Isolation document for suggested values and to understand how +Resource Isolation document for suggested values and to understand how resources are allocated.

      @@ -596,7 +596,7 @@ resources are allocated.

      - + @@ -631,7 +631,7 @@ resources are allocated.

      - + @@ -699,7 +699,7 @@ resources are allocated.

      - +
      cron_schedule StringCron schedule in cron format. May only be used with non-service jobs. See Cron Jobs for more information. Default: None (not a cron job.)Cron schedule in cron format. May only be used with non-service jobs. See Cron Jobs for more information. Default: None (not a cron job.)
      cron_collision_policy
      production BooleanWhether or not this is a production task that may preempt other tasks (Default: False). Production job role must have the appropriate quota.Whether or not this is a production task that may preempt other tasks (Default: False). Production job role must have the appropriate quota.
      health_check_config
      pulse_interval_secs IntegerIndicates a coordinated update. 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)Indicates a coordinated update. 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)
      @@ -812,13 +812,13 @@ resources are allocated.

      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 +no announcement will take place. For more information about ServerSets, see the Service Discover 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.

      +the overriden value needs to change for every executor, then the executor has to be started inside a wrapper, see 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 @@ -1025,7 +1025,7 @@ constraints.

      -

      Further details can be found in the Scheduling Constraints feature +

      Further details can be found in the Scheduling Constraints feature description.

      Template Namespaces

      Modified: aurora/site/publish/documentation/0.13.0/reference/scheduler-configuration/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/0.13.0/reference/scheduler-configuration/index.html?rev=1740340&r1=1740339&r2=1740340&view=diff ============================================================================== --- aurora/site/publish/documentation/0.13.0/reference/scheduler-configuration/index.html (original) +++ aurora/site/publish/documentation/0.13.0/reference/scheduler-configuration/index.html Thu Apr 21 15:07:18 2016 @@ -85,7 +85,7 @@

      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 for details on how +

      Please refer to the Operator Configuration Guide for details on how to properly set the most important options.

      $ aurora-scheduler -help
 -------------------------------------------------------------------------