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 14A1E188B7 for ; Thu, 2 Jul 2015 17:32:15 +0000 (UTC) Received: (qmail 78167 invoked by uid 500); 2 Jul 2015 17:32:15 -0000 Delivered-To: apmail-aurora-commits-archive@aurora.apache.org Received: (qmail 78133 invoked by uid 500); 2 Jul 2015 17:32:15 -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 78124 invoked by uid 99); 2 Jul 2015 17:32:14 -0000 Received: from eris.apache.org (HELO hades.apache.org) (140.211.11.105) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2015 17:32:14 +0000 Received: from hades.apache.org (localhost [127.0.0.1]) by hades.apache.org (ASF Mail Server at hades.apache.org) with ESMTP id B85DBAC013F for ; Thu, 2 Jul 2015 17:32:14 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r1688866 - in /aurora/site: publish/documentation/latest/configuration-reference/ publish/documentation/latest/cron-jobs/ publish/documentation/latest/deploying-aurora-scheduler/ publish/documentation/latest/developing-aurora-client/ publis... Date: Thu, 02 Jul 2015 17:32:14 -0000 To: commits@aurora.apache.org From: wfarner@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20150702173214.B85DBAC013F@hades.apache.org> Author: wfarner Date: Thu Jul 2 17:32:02 2015 New Revision: 1688866 URL: http://svn.apache.org/r1688866 Log: Updating Aurora documentation to match source in git. Added: aurora/site/publish/documentation/latest/images/presentations/ aurora/site/publish/documentation/latest/images/presentations/02_19_2015_aurora_adopters_panel_thumb.png (with props) aurora/site/publish/documentation/latest/images/presentations/02_19_2015_aurora_at_tellapart_thumb.png (with props) aurora/site/publish/documentation/latest/images/presentations/02_19_2015_aurora_at_twitter_thumb.png (with props) aurora/site/publish/documentation/latest/images/presentations/02_28_2015_apache_aurora_thumb.png (with props) aurora/site/publish/documentation/latest/images/presentations/03_25_2014_introduction_to_aurora_thumb.png (with props) aurora/site/publish/documentation/latest/images/presentations/04_30_2015_monolith_to_microservices_thumb.png (with props) aurora/site/publish/documentation/latest/images/presentations/08_21_2014_past_present_future_thumb.png (with props) aurora/site/source/documentation/latest/images/presentations/ aurora/site/source/documentation/latest/images/presentations/02_19_2015_aurora_adopters_panel_thumb.png (with props) aurora/site/source/documentation/latest/images/presentations/02_19_2015_aurora_at_tellapart_thumb.png (with props) aurora/site/source/documentation/latest/images/presentations/02_19_2015_aurora_at_twitter_thumb.png (with props) aurora/site/source/documentation/latest/images/presentations/02_28_2015_apache_aurora_thumb.png (with props) aurora/site/source/documentation/latest/images/presentations/03_25_2014_introduction_to_aurora_thumb.png (with props) aurora/site/source/documentation/latest/images/presentations/04_30_2015_monolith_to_microservices_thumb.png (with props) aurora/site/source/documentation/latest/images/presentations/08_21_2014_past_present_future_thumb.png (with props) aurora/site/source/documentation/latest/presentations.md Modified: aurora/site/publish/documentation/latest/configuration-reference/index.html aurora/site/publish/documentation/latest/cron-jobs/index.html aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html aurora/site/publish/documentation/latest/developing-aurora-client/index.html aurora/site/publish/documentation/latest/storage-config/index.html aurora/site/publish/documentation/latest/test-resource-generation/index.html aurora/site/source/documentation/latest.html.md aurora/site/source/documentation/latest/configuration-reference.md aurora/site/source/documentation/latest/cron-jobs.md aurora/site/source/documentation/latest/deploying-aurora-scheduler.md aurora/site/source/documentation/latest/developing-aurora-client.md aurora/site/source/documentation/latest/storage-config.md aurora/site/source/documentation/latest/test-resource-generation.md Modified: aurora/site/publish/documentation/latest/configuration-reference/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/configuration-reference/index.html?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/configuration-reference/index.html (original) +++ aurora/site/publish/documentation/latest/configuration-reference/index.html Thu Jul 2 17:32:02 2015 @@ -85,6 +85,7 @@
  • HealthCheckConfig Objects
  • Announcer Objects
  • Container Objects
    • +
  • LifecycleConfig Objects
  • Specifying Scheduling Constraints
  • Template Namespaces @@ -551,6 +552,11 @@ resources are allocated.

    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 for more information. +

    Services

    @@ -638,14 +644,29 @@ either due to human error or machine fai Interval on which to check the task’s health via HTTP. (Default: 10) +max_consecutive_failures +Integer +Maximum number of consecutive failures that tolerated before considering a task unhealthy (Default: 0) + + timeout_secs Integer HTTP request timeout. (Default: 1) -max_consecutive_failures +endpoint +String +HTTP endpoint to check (Default: /health) + + +expected_response +String +If not empty, fail the health check if the response differs. Case insensitive. (Default: ok) + + +expected_response_code Integer -Maximum number of consecutive failures that tolerated before considering a task unhealthy (Default: 0) +If not zero, fail the health check if the response code differs. (Default: 0) @@ -736,6 +757,65 @@ guarantees should they be needed.

    +

    LifecycleConfig Objects

    + +

    Note: The only lifecycle configuration supported is the HTTP lifecycle via the HTTPLifecycleConfig.

    + + + + + + + + + + + + + +
    paramtypedescription
    httpHTTPLifecycleConfigConfigure the lifecycle manager to send lifecycle commands to the task via HTTP.
    + +

    HTTPLifecycleConfig Objects

    + + + + + + + + + + + + + + + + + + + + + + + +
    paramtypedescription
    portStringThe named port to send POST commands (Default: health)
    graceful_shutdown_endpointStringEndpoint to hit to indicate that a task should gracefully shutdown. (Default: /quitquitquit)
    shutdown_endpointStringEndpoint to hit to give a task its final warning before being killed. (Default: /abortabortabort)
    + +

    gracefulshutdownendpoint

    + +

    If the Job is listening on the port as specified by the HTTPLifecycleConfig +(default: health), a HTTP POST request will be sent over localhost to this +endpoint to request that the task gracefully shut itself down. This is a +courtesy call before the shutdown_endpoint is invoked a fixed amount of +time later.

    + +

    shutdown_endpoint

    + +

    If the Job is listening on the port as specified by the HTTPLifecycleConfig +(default: health), a HTTP POST request will be sent over localhost to this +endpoint to request as a final warning before being shut down. If the task +does not shut down on its own after this, it will be forcefully killed

    +

    Specifying Scheduling Constraints

    Most users will not need to specify constraints explicitly, as the Modified: aurora/site/publish/documentation/latest/cron-jobs/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/cron-jobs/index.html?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/cron-jobs/index.html (original) +++ aurora/site/publish/documentation/latest/cron-jobs/index.html Thu Jul 2 17:32:02 2015 @@ -118,7 +118,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-failure” 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/latest/deploying-aurora-scheduler/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html (original) +++ aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html Thu Jul 2 17:32:02 2015 @@ -358,7 +358,7 @@ the master in ZooKeeper, make sure comma

    Symptoms

    -

    The scheduler is registered, and (receiving offers](docs/monitoring.md#schedulerresourceoffers), +

    The scheduler is registered, and receiving offers, but tasks are perpetually shown as PENDING - Constraint not satisfied: host.

    Solution

    Modified: aurora/site/publish/documentation/latest/developing-aurora-client/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/developing-aurora-client/index.html?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/developing-aurora-client/index.html (original) +++ aurora/site/publish/documentation/latest/developing-aurora-client/index.html Thu Jul 2 17:32:02 2015 @@ -69,7 +69,7 @@ To start a virtual cluster, you need to the aurora workspace. This will create a vagrant host named “devcluster”, with a mesos master, a set of mesos slaves, and an aurora scheduler.

    -

    If you have changed you would like to test in your local cluster, you’ll rebuild the client:

    +

    If you have a change you would like to test in your local cluster, you’ll rebuild the client:

    vagrant ssh -c 'aurorabuild client'

    Once this completes, the aurora command will reflect your changes.

    Added: aurora/site/publish/documentation/latest/images/presentations/02_19_2015_aurora_adopters_panel_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/images/presentations/02_19_2015_aurora_adopters_panel_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/publish/documentation/latest/images/presentations/02_19_2015_aurora_adopters_panel_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/publish/documentation/latest/images/presentations/02_19_2015_aurora_at_tellapart_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/images/presentations/02_19_2015_aurora_at_tellapart_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/publish/documentation/latest/images/presentations/02_19_2015_aurora_at_tellapart_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/publish/documentation/latest/images/presentations/02_19_2015_aurora_at_twitter_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/images/presentations/02_19_2015_aurora_at_twitter_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/publish/documentation/latest/images/presentations/02_19_2015_aurora_at_twitter_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/publish/documentation/latest/images/presentations/02_28_2015_apache_aurora_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/images/presentations/02_28_2015_apache_aurora_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/publish/documentation/latest/images/presentations/02_28_2015_apache_aurora_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/publish/documentation/latest/images/presentations/03_25_2014_introduction_to_aurora_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/images/presentations/03_25_2014_introduction_to_aurora_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/publish/documentation/latest/images/presentations/03_25_2014_introduction_to_aurora_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/publish/documentation/latest/images/presentations/04_30_2015_monolith_to_microservices_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/images/presentations/04_30_2015_monolith_to_microservices_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/publish/documentation/latest/images/presentations/04_30_2015_monolith_to_microservices_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/publish/documentation/latest/images/presentations/08_21_2014_past_present_future_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/images/presentations/08_21_2014_past_present_future_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/publish/documentation/latest/images/presentations/08_21_2014_past_present_future_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Modified: aurora/site/publish/documentation/latest/storage-config/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/storage-config/index.html?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/storage-config/index.html (original) +++ aurora/site/publish/documentation/latest/storage-config/index.html Thu Jul 2 17:32:02 2015 @@ -158,9 +158,9 @@ accomplished by updating the following s registering with Mesos. E.g.: -mesos_master_address=zk://localhost:2181
  • -max_registration_delay - set to sufficiently long interval to prevent registration timeout and as a result scheduler suicide. E.g: -max_registration_delay=360min
    • -
  • Make sure -gc_executor_path option is not set to prevent accidental task GC. This is -important as scheduler will attempt to reconcile the cluster state and will kill all tasks when -restarted with an empty Mesos replicated log.
    • +
  • Make sure -reconciliation_initial_delay option is set high enough (e.g.: 365days) to +prevent accidental task GC. This is important as scheduler will attempt to reconcile the cluster +state and will kill all tasks when restarted with an empty Mesos replicated log.

  • Restart all schedulers

    • Modified: aurora/site/publish/documentation/latest/test-resource-generation/index.html URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/test-resource-generation/index.html?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/publish/documentation/latest/test-resource-generation/index.html (original) +++ aurora/site/publish/documentation/latest/test-resource-generation/index.html Thu Jul 2 17:32:02 2015 @@ -46,9 +46,8 @@

    The Aurora source repository and distributions contain several binary files to qualify the backwards-compatibility of thermos with checkpoint data. Since -thermos persists state to disk, to be read by other components (the GC executor -and the thermos observer), it is important that we have tests that prevent -regressions affecting the ability to parse previously-written data.

    +thermos persists state to disk, to be read by the thermos observer), it is important that we have +tests that prevent regressions affecting the ability to parse previously-written data.

    Generating test files

    Modified: aurora/site/source/documentation/latest.html.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest.html.md?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/source/documentation/latest.html.md (original) +++ aurora/site/source/documentation/latest.html.md Thu Jul 2 17:32:02 2015 @@ -27,7 +27,10 @@ We encourage you to ask questions on the * [Generating test resources](/documentation/latest/test-resource-generation/) ## Developers - * [Contributing to the project](/documentation/latest/contributing/) + * [Contributing to the project](../CONTRIBUTING.md) * [Developing the Aurora Scheduler](/documentation/latest/developing-aurora-scheduler/) * [Developing the Aurora Client](/documentation/latest/developing-aurora-client/) * [Committers Guide](/documentation/latest/committers/) + +## Additional Resources + * [Presentation videos and slides](/documentation/latest/presentations/) \ No newline at end of file Modified: aurora/site/source/documentation/latest/configuration-reference.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/configuration-reference.md?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/source/documentation/latest/configuration-reference.md (original) +++ aurora/site/source/documentation/latest/configuration-reference.md Thu Jul 2 17:32:02 2015 @@ -30,6 +30,7 @@ Aurora + Thermos Configuration Reference - [HealthCheckConfig Objects](#healthcheckconfig-objects) - [Announcer Objects](#announcer-objects) - [Container Objects](#container) + - [LifecycleConfig Objects](#lifecycleconfig-objects) - [Specifying Scheduling Constraints](#specifying-scheduling-constraints) - [Template Namespaces](#template-namespaces) - [mesos Namespace](#mesos-namespace) @@ -277,6 +278,7 @@ Client applications with higher priority finalization wait (e.g. through parameters to `thermos kill`), so this is mostly a best-effort signal. + ### Constraint Object Current constraint objects only support a single ordering constraint, `order`, @@ -325,6 +327,7 @@ Job Schema ```production``` | Boolean | Whether or not this is a production task backed by quota (Default: False). Production jobs may preempt any non-production job, and may only be preempted by production jobs in the same role and of higher priority. To run jobs at this level, the job role must have the appropriate quota. To grant quota to a particular role in production, operators use the ``aurora_admin set_quota`` command. ```health_check_config``` | ```heath_check_config``` object | Parameters for controlling a task's health checks via HTTP. Only used if a health port was assigned with a command line wildcard. ```container``` | ```Container``` object | An optional container to run all processes inside of. + ```lifecycle``` | ```LifecycleConfig``` object | An optional task lifecycle configuration that dictates commands to be executed on startup/teardown. HTTP lifecycle is enabled by default if the "health" port is requested. See [LifecycleConfig Objects](#lifecycleconfig-objects) for more information. ### Services @@ -359,8 +362,11 @@ Parameters for controlling a task's heal | ------- | :-------: | -------- | ```initial_interval_secs``` | Integer | Initial delay for performing an HTTP health check. (Default: 15) | ```interval_secs``` | Integer | Interval on which to check the task's health via HTTP. (Default: 10) -| ```timeout_secs``` | Integer | HTTP request timeout. (Default: 1) | ```max_consecutive_failures``` | Integer | Maximum number of consecutive failures that tolerated before considering a task unhealthy (Default: 0) +| ```timeout_secs``` | Integer | HTTP request timeout. (Default: 1) +| ```endpoint``` | String | HTTP endpoint to check (Default: /health) +| ```expected_response``` | String | If not empty, fail the health check if the response differs. Case insensitive. (Default: ok) +| ```expected_response_code``` | Integer | If not zero, fail the health check if the response code differs. (Default: 0) ### Announcer Objects @@ -415,6 +421,37 @@ Describes the container the job's proces ----- | :----: | ----------- ```image``` | String | The name of the docker image to execute. If the image does not exist locally it will be pulled with ```docker pull```. +### LifecycleConfig Objects + +*Note: The only lifecycle configuration supported is the HTTP lifecycle via the HTTPLifecycleConfig.* + + param | type | description + ----- | :----: | ----------- + ```http``` | HTTPLifecycleConfig | Configure the lifecycle manager to send lifecycle commands to the task via HTTP. + +### HTTPLifecycleConfig Objects + + param | type | description + ----- | :----: | ----------- + ```port``` | String | The named port to send POST commands (Default: health) + ```graceful_shutdown_endpoint``` | String | Endpoint to hit to indicate that a task should gracefully shutdown. (Default: /quitquitquit) + ```shutdown_endpoint``` | String | Endpoint to hit to give a task its final warning before being killed. (Default: /abortabortabort) + +#### graceful_shutdown_endpoint + +If the Job is listening on the port as specified by the HTTPLifecycleConfig +(default: `health`), a HTTP POST request will be sent over localhost to this +endpoint to request that the task gracefully shut itself down. This is a +courtesy call before the `shutdown_endpoint` is invoked a fixed amount of +time later. + +#### shutdown_endpoint + +If the Job is listening on the port as specified by the HTTPLifecycleConfig +(default: `health`), a HTTP POST request will be sent over localhost to this +endpoint to request as a final warning before being shut down. If the task +does not shut down on its own after this, it will be forcefully killed + Specifying Scheduling Constraints ================================= Modified: aurora/site/source/documentation/latest/cron-jobs.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/cron-jobs.md?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/source/documentation/latest/cron-jobs.md (original) +++ aurora/site/source/documentation/latest/cron-jobs.md Thu Jul 2 17:32:02 2015 @@ -67,7 +67,7 @@ grow faster than they can process it. Unlike with services, which aurora will always re-execute regardless of exit status, instances of cron jobs retry according to the `max_task_failures` attribute of the -[Task](configuration-reference.md#task-objects) object. To get "run-until-failure" semantics, +[Task](configuration-reference.md#task-objects) object. To get "run-until-success" semantics, set `max_task_failures` to `-1`. ## Interacting with cron jobs via the Aurora CLI Modified: aurora/site/source/documentation/latest/deploying-aurora-scheduler.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/deploying-aurora-scheduler.md?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/source/documentation/latest/deploying-aurora-scheduler.md (original) +++ aurora/site/source/documentation/latest/deploying-aurora-scheduler.md Thu Jul 2 17:32:02 2015 @@ -278,7 +278,7 @@ is the same as the one on the scheduler: ### Tasks are stuck in `PENDING` forever #### Symptoms -The scheduler is registered, and (receiving offers](docs/monitoring.md#scheduler_resource_offers), +The scheduler is registered, and [receiving offers](monitoring.md#scheduler_resource_offers), but tasks are perpetually shown as `PENDING - Constraint not satisfied: host`. #### Solution Modified: aurora/site/source/documentation/latest/developing-aurora-client.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/developing-aurora-client.md?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/source/documentation/latest/developing-aurora-client.md (original) +++ aurora/site/source/documentation/latest/developing-aurora-client.md Thu Jul 2 17:32:02 2015 @@ -30,7 +30,7 @@ To start a virtual cluster, you need to the aurora workspace. This will create a vagrant host named "devcluster", with a mesos master, a set of mesos slaves, and an aurora scheduler. -If you have changed you would like to test in your local cluster, you'll rebuild the client: +If you have a change you would like to test in your local cluster, you'll rebuild the client: vagrant ssh -c 'aurorabuild client' Added: aurora/site/source/documentation/latest/images/presentations/02_19_2015_aurora_adopters_panel_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/images/presentations/02_19_2015_aurora_adopters_panel_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/source/documentation/latest/images/presentations/02_19_2015_aurora_adopters_panel_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/source/documentation/latest/images/presentations/02_19_2015_aurora_at_tellapart_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/images/presentations/02_19_2015_aurora_at_tellapart_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/source/documentation/latest/images/presentations/02_19_2015_aurora_at_tellapart_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/source/documentation/latest/images/presentations/02_19_2015_aurora_at_twitter_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/images/presentations/02_19_2015_aurora_at_twitter_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/source/documentation/latest/images/presentations/02_19_2015_aurora_at_twitter_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/source/documentation/latest/images/presentations/02_28_2015_apache_aurora_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/images/presentations/02_28_2015_apache_aurora_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/source/documentation/latest/images/presentations/02_28_2015_apache_aurora_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/source/documentation/latest/images/presentations/03_25_2014_introduction_to_aurora_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/images/presentations/03_25_2014_introduction_to_aurora_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/source/documentation/latest/images/presentations/03_25_2014_introduction_to_aurora_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/source/documentation/latest/images/presentations/04_30_2015_monolith_to_microservices_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/images/presentations/04_30_2015_monolith_to_microservices_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/source/documentation/latest/images/presentations/04_30_2015_monolith_to_microservices_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/source/documentation/latest/images/presentations/08_21_2014_past_present_future_thumb.png URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/images/presentations/08_21_2014_past_present_future_thumb.png?rev=1688866&view=auto ============================================================================== Binary file - no diff available. Propchange: aurora/site/source/documentation/latest/images/presentations/08_21_2014_past_present_future_thumb.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: aurora/site/source/documentation/latest/presentations.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/presentations.md?rev=1688866&view=auto ============================================================================== --- aurora/site/source/documentation/latest/presentations.md (added) +++ aurora/site/source/documentation/latest/presentations.md Thu Jul 2 17:32:02 2015 @@ -0,0 +1,50 @@ +# Apache Aurora Presentations +Video and slides from presentations and panel discussions about Apache Aurora. + +_(Listed in date descending order)_ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    From Monolith to Microservices with Aurora Video ThumbnailFrom Monolith to Microservices w/ Aurora (Video) +

    Presented by Thanos Baskous, Tony Dong, Dobromir Montauk

    +

    April 30, 2015 at Bay Area Apache Aurora Users Group

    Apache Auroraの始めかた Slideshow ThumbnailApache Auroraの始めかた (Slides) +

    Presented by Masahito Zembutsu

    +

    February 28, 2015 at Open Source Conference 2015 Tokyo Spring

    Apache Aurora Adopters Panel Video ThumbnailApache Aurora Adopters Panel (Video) +

    Panelists Ben Staffin, Josh Adams, Bill Farner, Berk Demir

    +

    February 19, 2015 at Bay Area Mesos Users Group

    Operating Apache Aurora and Mesos at Twitter Video ThumbnailOperating Apache Aurora and Mesos at Twitter (Video) +

    Presented by Joe Smith

    +

    February 19, 2015 at Bay Area Mesos Users Group

    Apache Aurora and Mesos at TellApartApache Aurora and Mesos at TellApart (Video) +

    Presented by Steve Niemitz

    +

    February 19, 2015 at Bay Area Mesos Users Group

    Past, Present, and Future of the Aurora Scheduler Video ThumbnailPast, Present, and Future of the Aurora Scheduler (Video) +

    Presented by Bill Farner

    +

    August 21, 2014 at #MesosCon 2014

    +
    Introduction to Apache Aurora Video ThumbnailIntroduction to Apache Aurora (Video) +

    Presented by Bill Farner

    +

    March 25, 2014 at Aurora and Mesos Frameworks Meetup

    \ No newline at end of file Modified: aurora/site/source/documentation/latest/storage-config.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/storage-config.md?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/source/documentation/latest/storage-config.md (original) +++ aurora/site/source/documentation/latest/storage-config.md Thu Jul 2 17:32:02 2015 @@ -100,9 +100,9 @@ accomplished by updating the following s registering with Mesos. E.g.: `-mesos_master_address=zk://localhost:2181` * `-max_registration_delay` - set to sufficiently long interval to prevent registration timeout and as a result scheduler suicide. E.g: `-max_registration_delay=360min` - * Make sure `-gc_executor_path` option is not set to prevent accidental task GC. This is - important as scheduler will attempt to reconcile the cluster state and will kill all tasks when - restarted with an empty Mesos replicated log. + * Make sure `-reconciliation_initial_delay` option is set high enough (e.g.: `365days`) to + prevent accidental task GC. This is important as scheduler will attempt to reconcile the cluster + state and will kill all tasks when restarted with an empty Mesos replicated log. * Restart all schedulers Modified: aurora/site/source/documentation/latest/test-resource-generation.md URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/test-resource-generation.md?rev=1688866&r1=1688865&r2=1688866&view=diff ============================================================================== --- aurora/site/source/documentation/latest/test-resource-generation.md (original) +++ aurora/site/source/documentation/latest/test-resource-generation.md Thu Jul 2 17:32:02 2015 @@ -4,9 +4,8 @@ The Aurora source repository and distributions contain several [binary files](../src/test/resources/org/apache/thermos/root/checkpoints) to qualify the backwards-compatibility of thermos with checkpoint data. Since -thermos persists state to disk, to be read by other components (the GC executor -and the thermos observer), it is important that we have tests that prevent -regressions affecting the ability to parse previously-written data. +thermos persists state to disk, to be read by the thermos observer), it is important that we have +tests that prevent regressions affecting the ability to parse previously-written data. ## Generating test files The files included represent persisted checkpoints that exercise different