aurora-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jfarr...@apache.org
Subject svn commit: r1677065 [2/2] - in /aurora/site: publish/ publish/blog/ publish/blog/2015-upcoming-apache-aurora-meetups/ publish/blog/aurora-0-6-0-incubating-released/ publish/blog/aurora-0-7-0-incubating-released/ publish/community/ publish/developers/ ...
Date Thu, 30 Apr 2015 20:41:01 GMT
Modified: aurora/site/publish/documentation/latest/vagrant/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/vagrant/index.html?rev=1677065&r1=1677064&r2=1677065&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/vagrant/index.html (original)
+++ aurora/site/publish/documentation/latest/vagrant/index.html Thu Apr 30 20:41:01 2015
@@ -21,6 +21,7 @@
 	</script>
   </head>
   <body>
+	  
         <div class="container-fluid section-header">
   <div class="container">
     <div class="nav nav-bar">
@@ -139,7 +140,7 @@ and rebuilding your VM.</p>
 
 <p><code>aurorabuild</code> accepts a list of components to build and update.
To get a list of supported
 components, invoke the <code>aurorabuild</code> command with no arguments:</p>
-<pre class="highlight text"> vagrant ssh -c 'aurorabuild client'
+<pre class="highlight text"> vagrant ssh -c &#39;aurorabuild client&#39;
 </pre>
 <h2 id="shut-down-or-delete-your-local-cluster">Shut down or delete your local cluster</h2>
 
@@ -159,11 +160,11 @@ you can use the command <code>vagrant de
 <li>Cleaning the repository of build artifacts and other intermediate output with <code>git
clean -fdx</code></li>
 <li>Bringing up the vagrant environment with <code>vagrant up</code></li>
 </ul>
-
 </div>
 
   		</div>
   	  </div>
+	  
       	<div class="container-fluid section-footer buffer">
       <div class="container">
         <div class="row">

Modified: aurora/site/publish/downloads/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/downloads/index.html?rev=1677065&r1=1677064&r2=1677065&view=diff
==============================================================================
--- aurora/site/publish/downloads/index.html (original)
+++ aurora/site/publish/downloads/index.html Thu Apr 30 20:41:01 2015
@@ -21,6 +21,7 @@
 	</script>
   </head>
   <body>
+	  
         <div class="container-fluid section-header">
   <div class="container">
     <div class="nav nav-bar">
@@ -75,6 +76,7 @@ and the <a href="https://github.com/apac
 
   		</div>
   	  </div>
+	  
       	<div class="container-fluid section-footer buffer">
       <div class="container">
         <div class="row">

Modified: aurora/site/publish/index.html
URL: http://svn.apache.org/viewvc/aurora/site/publish/index.html?rev=1677065&r1=1677064&r2=1677065&view=diff
==============================================================================
--- aurora/site/publish/index.html (original)
+++ aurora/site/publish/index.html Thu Apr 30 20:41:01 2015
@@ -21,6 +21,7 @@
 	</script>
   </head>
   <body>
+	  
 	    <div class="container-fluid section-homepage-header">
   <div class="container">
     <div class="nav nav-bar">
@@ -74,6 +75,7 @@
  </div>
 </div>
 
+      
       	<div class="container-fluid section-footer buffer">
       <div class="container">
         <div class="row">

Modified: aurora/site/publish/sitemap.xml
URL: http://svn.apache.org/viewvc/aurora/site/publish/sitemap.xml?rev=1677065&r1=1677064&r2=1677065&view=diff
==============================================================================
--- aurora/site/publish/sitemap.xml (original)
+++ aurora/site/publish/sitemap.xml Thu Apr 30 20:41:01 2015
@@ -1,135 +1,139 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
-    <loc>http://aurora.apache.org/blog/2015-upcoming-apache-aurora-meetups/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
-  </url>
-  <url>
     <loc>http://aurora.apache.org/blog/aurora-0-6-0-incubating-released/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.apache.org/blog/aurora-0-7-0-incubating-released/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/blog/2015-upcoming-apache-aurora-meetups/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/client-commands/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/blog/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/developing-aurora-client/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/community/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/configuration-reference/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/developers/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/test-resource-generation/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/docs/gettingstarted/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/tutorial/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/docs/howtocontribute/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/resource-isolation/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/client-cluster-configuration/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/developing-aurora-scheduler/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/client-commands/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/configuration-tutorial/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/committers/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/cron-jobs/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/configuration-reference/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/contributing/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/configuration-tutorial/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/scheduler-storage/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/contributing/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/vagrant/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/cron-jobs/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/client-cluster-configuration/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/deploying-aurora-scheduler/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/storage-config/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/developing-aurora-client/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/monitoring/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/developing-aurora-scheduler/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.apache.org/documentation/latest/hooks/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/user-guide/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/monitoring/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/sla/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/resource-isolation/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/committers/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/scheduler-storage/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/thrift-deprecation/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/security/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/documentation/latest/deploying-aurora-scheduler/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/sla/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
+  </url>
+  <url>
+    <loc>http://aurora.apache.org/documentation/latest/storage-config/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
     <loc>http://aurora.apache.org/documentation/latest/storage/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/docs/howtocontribute/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/test-resource-generation/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/docs/gettingstarted/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/thrift-deprecation/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/tutorial/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/downloads/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/user-guide/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/developers/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/vagrant/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/community/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/documentation/latest/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
   <url>
-    <loc>http://aurora.apache.org/blog/</loc>
-    <lastmod>2015-04-07T00:00:00-07:00</lastmod>
+    <loc>http://aurora.apache.org/downloads/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
+  </url>
+  <url>
+    <loc>http://aurora.apache.org/</loc>
+    <lastmod>2015-04-30T00:00:00-04:00</lastmod>
   </url>
 </urlset>
\ 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=1677065&r1=1677064&r2=1677065&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/configuration-reference.md (original)
+++ aurora/site/source/documentation/latest/configuration-reference.md Thu Apr 30 20:41:01
2015
@@ -359,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
 

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=1677065&r1=1677064&r2=1677065&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/deploying-aurora-scheduler.md (original)
+++ aurora/site/source/documentation/latest/deploying-aurora-scheduler.md Thu Apr 30 20:41:01
2015
@@ -13,6 +13,7 @@ machines.  This guide helps you get the
   - [Storage Performance Considerations](#storage-performance-considerations)
   - [Network considerations](#network-considerations)
   - [Considerations for running jobs in docker](#considerations-for-running-jobs-in-docker)
+  - [Security Considerations](#security-considerations)
 - [Running Aurora](#running-aurora)
   - [Maintaining an Aurora Installation](#maintaining-an-aurora-installation)
   - [Monitoring](#monitoring)
@@ -34,7 +35,7 @@ machines.  This guide helps you get the
 ## Installing Aurora
 The Aurora scheduler is a standalone Java server. As part of the build process it creates
a bundle
 of all its dependencies, with the notable exceptions of the JVM and libmesos. Each target
server
-should have a JVM (Java 7 or higher) and libmesos (0.21.1) installed.
+should have a JVM (Java 7 or higher) and libmesos (0.22.0) installed.
 
 ### Creating the Distribution .zip File (Optional)
 To create a distribution for installation you will need build tools installed. On Ubuntu
this can be
@@ -183,6 +184,10 @@ For example, monit can be configured wit
 
 assuming you set `-http_port=8081`.
 
+## Security Considerations
+
+See [security.md](/documentation/latest/security/).
+
 ### Maintaining an Aurora Installation
 
 ### Monitoring

Modified: aurora/site/source/documentation/latest/monitoring.md
URL: http://svn.apache.org/viewvc/aurora/site/source/documentation/latest/monitoring.md?rev=1677065&r1=1677064&r2=1677065&view=diff
==============================================================================
--- aurora/site/source/documentation/latest/monitoring.md (original)
+++ aurora/site/source/documentation/latest/monitoring.md Thu Apr 30 20:41:01 2015
@@ -74,133 +74,108 @@ recommend you start with a strict value
 adjust thresholds as you see fit. Feel free to ask us if you would like to validate that
your alerts
 and thresholds make sense.
 
-#### `jvm_uptime_secs`
+## Important stats
+
+### `jvm_uptime_secs`
 Type: integer counter
 
-#### Description
 The number of seconds the JVM process has been running. Comes from
 [RuntimeMXBean#getUptime()](http://docs.oracle.com/javase/7/docs/api/java/lang/management/RuntimeMXBean.html#getUptime\(\))
 
-#### Alerting
 Detecting resets (decreasing values) on this stat will tell you that the scheduler is failing
to
 stay alive.
 
-#### Triage
 Look at the scheduler logs to identify the reason the scheduler is exiting.
 
-#### `system_load_avg`
+### `system_load_avg`
 Type: double gauge
 
-#### Description
 The current load average of the system for the last minute. Comes from
 [OperatingSystemMXBean#getSystemLoadAverage()](http://docs.oracle.com/javase/7/docs/api/java/lang/management/OperatingSystemMXBean.html?is-external=true#getSystemLoadAverage\(\)).
 
-#### Alerting
 A high sustained value suggests that the scheduler machine may be over-utilized.
 
-#### Triage
 Use standard unix tools like `top` and `ps` to track down the offending process(es).
 
-#### `process_cpu_cores_utilized`
+### `process_cpu_cores_utilized`
 Type: double gauge
 
-#### Description
 The current number of CPU cores in use by the JVM process. This should not exceed the number
of
 logical CPU cores on the machine. Derived from
 [OperatingSystemMXBean#getProcessCpuTime()](http://docs.oracle.com/javase/7/docs/jre/api/management/extension/com/sun/management/OperatingSystemMXBean.html)
 
-#### Alerting
 A high sustained value indicates that the scheduler is overworked. Due to current internal
design
 limitations, if this value is sustained at `1`, there is a good chance the scheduler is under
water.
 
-#### Triage
 There are two main inputs that tend to drive this figure: task scheduling attempts and status
 updates from Mesos.  You may see activity in the scheduler logs to give an indication of
where
 time is being spent.  Beyond that, it really takes good familiarity with the code to effectively
 triage this.  We suggest engaging with an Aurora developer.
 
-#### `task_store_LOST`
+### `task_store_LOST`
 Type: integer gauge
 
-#### Description
 The number of tasks stored in the scheduler that are in the `LOST` state, and have been rescheduled.
 
-#### Alerting
 If this value is increasing at a high rate, it is a sign of trouble.
 
-#### Triage
 There are many sources of `LOST` tasks in Mesos: the scheduler, master, slave, and executor
can all
 trigger this.  The first step is to look in the scheduler logs for `LOST` to identify where
the
 state changes are originating.
 
-#### `scheduler_resource_offers`
+### `scheduler_resource_offers`
 Type: integer counter
 
-#### Description
 The number of resource offers that the scheduler has received.
 
-#### Alerting
 For a healthy scheduler, this value must be increasing over time.
 
-##### Triage
 Assuming the scheduler is up and otherwise healthy, you will want to check if the master
thinks it
 is sending offers. You should also look at the master's web interface to see if it has a
large
 number of outstanding offers that it is waiting to be returned.
 
-#### `framework_registered`
+### `framework_registered`
 Type: binary integer counter
 
-#### Description
 Will be `1` for the leading scheduler that is registered with the Mesos master, `0` for passive
 schedulers,
 
-#### Alerting
 A sustained period without a `1` (or where `sum() != 1`) warrants investigation.
 
-#### Triage
 If there is no leading scheduler, look in the scheduler and master logs for why.  If there
are
 multiple schedulers claiming leadership, this suggests a split brain and warrants filing
a critical
 bug.
 
-#### `rate(scheduler_log_native_append_nanos_total)/rate(scheduler_log_native_append_events)`
+### `rate(scheduler_log_native_append_nanos_total)/rate(scheduler_log_native_append_events)`
 Type: rate ratio of integer counters
 
-#### Description
 This composes two counters to compute a windowed figure for the latency of replicated log
writes.
 
-#### Alerting
 A hike in this value suggests disk bandwidth contention.
 
-#### Triage
 Look in scheduler logs for any reported oddness with saving to the replicated log. Also use
 standard tools like `vmstat` and `iotop` to identify whether the disk has become slow or
 over-utilized. We suggest using a dedicated disk for the replicated log to mitigate this.
 
-#### `timed_out_tasks`
+### `timed_out_tasks`
 Type: integer counter
 
-#### Description
 Tracks the number of times the scheduler has given up while waiting
 (for `-transient_task_state_timeout`) to hear back about a task that is in a transient state
 (e.g. `ASSIGNED`, `KILLING`), and has moved to `LOST` before rescheduling.
 
-#### Alerting
 This value is currently known to increase occasionally when the scheduler fails over
 ([AURORA-740](https://issues.apache.org/jira/browse/AURORA-740)). However, any large spike
in this
 value warrants investigation.
 
-#### Triage
 The scheduler will log when it times out a task. You should trace the task ID of the timed
out
 task into the master, slave, and/or executors to determine where the message was dropped.
 
-#### `http_500_responses_events`
+### `http_500_responses_events`
 Type: integer counter
 
-#### Description
 The total number of HTTP 500 status responses sent by the scheduler. Includes API and asset
serving.
 
-#### Alerting
 An increase warrants investigation.
 
-#### Triage
 Look in scheduler logs to identify why the scheduler returned a 500, there should be a stack
trace.



Mime
View raw message