Author: jfarrell
Date: Fri Jul 24 13:05:53 2015
New Revision: 1692500
URL: http://svn.apache.org/r1692500
Log:
Updating website for 0.9.0
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/index.html
aurora/site/publish/documentation/latest/sla/index.html
aurora/site/publish/documentation/latest/storage-config/index.html
aurora/site/publish/documentation/latest/test-resource-generation/index.html
aurora/site/publish/documentation/latest/vagrant/index.html
aurora/site/publish/downloads/index.html
aurora/site/publish/sitemap.xml
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/sla.md
aurora/site/source/documentation/latest/storage-config.md
aurora/site/source/documentation/latest/test-resource-generation.md
aurora/site/source/documentation/latest/vagrant.md
aurora/site/source/downloads.html.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=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/configuration-reference/index.html
(original)
+++ aurora/site/publish/documentation/latest/configuration-reference/index.html
Fri Jul 24 13:05:53 2015
@@ -85,7 +85,6 @@
<li><a href="#healthcheckconfig-objects">HealthCheckConfig Objects</a></li>
<li><a href="#announcer-objects">Announcer Objects</a></li>
<li><a href="#container">Container Objects</a></li>
-<li><a href="#lifecycleconfig-objects">LifecycleConfig Objects</a></li>
</ul></li>
<li><a href="#specifying-scheduling-constraints">Specifying Scheduling
Constraints</a></li>
<li><a href="#template-namespaces">Template Namespaces</a>
@@ -552,11 +551,6 @@ resources are allocated.</p>
<td style="text-align: center"><code>Container</code> object</td>
<td>An optional container to run all processes inside of.</td>
</tr>
-<tr>
-<td><code>lifecycle</code></td>
-<td style="text-align: center"><code>LifecycleConfig</code> object</td>
-<td>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 <a
href="#lifecycleconfig-objects">LifecycleConfig Objects</a> for more
information.</td>
-</tr>
</tbody></table>
<h3 id="services">Services</h3>
@@ -644,29 +638,14 @@ either due to human error or machine fai
<td>Interval on which to check the task’s health via HTTP. (Default:
10)</td>
</tr>
<tr>
-<td><code>max_consecutive_failures</code></td>
-<td style="text-align: center">Integer</td>
-<td>Maximum number of consecutive failures that tolerated before considering a
task unhealthy (Default: 0)</td>
-</tr>
-<tr>
<td><code>timeout_secs</code></td>
<td style="text-align: center">Integer</td>
<td>HTTP request timeout. (Default: 1)</td>
</tr>
<tr>
-<td><code>endpoint</code></td>
-<td style="text-align: center">String</td>
-<td>HTTP endpoint to check (Default: /health)</td>
-</tr>
-<tr>
-<td><code>expected_response</code></td>
-<td style="text-align: center">String</td>
-<td>If not empty, fail the health check if the response differs. Case
insensitive. (Default: ok)</td>
-</tr>
-<tr>
-<td><code>expected_response_code</code></td>
+<td><code>max_consecutive_failures</code></td>
<td style="text-align: center">Integer</td>
-<td>If not zero, fail the health check if the response code differs. (Default:
0)</td>
+<td>Maximum number of consecutive failures that tolerated before considering a
task unhealthy (Default: 0)</td>
</tr>
</tbody></table>
@@ -757,65 +736,6 @@ guarantees should they be needed.</p>
</tr>
</tbody></table>
-<h3 id="lifecycleconfig-objects">LifecycleConfig Objects</h3>
-
-<p><em>Note: The only lifecycle configuration supported is the HTTP lifecycle
via the HTTPLifecycleConfig.</em></p>
-
-<table><thead>
-<tr>
-<th>param</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>http</code></td>
-<td style="text-align: center">HTTPLifecycleConfig</td>
-<td>Configure the lifecycle manager to send lifecycle commands to the task via
HTTP.</td>
-</tr>
-</tbody></table>
-
-<h3 id="httplifecycleconfig-objects">HTTPLifecycleConfig Objects</h3>
-
-<table><thead>
-<tr>
-<th>param</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>port</code></td>
-<td style="text-align: center">String</td>
-<td>The named port to send POST commands (Default: health)</td>
-</tr>
-<tr>
-<td><code>graceful_shutdown_endpoint</code></td>
-<td style="text-align: center">String</td>
-<td>Endpoint to hit to indicate that a task should gracefully shutdown.
(Default: /quitquitquit)</td>
-</tr>
-<tr>
-<td><code>shutdown_endpoint</code></td>
-<td style="text-align: center">String</td>
-<td>Endpoint to hit to give a task its final warning before being killed.
(Default: /abortabortabort)</td>
-</tr>
-</tbody></table>
-
-<h4 id="gracefulshutdownendpoint">graceful<em>shutdown</em>endpoint</h4>
-
-<p>If the Job is listening on the port as specified by the HTTPLifecycleConfig
-(default: <code>health</code>), 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 <code>shutdown_endpoint</code> is invoked a fixed
amount of
-time later.</p>
-
-<h4 id="shutdown_endpoint">shutdown_endpoint</h4>
-
-<p>If the Job is listening on the port as specified by the HTTPLifecycleConfig
-(default: <code>health</code>), 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</p>
-
<h1 id="specifying-scheduling-constraints">Specifying Scheduling
Constraints</h1>
<p>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=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/cron-jobs/index.html (original)
+++ aurora/site/publish/documentation/latest/cron-jobs/index.html Fri Jul 24
13:05:53 2015
@@ -118,7 +118,7 @@ grow faster than they can process it.</p
<p>Unlike with services, which aurora will always re-execute regardless of
exit status, instances of
cron jobs retry according to the <code>max_task_failures</code> attribute of
the
-<a href="configuration-reference.md#task-objects">Task</a> object. To get
“run-until-success” semantics,
+<a href="configuration-reference.md#task-objects">Task</a> object. To get
“run-until-failure” semantics,
set <code>max_task_failures</code> to <code>-1</code>.</p>
<h2 id="interacting-with-cron-jobs-via-the-aurora-cli">Interacting with cron
jobs via the Aurora CLI</h2>
Modified:
aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html?rev=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
---
aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html
(original)
+++
aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html
Fri Jul 24 13:05:53 2015
@@ -358,7 +358,7 @@ the master in ZooKeeper, make sure comma
<h4 id="symptoms">Symptoms</h4>
-<p>The scheduler is registered, and <a
href="monitoring.md#scheduler_resource_offers">receiving offers</a>,
+<p>The scheduler is registered, and (receiving
offers](docs/monitoring.md#scheduler<em>resource</em>offers),
but tasks are perpetually shown as <code>PENDING - Constraint not satisfied:
host</code>.</p>
<h4 id="solution">Solution</h4>
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=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
---
aurora/site/publish/documentation/latest/developing-aurora-client/index.html
(original)
+++
aurora/site/publish/documentation/latest/developing-aurora-client/index.html
Fri Jul 24 13:05:53 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.</p>
-<p>If you have a change you would like to test in your local cluster,
you’ll rebuild the client:</p>
+<p>If you have changed you would like to test in your local cluster,
you’ll rebuild the client:</p>
<pre class="highlight text">vagrant ssh -c 'aurorabuild client'
</pre>
<p>Once this completes, the <code>aurora</code> command will reflect your
changes.</p>
Modified: aurora/site/publish/documentation/latest/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/index.html?rev=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/index.html (original)
+++ aurora/site/publish/documentation/latest/index.html Fri Jul 24 13:05:53 2015
@@ -79,17 +79,11 @@
<h2 id="developers">Developers</h2>
<ul>
-<li><a href="../CONTRIBUTING.md">Contributing to the project</a></li>
+<li><a href="/documentation/latest/contributing/">Contributing to the
project</a></li>
<li><a href="/documentation/latest/developing-aurora-scheduler/">Developing
the Aurora Scheduler</a></li>
<li><a href="/documentation/latest/developing-aurora-client/">Developing the
Aurora Client</a></li>
<li><a href="/documentation/latest/committers/">Committers Guide</a></li>
</ul>
-
-<h2 id="additional-resources">Additional Resources</h2>
-
-<ul>
-<li><a href="/documentation/latest/presentations/">Presentation videos and
slides</a></li>
-</ul>
</div>
</div>
Modified: aurora/site/publish/documentation/latest/sla/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/sla/index.html?rev=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/sla/index.html (original)
+++ aurora/site/publish/documentation/latest/sla/index.html Fri Jul 24 13:05:53
2015
@@ -60,9 +60,8 @@
Agreements) metrics that defining a contractual relationship between the
Aurora/Mesos platform
and hosted services.</p>
-<p>The Aurora SLA feature is by default only enabled for service (non-cron)
-production jobs (<code>"production = True"</code> in your
<code>.aurora</code> config). It can be enabled for
-non-production services via the scheduler command line flag
<code>-sla_non_prod_metrics</code>.</p>
+<p>The Aurora SLA feature currently supports stat collection only for service
(non-cron)
+production jobs (<code>"production = True"</code> in your
<code>.aurora</code> config).</p>
<p>Counters that track SLA measurements are computed periodically within the
scheduler.
The individual instance metrics are refreshed every minute (configurable via
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=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/storage-config/index.html
(original)
+++ aurora/site/publish/documentation/latest/storage-config/index.html Fri Jul
24 13:05:53 2015
@@ -158,9 +158,9 @@ accomplished by updating the following s
registering with Mesos. E.g.:
<code>-mesos_master_address=zk://localhost:2181</code></li>
<li><code>-max_registration_delay</code> - set to sufficiently long interval
to prevent registration timeout
and as a result scheduler suicide. E.g:
<code>-max_registration_delay=360min</code></li>
-<li>Make sure <code>-reconciliation_initial_delay</code> option is set high
enough (e.g.: <code>365days</code>) 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.</li>
+<li>Make sure <code>-gc_executor_path</code> 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.</li>
</ul></li>
<li><p>Restart all schedulers</p></li>
</ul>
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=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
---
aurora/site/publish/documentation/latest/test-resource-generation/index.html
(original)
+++
aurora/site/publish/documentation/latest/test-resource-generation/index.html
Fri Jul 24 13:05:53 2015
@@ -46,8 +46,9 @@
<p>The Aurora source repository and distributions contain several
<a href="../src/test/resources/org/apache/thermos/root/checkpoints">binary
files</a> to
qualify the backwards-compatibility of thermos with checkpoint data. Since
-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.</p>
+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.</p>
<h2 id="generating-test-files">Generating test files</h2>
Modified: aurora/site/publish/documentation/latest/vagrant/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/vagrant/index.html?rev=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/vagrant/index.html (original)
+++ aurora/site/publish/documentation/latest/vagrant/index.html Fri Jul 24
13:05:53 2015
@@ -78,7 +78,7 @@ common commands for this tool.</p>
<h2 id="clone-the-aurora-repository">Clone the Aurora repository</h2>
<p>To obtain the Aurora source distribution, clone its Git repository using
the following command:</p>
-<pre class="highlight text"> git clone git://git.apache.org/aurora.git
+<pre class="highlight text"> git clone http://git.apache.org/aurora.git
</pre>
<h2 id="start-the-local-cluster">Start the local cluster</h2>
Modified: aurora/site/publish/downloads/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/downloads/index.html?rev=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/publish/downloads/index.html (original)
+++ aurora/site/publish/downloads/index.html Fri Jul 24 13:05:53 2015
@@ -48,10 +48,10 @@
<h2 id="current-release">Current Release</h2>
-<p>The current released version is <em>0.8.0</em>. <a
href="https://www.apache.org/dyn/mirrors/mirrors.cgi/aurora/0.8.0/apache-aurora-0.8.0.tar.gz";>(tar.gz)</a>
-<a
href="https://www.apache.org/dist/aurora/0.8.0/apache-aurora-0.8.0.tar.gz.md5";>(md5)</a>
-<a
href="https://www.apache.org/dist/aurora/0.8.0/apache-aurora-0.8.0.tar.gz.sha";>(sha)</a>
-<a
href="https://www.apache.org/dist/aurora/0.8.0/apache-aurora-0.8.0.tar.gz.asc";>(sig)</a></p>
+<p>The current released version is <em>0.9.0</em>. <a
href="https://www.apache.org/dyn/mirrors/mirrors.cgi/aurora/0.9.0/apache-aurora-0.9.0.tar.gz";>(tar.gz)</a>
+<a
href="https://www.apache.org/dist/aurora/0.9.0/apache-aurora-0.9.0.tar.gz.md5";>(md5)</a>
+<a
href="https://www.apache.org/dist/aurora/0.9.0/apache-aurora-0.9.0.tar.gz.sha";>(sha)</a>
+<a
href="https://www.apache.org/dist/aurora/0.9.0/apache-aurora-0.9.0.tar.gz.asc";>(sig)</a></p>
<p>To quickly get started, we reccomend using Vagrant and following the <a
href="/documentation/latest/vagrant/">Getting Started guide</a>.</p>
@@ -109,4 +109,4 @@ and the <a href="https://github.com/apac
</div>
</div>
</body>
-</html>
+</html>
\ No newline at end of file
Modified: aurora/site/publish/sitemap.xml
URL:
http://svn.apache.org/viewvc/aurora/site/publish/sitemap.xml?rev=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/publish/sitemap.xml (original)
+++ aurora/site/publish/sitemap.xml Fri Jul 24 13:05:53 2015
@@ -2,146 +2,142 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";>
<url>
<loc>http://aurora.apache.org/blog/aurora-0-6-0-incubating-released/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
<loc>http://aurora.apache.org/blog/aurora-0-7-0-incubating-released/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
<loc>http://aurora.apache.org/blog/2015-upcoming-apache-aurora-meetups/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
<loc>http://aurora.apache.org/blog/aurora-0-8-0-released/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/docs/gettingstarted/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
- </url>
- <url>
- <loc>http://aurora.apache.org/docs/howtocontribute/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
- </url>
- <url>
- <loc>http://aurora.apache.org/documentation/latest/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/blog/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/presentations/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/community/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/sla/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/developers/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
-
<loc>http://aurora.apache.org/documentation/latest/resource-isolation/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/docs/gettingstarted/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/hooks/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/docs/howtocontribute/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/monitoring/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+
<loc>http://aurora.apache.org/documentation/latest/client-cluster-configuration/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
-
<loc>http://aurora.apache.org/documentation/latest/developing-aurora-client/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/client-commands/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/user-guide/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/committers/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/security/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+
<loc>http://aurora.apache.org/documentation/latest/configuration-reference/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
-
<loc>http://aurora.apache.org/documentation/latest/thrift-deprecation/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+
<loc>http://aurora.apache.org/documentation/latest/configuration-tutorial/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
-
<loc>http://aurora.apache.org/documentation/latest/developing-aurora-scheduler/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/contributing/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/client-commands/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/cron-jobs/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/cron-jobs/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+
<loc>http://aurora.apache.org/documentation/latest/deploying-aurora-scheduler/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
-
<loc>http://aurora.apache.org/documentation/latest/configuration-tutorial/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+
<loc>http://aurora.apache.org/documentation/latest/developing-aurora-client/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/vagrant/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+
<loc>http://aurora.apache.org/documentation/latest/developing-aurora-scheduler/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
-
<loc>http://aurora.apache.org/documentation/latest/client-cluster-configuration/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/hooks/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/tutorial/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/monitoring/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/contributing/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+
<loc>http://aurora.apache.org/documentation/latest/resource-isolation/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
<loc>http://aurora.apache.org/documentation/latest/scheduler-storage/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/storage/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/security/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
-
<loc>http://aurora.apache.org/documentation/latest/test-resource-generation/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/sla/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
-
<loc>http://aurora.apache.org/documentation/latest/deploying-aurora-scheduler/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/storage-config/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
-
<loc>http://aurora.apache.org/documentation/latest/configuration-reference/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/storage/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/storage-config/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+
<loc>http://aurora.apache.org/documentation/latest/test-resource-generation/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/documentation/latest/committers/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+
<loc>http://aurora.apache.org/documentation/latest/thrift-deprecation/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/tutorial/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/developers/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/user-guide/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/community/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/vagrant/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
- <loc>http://aurora.apache.org/blog/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <loc>http://aurora.apache.org/documentation/latest/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
<url>
<loc>http://aurora.apache.org/downloads/</loc>
- <lastmod>2015-07-06T00:00:00-07:00</lastmod>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
+ </url>
+ <url>
+ <loc>http://aurora.apache.org/</loc>
+ <lastmod>2015-07-24T00:00:00-04:00</lastmod>
</url>
</urlset>
\ No newline at end of file
Modified: aurora/site/source/documentation/latest.html.md
URL:
http://svn.apache.org/viewvc/aurora/site/source/documentation/latest.html.md?rev=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/source/documentation/latest.html.md (original)
+++ aurora/site/source/documentation/latest.html.md Fri Jul 24 13:05:53 2015
@@ -27,10 +27,7 @@ We encourage you to ask questions on the
* [Generating test resources](/documentation/latest/test-resource-generation/)
## Developers
- * [Contributing to the project](../CONTRIBUTING.md)
+ * [Contributing to the project](/documentation/latest/contributing/)
* [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=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/configuration-reference.md
(original)
+++ aurora/site/source/documentation/latest/configuration-reference.md Fri Jul
24 13:05:53 2015
@@ -30,7 +30,6 @@ 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)
@@ -278,7 +277,6 @@ 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`,
@@ -327,7 +325,6 @@ 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
@@ -362,11 +359,8 @@ 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)
-| ```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)
+| ```max_consecutive_failures``` | Integer | Maximum number of consecutive
failures that tolerated before considering a task unhealthy (Default: 0)
### Announcer Objects
@@ -421,37 +415,6 @@ 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=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/cron-jobs.md (original)
+++ aurora/site/source/documentation/latest/cron-jobs.md Fri Jul 24 13:05:53
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-success" semantics,
+[Task](configuration-reference.md#task-objects) object. To get
"run-until-failure" 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=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/deploying-aurora-scheduler.md
(original)
+++ aurora/site/source/documentation/latest/deploying-aurora-scheduler.md Fri
Jul 24 13:05:53 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](monitoring.md#scheduler_resource_offers),
+The scheduler is registered, and (receiving
offers](docs/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=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/developing-aurora-client.md
(original)
+++ aurora/site/source/documentation/latest/developing-aurora-client.md Fri Jul
24 13:05:53 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 a change you would like to test in your local cluster, you'll
rebuild the client:
+If you have changed you would like to test in your local cluster, you'll
rebuild the client:
vagrant ssh -c 'aurorabuild client'
Modified: aurora/site/source/documentation/latest/sla.md
URL:
http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/sla.md?rev=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/sla.md (original)
+++ aurora/site/source/documentation/latest/sla.md Fri Jul 24 13:05:53 2015
@@ -15,9 +15,8 @@ The primary goal of the feature is colle
Agreements) metrics that defining a contractual relationship between the
Aurora/Mesos platform
and hosted services.
-The Aurora SLA feature is by default only enabled for service (non-cron)
-production jobs (`"production = True"` in your `.aurora` config). It can be
enabled for
-non-production services via the scheduler command line flag
`-sla_non_prod_metrics`.
+The Aurora SLA feature currently supports stat collection only for service
(non-cron)
+production jobs (`"production = True"` in your `.aurora` config).
Counters that track SLA measurements are computed periodically within the
scheduler.
The individual instance metrics are refreshed every minute (configurable via
@@ -174,4 +173,4 @@ unreasonable resource constraints) do no
* The availability of Aurora SLA metrics is bound by the scheduler
availability.
* All metrics are calculated at a pre-defined interval (currently set at 1
minute).
- Scheduler restarts may result in missed collections.
+ Scheduler restarts may result in missed collections.
\ 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=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/storage-config.md (original)
+++ aurora/site/source/documentation/latest/storage-config.md Fri Jul 24
13:05:53 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 `-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.
+ * 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.
* 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=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/test-resource-generation.md
(original)
+++ aurora/site/source/documentation/latest/test-resource-generation.md Fri Jul
24 13:05:53 2015
@@ -4,8 +4,9 @@
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 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 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.
## Generating test files
The files included represent persisted checkpoints that exercise different
Modified: aurora/site/source/documentation/latest/vagrant.md
URL:
http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/vagrant.md?rev=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/vagrant.md (original)
+++ aurora/site/source/documentation/latest/vagrant.md Fri Jul 24 13:05:53 2015
@@ -43,7 +43,7 @@ Clone the Aurora repository
To obtain the Aurora source distribution, clone its Git repository using the
following command:
- git clone git://git.apache.org/aurora.git
+ git clone http://git.apache.org/aurora.git
Start the local cluster
Modified: aurora/site/source/downloads.html.md
URL:
http://svn.apache.org/viewvc/aurora/site/source/downloads.html.md?rev=1692500&r1=1692499&r2=1692500&view=diff
==============================================================================
--- aurora/site/source/downloads.html.md (original)
+++ aurora/site/source/downloads.html.md Fri Jul 24 13:05:53 2015
@@ -8,10 +8,10 @@
-->
## Current Release
-The current released version is *0.8.0*.
[(tar.gz)](https://www.apache.org/dyn/mirrors/mirrors.cgi/aurora/0.8.0/apache-aurora-0.8.0.tar.gz)
-[(md5)](https://www.apache.org/dist/aurora/0.8.0/apache-aurora-0.8.0.tar.gz.md5)
-[(sha)](https://www.apache.org/dist/aurora/0.8.0/apache-aurora-0.8.0.tar.gz.sha)
-[(sig)](https://www.apache.org/dist/aurora/0.8.0/apache-aurora-0.8.0.tar.gz.asc)
+The current released version is *0.9.0*.
[(tar.gz)](https://www.apache.org/dyn/mirrors/mirrors.cgi/aurora/0.9.0/apache-aurora-0.9.0.tar.gz)
+[(md5)](https://www.apache.org/dist/aurora/0.9.0/apache-aurora-0.9.0.tar.gz.md5)
+[(sha)](https://www.apache.org/dist/aurora/0.9.0/apache-aurora-0.9.0.tar.gz.sha)
+[(sig)](https://www.apache.org/dist/aurora/0.9.0/apache-aurora-0.9.0.tar.gz.asc)
To quickly get started, we reccomend using Vagrant and following the [Getting
Started guide](/documentation/latest/vagrant/).
