mesos-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ji...@apache.org
Subject svn commit: r1748304 [2/4] - in /mesos/site/publish: ./ blog/ blog/mesos-0-28-2-released/ documentation/ documentation/agent-recovery/ documentation/allocation-module/ documentation/authorization/ documentation/c++-style-guide/ documentation/committers...
Date Mon, 13 Jun 2016 19:19:13 GMT
Modified: mesos/site/publish/documentation/latest/executor-http-api/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/executor-http-api/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/executor-http-api/index.html (original)
+++ mesos/site/publish/documentation/latest/executor-http-api/index.html Mon Jun 13 19:19:12 2016
@@ -98,12 +98,7 @@
 
 <h2>Overview</h2>
 
-<p>The executor interacts with Mesos via  &ldquo;/api/v1/executor&rdquo; endpoint hosted by the Mesos agent. The fully qualified URL of the endpoint might look like:</p>
-
-<pre><code>http://agenthost:5051/api/v1/executor
-</code></pre>
-
-<p>Note that we refer to this endpoint with its suffix &ldquo;/executor&rdquo; in the rest of this document. This endpoint accepts HTTP POST requests with data encoded as JSON (Content-Type: application/json) or binary Protobuf (Content-Type: application/x-protobuf). The first request that the executor sends to &ldquo;/executor&rdquo; endpoint is called SUBSCRIBE and results in a streaming response (&ldquo;200 OK&rdquo; status code with Transfer-Encoding: chunked). <strong>Executors are expected to keep the subscription connection open as long as possible (barring errors in network, agent process restarts, software bugs etc.) and incrementally process the response</strong> (NOTE: HTTP client libraries that can only parse the response after the connection is closed cannot be used). For the encoding used, please refer to <strong>Events</strong> section below.</p>
+<p>The executor interacts with Mesos via the <a href="/documentation/latest/./endpoints/slave/api/v1/executor/">/api/v1/executor</a> agent endpoint. Note that we refer to this endpoint with its suffix &ldquo;/executor&rdquo; in the rest of this document. This endpoint accepts HTTP POST requests with data encoded as JSON (Content-Type: application/json) or binary Protobuf (Content-Type: application/x-protobuf). The first request that the executor sends to &ldquo;/executor&rdquo; endpoint is called SUBSCRIBE and results in a streaming response (&ldquo;200 OK&rdquo; status code with Transfer-Encoding: chunked). <strong>Executors are expected to keep the subscription connection open as long as possible (barring errors in network, agent process restarts, software bugs etc.) and incrementally process the response</strong> (NOTE: HTTP client libraries that can only parse the response after the connection is closed cannot be used). For the encoding used, please refer to <strong>Events</stro
 ng> section below.</p>
 
 <p>All the subsequent (non-<code>SUBSCRIBE</code>) requests to the &ldquo;/executor&rdquo; endpoint (see details below in <strong>Calls</strong> section) must be sent using a different connection(s) than the one being used for subscription. The agent responds to these HTTP POST requests with &ldquo;202 Accepted&rdquo; status codes (or, for unsuccessful requests, with 4xx or 5xx status codes; details in later sections). The &ldquo;202 Accepted&rdquo; response means that a request has been accepted for processing, not that the processing of the request has been completed. The request might or might not be acted upon by Mesos (e.g., agent fails during the processing of the request). Any asynchronous responses from these requests will be streamed on the long-lived subscription connection.</p>
 
@@ -289,7 +284,7 @@ HTTP/1.1 202 Accepted
 
 <p>Executor is expected to keep a <strong>persistent</strong> connection open to &ldquo;/executor&rdquo; endpoint even after getting a <code>SUBSCRIBED</code> HTTP Response event. This is indicated by &ldquo;Connection: keep-alive&rdquo; and &ldquo;Transfer-Encoding: chunked&rdquo; headers with <em>no</em> &ldquo;Content-Length&rdquo; header set. All subsequent events that are relevant to this executor generated by Mesos are streamed on this connection. agent encodes each Event in <a href="/documentation/latest/./scheduler-http-api/#recordio-response-format">RecordIO</a> format, i.e., string representation of length of the event in bytes followed by JSON or binary Protobuf  (possibly compressed) encoded event. Note that the value of length will never be ‘0’ and the size of the length will be the size of unsigned integer (i.e., 64 bits). Also, note that the <code>RecordIO</code> encoding should be decoded by the executor whereas the underlying HTTP chunked encoding is typic
 ally invisible at the application (executor) layer. The type of content encoding used for the events will be determined by the accept header of the POST request (e.g., &ldquo;Accept: application/json&rdquo;).</p>
 
-<p>The following events are currently sent by the agent. The canonical source of this information is at <a href="include/mesos/v1/executor/executor.proto">executor.proto</a>. Note that when sending JSON encoded events, agent encodes raw bytes in Base64 and strings in UTF-8.</p>
+<p>The following events are currently sent by the agent. The canonical source of this information is at <a href="https://github.com/apache/mesos/blob/master/include/mesos/v1/executor/executor.proto">executor.proto</a>. Note that when sending JSON encoded events, agent encodes raw bytes in Base64 and strings in UTF-8.</p>
 
 <h3>SUBSCRIBED</h3>
 
@@ -302,6 +297,7 @@ HTTP/1.1 202 Accepted
 <p>The executor must maintain a list of unacknowledged tasks (see <code>SUBSCRIBE</code> in <code>Calls</code> section). If for some reason, the executor is disconnected from the agent, these tasks must be sent as part of <code>SUBSCRIBE</code> request in the <code>tasks</code> field.</p>
 
 <pre><code>LAUNCH Event (JSON)
+
 &lt;event-length&gt;
 {
   "type": "LAUNCH",
@@ -337,6 +333,7 @@ HTTP/1.1 202 Accepted
 <p>The <code>KILL</code> event is sent whenever the scheduler needs to stop execution of a specific task. The executor is required to send a terminal update (e.g., <code>TASK_FINISHED</code>, <code>TASK_KILLED</code> or <code>TASK_FAILED</code>) back to the agent once it has stopped/killed the task. Mesos will mark the task resources as freed once the terminal update is received.</p>
 
 <pre><code>LAUNCH Event (JSON)
+
 &lt;event-length&gt;
 {
   "type" : "KILL",
@@ -351,6 +348,7 @@ HTTP/1.1 202 Accepted
 <p>Sent by the agent in order to signal the executor that a status update was received as part of the reliable message passing mechanism. Acknowledged updates must not be retried.</p>
 
 <pre><code>ACKNOWLEDGED Event (JSON)
+
 &lt;event-length&gt;
 {
   "type" : "ACKNOWLEDGED",
@@ -366,6 +364,7 @@ HTTP/1.1 202 Accepted
 <p>Custom message generated by the scheduler and forwarded all the way to the executor. These messages are delivered &ldquo;as-is&rdquo; by Mesos and have no delivery guarantees. It is up to the scheduler to retry if a message is dropped for any reason. Note that <code>data</code> is raw bytes encoded as Base64.</p>
 
 <pre><code>MESSAGE Event (JSON)
+
 &lt;event-length&gt;
 {
   "type" : "MESSAGE",
@@ -380,6 +379,7 @@ HTTP/1.1 202 Accepted
 <p>Sent by the agent in order to shutdown the executor. Once an executor gets a <code>SHUTDOWN</code> event it is required to kill all its tasks, send <code>TASK_KILLED</code> updates and gracefully exit. If an executor doesn&rsquo;t terminate within a certain period <code>MESOS_EXECUTOR_SHUTDOWN_GRACE_PERIOD</code> (an environment variable set by the agent upon executor startup), the agent will forcefully destroy the container where the executor is running. The agent would then send <code>TASK_LOST</code> updates for any remaining active tasks of this executor.</p>
 
 <pre><code>SHUTDOWN Event (JSON)
+
 &lt;event-length&gt;
 {
   "type" : "SHUTDOWN"
@@ -391,6 +391,7 @@ HTTP/1.1 202 Accepted
 <p>Sent by the agent when an asynchronous error event is generated. It is recommended that the executor abort when it receives an error event and retry subscription.</p>
 
 <pre><code>ERROR Event (JSON)
+
 &lt;event-length&gt;
 {
   "type" : "ERROR",
@@ -424,6 +425,8 @@ HTTP/1.1 202 Accepted
 
 <p>NOTE: Additionally, the executor also inherits all the agent&rsquo;s environment variables.</p>
 
+<p><a name="disconnections"></a></p>
+
 <h2>Disconnections</h2>
 
 <p>An executor considers itself disconnected if the persistent subscription connection (opened via SUBSCRIBE request) to &ldquo;/executor&rdquo; breaks. The disconnection can happen due to an agent process failure etc.</p>
@@ -442,10 +445,12 @@ HTTP/1.1 202 Accepted
 
 <ul>
 <li><strong>reconnect</strong> (default): This mode allows the agent to reconnect with any of it’s old live executors provided the framework has enabled checkpointing. The recovery of the agent is only marked complete once all the disconnected executors have connected and hung executors have been destroyed. Hence, it is mandatory that every executor retries at least once within the interval (<code>MESOS_SUBSCRIPTION_BACKOFF_MAX</code>) to ensure it is not shutdown by the agent due to being hung/unresponsive.</li>
-<li><strong>cleanup</strong> : This mode kills any old live executors and then exits the agent. This is usually done by operators when making a non-compatible agent/executor upgrade. Upon receiving a <code>SUBSCRIBE</code> request from the executor of a framework with checkpointing enabled, the agent would send it a <code>SHUTDOWN</code> event as soon as it reconnects. For hung executors, the agent would wait for a duration of <code>--executor_shutdown_grace_period</code> (configurable at agent startup) and then forcefully kill the container where the executor is running in.</li>
+<li><strong>cleanup</strong>: This mode kills any old live executors and then exits the agent. This is usually done by operators when making a non-compatible agent/executor upgrade. Upon receiving a <code>SUBSCRIBE</code> request from the executor of a framework with checkpointing enabled, the agent would send it a <code>SHUTDOWN</code> event as soon as it reconnects. For hung executors, the agent would wait for a duration of <code>--executor_shutdown_grace_period</code> (configurable at agent startup) and then forcefully kill the container where the executor is running in.</li>
 </ul>
 
 
+<p><a name="backoff-strategies"></a></p>
+
 <h2>Backoff Strategies</h2>
 
 <p>Executors are encouraged to retry subscription using a suitable backoff strategy like linear backoff, when they notice a disconnection with the agent. A disconnection typically happens when the agent process terminates (e.g., restarted for an upgrade). Each retry interval should be bounded by the value of <code>MESOS_SUBSCRIPTION_BACKOFF_MAX</code> which is set as an environment variable.</p>

Modified: mesos/site/publish/documentation/latest/external-containerizer/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/external-containerizer/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/external-containerizer/index.html (original)
+++ mesos/site/publish/documentation/latest/external-containerizer/index.html Mon Jun 13 19:19:12 2016
@@ -203,6 +203,8 @@ container. Their order however is not de
 
 <p><img src="/assets/img/documentation/ec_kill_seqdiag.png?raw=true" alt="Resource Limitation Scheme" /></p>
 
+<p><a name="agent-recovery-overview"></a></p>
+
 <h2>Agent Recovery Overview</h2>
 
 <ul>
@@ -474,6 +476,8 @@ include/mesos/containerizer/containerize
 
 <h1>Environment</h1>
 
+<p><a name="sandbox"></a></p>
+
 <h2><strong>Sandbox</strong></h2>
 
 <p>A sandbox environment is formed by <code>cd</code> into the work-directory of the
@@ -508,6 +512,8 @@ calls to <code>launch</code>.</li>
 
 <h1>Debugging</h1>
 
+<p><a name="enhanced-verbosity-logging"></a></p>
+
 <h2>Enhanced Verbosity Logging</h2>
 
 <p>For receiving an increased level of status information from the EC
@@ -581,6 +587,8 @@ I0603 02:12:34.165686 174215168 external
 00000240:  3033 4000
 </code></pre>
 
+<p><a name="record-io-deserializing-example"></a></p>
+
 <h2>Record-IO De/Serializing Example</h2>
 
 <p>How to send and receive such record-io formatted message

Modified: mesos/site/publish/documentation/latest/high-availability/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/high-availability/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/high-availability/index.html (original)
+++ mesos/site/publish/documentation/latest/high-availability/index.html Mon Jun 13 19:19:12 2016
@@ -119,7 +119,7 @@
 
 <p>From now on, the Mesos masters and agents all communicate with ZooKeeper to find out which master is the current leading master. This is in addition to the usual communication between the leading master and the agents.</p>
 
-<p>In addition to ZooKeeper, one can get the location of the leading master by sending an HTTP request to <a href="/documentation/latest/./master/redirect/">/redirect</a> endpoint on any master.</p>
+<p>In addition to ZooKeeper, one can get the location of the leading master by sending an HTTP request to <a href="/documentation/latest/./endpoints/master/redirect/">/redirect</a> endpoint on any master.</p>
 
 <p>For HTTP endpoints that only work at the leading master, requests made to endpoints at a non-leading master will result in either a <code>307 Temporary Redirect</code> (with the location of the leading master) or <code>503 Service Unavailable</code> (if the master does not know who the current leader is).</p>
 

Modified: mesos/site/publish/documentation/latest/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/index.html (original)
+++ mesos/site/publish/documentation/latest/index.html Mon Jun 13 19:19:12 2016
@@ -211,6 +211,7 @@
 <ul>
 <li><a href="/documentation/latest/./powered-by-mesos/">Powered by Mesos</a> lists organizations and software that are powered by Apache Mesos.</li>
 <li><a href="https://www.usenix.org/conference/nsdi11/mesos-platform-fine-grained-resource-sharing-data-center">Academic Papers and Project History</a></li>
+<li><a href="/documentation/latest/./design-docs/">Design docs</a> list of design documents for various Mesos features</li>
 </ul>
 
 

Modified: mesos/site/publish/documentation/latest/markdown-style-guide/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/markdown-style-guide/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/markdown-style-guide/index.html (original)
+++ mesos/site/publish/documentation/latest/markdown-style-guide/index.html Mon Jun 13 19:19:12 2016
@@ -184,7 +184,7 @@ Continued longer note.
 &lt;/table&gt;
 </code></pre>
 
-<h2>Indendation and Whitespace</h2>
+<h2>Indentation and Whitespace</h2>
 
 <p>We use no extra indentation in markdown files.
 We have one new line after section headings and two blank lines

Modified: mesos/site/publish/documentation/latest/mesos-containerizer/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/mesos-containerizer/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/mesos-containerizer/index.html (original)
+++ mesos/site/publish/documentation/latest/mesos-containerizer/index.html Mon Jun 13 19:19:12 2016
@@ -167,7 +167,7 @@ specify <code>--enforce_container_disk_q
 
 <p>The Posix Disk isolator reports disk usage for each sandbox by
 periodically running the <code>du</code> command. The disk usage can be retrieved
-from the resource statistics endpoint (<a href="/documentation/latest/./endpoints/monitor/statistics/">/monitor/statistics</a>).</p>
+from the resource statistics endpoint (<a href="/documentation/latest/./endpoints/slave/monitor/statistics/">/monitor/statistics</a>).</p>
 
 <p>The interval between two <code>du</code>s can be controlled by the agent flag
 <code>--container_disk_watch_interval</code>. For example,
@@ -362,7 +362,7 @@ secondary handle to the net_cls cgroup a
 by writing to <code>net_cls.classid</code>. The cgroups/net_cls isolator exposes
 the assigned net_cls handle to operators by exposing the handle as
 part of the <code>ContainerStatus</code> &mdash;associated with any task running within
-the container&mdash; in the agent&rsquo;s <code>state</code> endpoint.</p>
+the container&mdash; in the agent&rsquo;s <a href="/documentation/latest/./endpoints/slave/state/">/state</a> endpoint.</p>
 
   </div>
 </div>

Modified: mesos/site/publish/documentation/latest/monitoring/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/monitoring/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/monitoring/index.html (original)
+++ mesos/site/publish/documentation/latest/monitoring/index.html Mon Jun 13 19:19:12 2016
@@ -125,13 +125,9 @@ above or below a threshold for a sustain
 
 <h2>Master Nodes</h2>
 
-<p>Metrics from the master node are available at the following URL:</p>
-
-<pre><code>http://&lt;mesos-master-ip&gt;:5050/metrics/snapshot
-</code></pre>
-
-<p>The response is a JSON object that contains metrics names and values as
-key-value pairs.</p>
+<p>Metrics from each master node are available via the
+<a href="/documentation/latest/./endpoints/metrics/snapshot/">/metrics/snapshot</a> master endpoint.  The response
+is a JSON object that contains metrics names and values as key-value pairs.</p>
 
 <h3>Observability metrics</h3>
 
@@ -1196,13 +1192,9 @@ failures, bugs in one of the frameworks,
 
 <h2>Agent Nodes</h2>
 
-<p>Metrics from each agent node are available at the following URL:</p>
-
-<pre><code>http://&lt;mesos-agent&gt;:5051/metrics/snapshot
-</code></pre>
-
-<p>The response is a JSON object that contains metrics names and values as key-
-value pairs.</p>
+<p>Metrics from each agent node are available via the
+<a href="/documentation/latest/./endpoints/metrics/snapshot/">/metrics/snapshot</a> agent endpoint.  The response
+is a JSON object that contains metrics names and values as key-value pairs.</p>
 
 <h3>Observability Metrics</h3>
 

Modified: mesos/site/publish/documentation/latest/network-monitoring/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/network-monitoring/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/network-monitoring/index.html (original)
+++ mesos/site/publish/documentation/latest/network-monitoring/index.html Mon Jun 13 19:19:12 2016
@@ -98,7 +98,7 @@
 isolation. The network isolation prevents a single container from exhausting the
 available network ports, consuming an unfair share of the network bandwidth or
 significantly delaying packet transmission for others. Network statistics for
-each active container are published through the <a href="/documentation/latest/./endpoints/monitor/statistics/">/monitor/statistics</a>
+each active container are published through the <a href="/documentation/latest/./endpoints/slave/monitor/statistics/">/monitor/statistics</a>
 endpoint on the agent. The network isolation is transparent for the majority of
 tasks running on a agent (those that bind to port 0 and let the kernel allocate
 their port).</p>
@@ -286,7 +286,7 @@ enabled would thus be:</p>
 <h2>Monitoring container network statistics</h2>
 
 <p>Mesos exposes statistics from the Linux network stack for each container network
-on the <a href="/documentation/latest/./endpoints/monitor/statistics/">/monitor/statistics</a> agent endpoint.</p>
+on the <a href="/documentation/latest/./endpoints/slave/monitor/statistics/">/monitor/statistics</a> agent endpoint.</p>
 
 <p>From the network interface inside the container, we report the following
 counters (since container creation) under the <code>statistics</code> key:</p>

Modified: mesos/site/publish/documentation/latest/operational-guide/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/operational-guide/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/operational-guide/index.html (original)
+++ mesos/site/publish/documentation/latest/operational-guide/index.html Mon Jun 13 19:19:12 2016
@@ -201,7 +201,7 @@ information, quota information, etc). To
 
 <h2>HTTP requests to non-leading master</h2>
 
-<p>HTTP requests to some master endpoints (e.g., <a href="/documentation/latest/./master/state/">/state</a>, <a href="/documentation/latest/./master/machine/down/">/machine/down</a>) can only be answered by the leading master. Such requests made to a non-leading master will result in either a <code>307 Temporary Redirect</code> (with the location of the leading master) or <code>503 Service Unavailable</code> (if the master does not know who the current leader is).</p>
+<p>HTTP requests to some master endpoints (e.g., <a href="/documentation/latest/./endpoints/master/state/">/state</a>, <a href="/documentation/latest/./endpoints/master/machine/down/">/machine/down</a>) can only be answered by the leading master. Such requests made to a non-leading master will result in either a <code>307 Temporary Redirect</code> (with the location of the leading master) or <code>503 Service Unavailable</code> (if the master does not know who the current leader is).</p>
 
   </div>
 </div>

Modified: mesos/site/publish/documentation/latest/persistent-volume/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/persistent-volume/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/persistent-volume/index.html (original)
+++ mesos/site/publish/documentation/latest/persistent-volume/index.html Mon Jun 13 19:19:12 2016
@@ -151,6 +151,8 @@ interfaces described above.</p>
 
 <h2>Framework Scheduler API</h2>
 
+<p><a name="offer-operation-create"></a></p>
+
 <h3><code>Offer::Operation::Create</code></h3>
 
 <p>A framework can create volumes through the resource offer cycle.  Suppose we
@@ -256,7 +258,7 @@ persistent volume:</p>
 <h3><code>Offer::Operation::Destroy</code></h3>
 
 <p>A framework can destroy persistent volumes through the resource offer cycle. In
-<a href="#offeroperationcreate">Offer::Operation::Create</a>, we created a persistent
+<a href="#offer-operation-create">Offer::Operation::Create</a>, we created a persistent
 volume from 2048 MB of disk resources. The volume will continue to exist until
 it is explicitly destroyed. Suppose we would like to destroy the volume we
 created. First, we receive a resource offer (copy/pasted from above):</p>
@@ -493,6 +495,15 @@ volumes:</p>
 <li><p>A single <code>acceptOffers</code> call can be used to both create a new dynamic
 reservation (via <code>Offer::Operation::Reserve</code>) and create a new persistent
 volume on those newly reserved resources (via <code>Offer::Operation::Create</code>).</p></li>
+<li><p>Volume IDs must be unique per role on each agent. However, it is strongly
+recommended that frameworks use globally unique volume IDs, to avoid potential
+confusion between volumes on different agents that use the same volume
+ID. Note also that the agent ID where a volume resides might change over
+time. For example, suppose a volume is created on an agent and then the
+agent&rsquo;s host machine is rebooted. When the agent registers with Mesos after
+the reboot, it will be assigned a new AgentID&mdash;but it will retain the same
+volume it had previouly. Hence, frameworks should not assume that using the
+pair &lt;AgentID, VolumeID> is a stable way to identify a volume in a cluster.</p></li>
 <li><p>Attempts to dynamically reserve resources or create persistent volumes might
 fail&mdash;for example, because the network message containing the operation did
 not reach the master or because the master rejected the operation.

Modified: mesos/site/publish/documentation/latest/reservation/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/reservation/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/reservation/index.html (original)
+++ mesos/site/publish/documentation/latest/reservation/index.html Mon Jun 13 19:19:12 2016
@@ -102,6 +102,8 @@ and authorized <strong>frameworks</stron
 
 <p>In both types of reservations, resources are reserved for a <a href="/documentation/latest/./roles/"><strong>role</strong></a>.</p>
 
+<p><a name="static-reservation"></a></p>
+
 <h2>Static Reservation</h2>
 
 <p>An operator can configure a slave with resources reserved for a role.
@@ -128,7 +130,7 @@ We start the slave like so:</p>
 
 <h2>Dynamic Reservation</h2>
 
-<p>As mentioned in <a href="#static-reservation-since-0140">Static Reservation</a>, specifying
+<p>As mentioned in <a href="#static-reservation">Static Reservation</a>, specifying
 the reserved resources via the <code>--resources</code> flag makes the reservation static.
 That is, statically reserved resources cannot be reserved for another role nor
 be unreserved. Dynamic reservation enables operators and authorized frameworks
@@ -181,6 +183,8 @@ same slave and use the same role.</p>
 
 <h3>Framework Scheduler API</h3>
 
+<p><a name="offer-operation-reserve"></a></p>
+
 <h4><code>Offer::Operation::Reserve</code></h4>
 
 <p>A framework can reserve resources through the resource offer cycle.  Suppose we
@@ -281,7 +285,7 @@ following reserved resources:</p>
 <h4><code>Offer::Operation::Unreserve</code></h4>
 
 <p>A framework can unreserve resources through the resource offer cycle.
-In <a href="#offeroperationreserve">Offer::Operation::Reserve</a>, we reserved 8 CPUs
+In <a href="#offer-operation-reserve">Offer::Operation::Reserve</a>, we reserved 8 CPUs
 and 4096 MB of RAM on a particular slave for our <code>role</code>. The master will
 continue to only offer these resources to our <code>role</code>. Suppose we would like to
 unreserve these resources. First, we receive a resource offer (copy/pasted

Modified: mesos/site/publish/documentation/latest/scheduler-http-api/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/scheduler-http-api/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/scheduler-http-api/index.html (original)
+++ mesos/site/publish/documentation/latest/scheduler-http-api/index.html Mon Jun 13 19:19:12 2016
@@ -98,12 +98,7 @@
 
 <h2>Overview</h2>
 
-<p>The scheduler interacts with Mesos via  &ldquo;/api/v1/scheduler&rdquo; endpoint hosted by the Mesos master. The fully qualified URL of the endpoint might look like:</p>
-
-<pre><code>http://masterhost:5050/api/v1/scheduler
-</code></pre>
-
-<p>Note that we refer to this endpoint with its suffix &ldquo;/scheduler&rdquo; in the rest of this document. This endpoint accepts HTTP POST requests with data encoded as JSON (Content-Type: application/json) or binary Protobuf (Content-Type: application/x-protobuf). The first request that a scheduler sends to &ldquo;/scheduler&rdquo; endpoint is called SUBSCRIBE and results in a streaming response (&ldquo;200 OK&rdquo; status code with Transfer-Encoding: chunked). <strong>Schedulers are expected to keep the subscription connection open as long as possible (barring errors in network, software, hardware etc.) and incrementally process the response</strong> (NOTE: HTTP client libraries that can only parse the response after the connection is closed cannot be used). For the encoding used, please refer to <strong>Events</strong> section below.</p>
+<p>The scheduler interacts with Mesos via the <a href="/documentation/latest/./endpoints/master/api/v1/scheduler/">/api/v1/scheduler</a> master endpoint. Note that we refer to this endpoint with its suffix &ldquo;/scheduler&rdquo; in the rest of this document. This endpoint accepts HTTP POST requests with data encoded as JSON (Content-Type: application/json) or binary Protobuf (Content-Type: application/x-protobuf). The first request that a scheduler sends to &ldquo;/scheduler&rdquo; endpoint is called SUBSCRIBE and results in a streaming response (&ldquo;200 OK&rdquo; status code with Transfer-Encoding: chunked). <strong>Schedulers are expected to keep the subscription connection open as long as possible (barring errors in network, software, hardware etc.) and incrementally process the response</strong> (NOTE: HTTP client libraries that can only parse the response after the connection is closed cannot be used). For the encoding used, please refer to <strong>Events</strong> section 
 below.</p>
 
 <p>All the subsequent (non-<code>SUBSCRIBE</code>) requests to &ldquo;/scheduler&rdquo; endpoint (see details below in <strong>Calls</strong> section) must be sent using a different connection(s) than the one being used for subscription. Master responds to these HTTP POST requests with &ldquo;202 Accepted&rdquo; status codes (or, for unsuccessful requests, with 4xx or 5xx status codes; details in later sections). The &ldquo;202 Accepted&rdquo; response means that a request has been accepted for processing, not that the processing of the request has been completed. The request might or might not be acted upon by Mesos (e.g., master fails during the processing of the request). Any asynchronous responses from these requests will be streamed on the long-lived subscription connection.</p>
 
@@ -458,7 +453,7 @@ HTTP/1.1 202 Accepted
 
 <p>Scheduler is expected to keep a <strong>persistent</strong> connection open to &ldquo;/scheduler&rdquo; endpoint even after getting a SUBSCRIBED HTTP Response event. This is indicated by &ldquo;Connection: keep-alive&rdquo; and &ldquo;Transfer-Encoding: chunked&rdquo; headers with <em>no</em> &ldquo;Content-Length&rdquo; header set. All subsequent events that are relevant to this framework  generated by Mesos are streamed on this connection. Master encodes each Event in RecordIO format, i.e., string representation of length of the event in bytes followed by JSON or binary Protobuf  (possibly compressed) encoded event. Note that the value of length will never be &lsquo;0&rsquo; and the size of the length will be the size of unsigned integer (i.e., 64 bits). Also, note that the RecordIO encoding should be decoded by the scheduler whereas the underlying HTTP chunked encoding is typically invisible at the application (scheduler) layer. The type of content encoding used for the events
  will be determined by the accept header of the POST request (e.g., Accept: application/json).</p>
 
-<p>The following events are currently sent by the master. The canonical source of this information is at <a href="include/mesos/v1/scheduler/scheduler.proto">scheduler.proto</a>. Note that when sending JSON encoded events, master encodes raw bytes in Base64 and strings in UTF-8.</p>
+<p>The following events are currently sent by the master. The canonical source of this information is at <a href="https://github.com/apache/mesos/blob/master/include/mesos/v1/scheduler/scheduler.proto">scheduler.proto</a>. Note that when sending JSON encoded events, master encodes raw bytes in Base64 and strings in UTF-8.</p>
 
 <h3>SUBSCRIBED</h3>
 
@@ -469,6 +464,7 @@ HTTP/1.1 202 Accepted
 <p>Sent by the master whenever there are new resources that can be offered to the framework. Each offer corresponds to a set of resources on an agent. Until the scheduler &lsquo;Accept&rsquo;s or 'Decline&rsquo;s an offer the resources are considered allocated to the scheduler, unless the offer is otherwise rescinded, e.g. due to a lost agent or <code>--offer_timeout</code>.</p>
 
 <pre><code>OFFERS Event (JSON)
+
 &lt;event-length&gt;
 {
   "type"    : "OFFERS",
@@ -491,6 +487,7 @@ HTTP/1.1 202 Accepted
 <p>Sent by the master when a particular offer is no longer valid (e.g., the agent corresponding to the offer has been removed) and hence needs to be rescinded. Any future calls (<code>ACCEPT</code> / <code>DECLINE</code>) made by the scheduler regarding this offer will be invalid.</p>
 
 <pre><code>RESCIND Event (JSON)
+
 &lt;event-length&gt;
 {
   "type"    : "RESCIND",
@@ -587,7 +584,7 @@ HTTP/1.1 202 Accepted
 
 <p>If master realizes that the subscription connection is broken, it marks the scheduler as &ldquo;disconnected&rdquo; and starts a failover timeout (failover timeout is part of FrameworkInfo). It also drops any pending events in its queue. Additionally, it rejects subsequent non-subscribe HTTP requests to &ldquo;/scheduler&rdquo; with &ldquo;403 Forbidden&rdquo;, until the scheduler subscribes again with &ldquo;/scheduler&rdquo;. If the scheduler <em>does not</em> re-subscribe within the failover timeout, the master considers the scheduler gone forever and shuts down all its executors, thus killing all its tasks. Therefore, all production schedulers are recommended to use a high value (e.g., 4 weeks) for the failover timeout.</p>
 
-<p>NOTE: To force shutdown of a framework before the failover timeout elapses (e.g., during framework development and testing), either the framework can send the <code>TEARDOWN</code> call (part of the Scheduler API) or an operator can use the &ldquo;/master/teardown&rdquo; endpoint (part of the Operator API).</p>
+<p>NOTE: To force shutdown of a framework before the failover timeout elapses (e.g., during framework development and testing), either the framework can send the <code>TEARDOWN</code> call (part of the Scheduler API) or an operator can use the <a href="/documentation/latest/./endpoints/master/teardown/">/teardown</a> master endpoint (part of the Operator API).</p>
 
 <p>If the scheduler realizes that its subscription connection to &ldquo;/scheduler&rdquo; is broken or the master has changed (e.g., via ZooKeeper), it should resubscribe (using a backoff strategy). This is done by sending a <code>SUBSCRIBE</code> request (with framework ID set) on a <strong>new</strong> persistent connection to the &ldquo;/scheduler&rdquo; endpoint on the (possibly new) master. It should not send new non-subscribe HTTP requests to &ldquo;/scheduler&rdquo; unless it receives a <code>SUBSCRIBED</code> event; such requests will result in &ldquo;403 Forbidden&rdquo;.</p>
 

Modified: mesos/site/publish/documentation/latest/upgrades/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/upgrades/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/upgrades/index.html (original)
+++ mesos/site/publish/documentation/latest/upgrades/index.html Mon Jun 13 19:19:12 2016
@@ -133,24 +133,37 @@ R Removed feature/behavior
   </thead>
 <tr>
   <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Version-->
-  0.29.x
+  1.0.x
   </td>
   <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Mesos Core-->
     <ul style="padding-left:10px;">
-      <li>CD <a href="#0-29-x-allocator-metrics">Allocator Metrics</a></li>
-      <li>D <a href="#0-29-x-credentials">--credential(s) (plain text format)</a></li>
+      <li>CD <a href="#1-0-x-allocator-metrics">Allocator Metrics</a></li>
+      <li>C <a href="#1-0-x-persistent-volume">Destruction of persistent volumes</a></li>
+      <li>C <a href="#1-0-x-slave">Slave to Agent rename</a></li>
+      <li>C <a href="#1-0-x-quota-acls">Quota ACLs</a></li>
     </ul>
   </td>
   <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Flags-->
     <ul style="padding-left:10px;">
-      <li>CD <a href="#0-29-x-quota-authorization">Quota Authorization</a></li>
+      <li>D <a href="#1-0-x-docker-timeout-flag">docker_stop_timeout</a></li>
+      <li>D <a href="#1-0-x-credentials-file">credential(s) (plain text format)</a></li>
+      <li>C <a href="#1-0-x-slave">Slave to Agent rename</a></li>
+      <li>R <a href="#1-0-x-workdir">work_dir default value</a></li>
     </ul>
   </td>
   <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Framework API-->
+      <li>DC <a href="#1-0-x-executorinfo">ExecutorInfo.source</a></li>
+      <li>N <a href="#1-0-x-v1-commandinfo">CommandInfo.URI output_file</a></li>
+      <li>C <a href="#1-0-x-scheduler-proto">scheduler.proto optional fields</a></li>
+      <li>C <a href="#1-0-x-executor-proto">executor.proto optional fields</a></li>
   </td>
   <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Module API-->
+    <li>C <a href="#1-0-x-authorizer">Authorizer</a></li>
   </td>
   <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Endpoints-->
+    <li>C <a href="#1-0-x-status-code">HTTP return codes</a></li>
+    <li>R <a href="#1-0-x-status-code">/observe</a></li>
+    <li>C <a href="#1-0-x-endpoint-authorization">Added authorization</a></li>
   </td>
 </tr>
 <tr>
@@ -249,10 +262,106 @@ R Removed feature/behavior
 
 <h2>Upgrading from 0.28.x to 1.0.x</h2>
 
+<p><a name="1-0-x-allocator-metrics"></a></p>
+
+<ul>
+<li>The allocator metric named <code>allocator/event_queue_dispatches</code> is now deprecated. The new name is <code>allocator/mesos/event_queue_dispatches</code> to better support metrics for alternative allocator implementations.</li>
+</ul>
+
+
+<p><a name="1-0-x-docker-timeout-flag"></a></p>
+
+<ul>
+<li>The &ndash;docker_stop_timeout agent flag is deprecated.</li>
+</ul>
+
+
+<p><a name="1-0-x-executorinfo"></a></p>
+
+<ul>
+<li>The ExecutorInfo.source field is deprecated in favor of ExecutorInfo.labels.</li>
+</ul>
+
+
+<p><a name="1-0-x-slave"></a></p>
+
+<p>Mesos 1.0 deprecates the &lsquo;slave&rsquo; keyword in favor of &lsquo;agent&rsquo; at number of places
+  * Deprecated flags with keyword &lsquo;slave&rsquo; in favor of &lsquo;agent&rsquo;.
+  * Deprecated sandbox links with &lsquo;slave&rsquo; keyword in the WebUI.
+  * Deprecated <code>slave</code> subcommand for mesos-cli.</p>
+
+<p><a name="1-0-x-workdir"></a></p>
+
+<p>Mesos 1.0 removes the default value for the agent <code>work_dir</code>. This flag is now required, and the agent will exit immediately if it is not provided.</p>
+
+<p><a name="1-0-x-credentials-file"></a></p>
+
+<ul>
+<li>Mesos 1.0 deprecates the use of plain text credential files in favor of JSON-formatted credential files.</li>
+</ul>
+
+
+<p><a name="1-0-x-persistent-volume"></a></p>
+
+<ul>
+<li>When a persistent volume is destroyed, Mesos will now remove any data that was stored on the volume from the filesystem of the appropriate slave. In prior versions of Mesos, destroying a volume would not delete data (this was a known missing feature that has now been implemented).</li>
+</ul>
+
+
+<p><a name="1-0-x-status-code"></a></p>
+
+<ul>
+<li>Mesos 1.0 changes the HTTP status code of the following endpoints from <code>200 OK</code> to <code>202 Accepted</code>:
+
+<ul>
+<li><code>/reserve</code></li>
+<li><code>/unreserve</code></li>
+<li><code>/create-volumes</code></li>
+<li><code>/destroy-volumes</code></li>
+</ul>
+</li>
+</ul>
+
+
+<p><a name="1-0-x-v1-commandinfo"></a></p>
+
 <ul>
-<li><p>The allocator metric named <code>allocator/event_queue_dispatches</code> is now deprecated. The new name is <code>allocator/mesos/event_queue_dispatches</code> to better support metrics for alternative allocator implementations.</p></li>
-<li><p>Mesos 1.0 deprecates the use of plain text credential files in favor of JSON-formatted credential files.</p></li>
-<li><p>Mesos 1.0 deprecates <code>SET_QUOTA_WITH_ROLE</code> and <code>DESTROY_QUOTA_WITH_PRINCIPAL</code> actions with <code>UPDATE_QUOTA_WITH_ROLE</code>, as well as the <code>SetQuota</code> and <code>RemoveQuota</code> ACLs with <code>UpdateQuota</code> ACL, to control which principal(s) is authorized to set, remove and (in future releases) update quota for role(s). A new <code>GET_QUOTA_WITH_ROLE</code> action and <code>get_quotas</code> ACL are introduced to control which principal(s) can query quota status for given role(s). This affects <code>--acls</code> flag for local authorizer in the following way:</p>
+<li>Added &lsquo;output_file&rsquo; field to CommandInfo.URI in Scheduler API and v1 Scheduler HTTP API.</li>
+</ul>
+
+
+<p><a name="1-0-x-scheduler-proto"></a></p>
+
+<ul>
+<li>Changed Call and Event Type enums in scheduler.proto from required to optional for the purpose of backwards compatibility.</li>
+</ul>
+
+
+<p><a name="1-0-x-executor-proto"></a></p>
+
+<ul>
+<li>Changed Call and Event Type enums in executor.proto from required to optional for the purpose of backwards compatibility.</li>
+</ul>
+
+
+<p><a name="1-0-x-nonterminal"></a></p>
+
+<ul>
+<li>Added non-terminal task metadata to the container resource usage information.</li>
+</ul>
+
+
+<p><a name="1-0-x-observe-endpoint"></a></p>
+
+<ul>
+<li>Deleted the /observe HTTP endpoint.</li>
+</ul>
+
+
+<p><a name="1-0-x-quota-acls"></a></p>
+
+<ul>
+<li>Mesos 1.0 deprecates <code>SET_QUOTA_WITH_ROLE</code> and <code>DESTROY_QUOTA_WITH_PRINCIPAL</code> actions with <code>UPDATE_QUOTA_WITH_ROLE</code>, as well as the <code>SetQuota</code> and <code>RemoveQuota</code> ACLs with <code>UpdateQuota</code> ACL, to control which principal(s) is authorized to set, remove and (in future releases) update quota for role(s). A new <code>GET_QUOTA_WITH_ROLE</code> action and <code>get_quotas</code> ACL are introduced to control which principal(s) can query quota status for given role(s). This affects <code>--acls</code> flag for local authorizer in the following way:
 
 <ul>
 <li>It is not allowed to specify <code>update_quotas</code> and any of <code>set_quotas</code> or <code>remove_quotas</code> at the same time. Local authorizor will error out in such case;</li>
@@ -261,19 +370,30 @@ R Removed feature/behavior
 <li>If desired, operator can use <code>get_quotas</code> after upgrade to control which principal(s) is allowed to query quota status for given role(s).</li>
 </ul>
 </li>
-<li><p>When a persistent volume is destroyed, Mesos will now remove any data that was stored on the volume from the filesystem of the appropriate slave. In prior versions of Mesos, destroying a volume would not delete data (this was a known missing feature that has now been implemented).</p></li>
-<li><p>Mesos 1.0 changes the HTTP status code of the following endpoints from <code>200 OK</code> to <code>202 Accepted</code>:</p>
+</ul>
+
+
+<p><a name="1-0-x-authorizer"></a></p>
 
 <ul>
-<li><code>/reserve</code></li>
-<li><code>/unreserve</code></li>
-<li><code>/create-volumes</code></li>
-<li><code>/destroy-volumes</code></li>
+<li>Mesos 1.0 contains a number of authorizer changes especially effecting authorizer modules:
+
+<ul>
+<li>The authorizer interface has been refactored in order to decouple the ACLs definition language from the interface. It additionally includes the option of retrieving <code>ObjectApprover</code>. An <code>ObjectApprover</code> can be used to synchronously check authorizations for a given object and is hence useful when authorizing a large number of objects and/or large objects (which need to be copied using request based authorization). NOTE: This is a <strong>breaking change</strong> for authorizer modules.</li>
+<li>Authorization based HTTP endpoint filtering enables operators to restrict what part of the cluster state a user is authorized to see. Consider for example the <code>/state</code> master endpoint: an operator can now authorize users to only see a subset of the running frameworks, tasks, or executors.</li>
+<li>Fields (i.e, <code>subject</code> and <code>object</code>) in authorization::Request protobuf are changed to optional. If these fields are not set, the request should be allowed only for ACLs with <code>ANY</code> semantics. NOTE: This is a semantic change for authorizer modules.</li>
 </ul>
 </li>
 </ul>
 
 
+<p><a name="1-0-x-endpoint-authorization"></a></p>
+
+<ul>
+<li>Mesos provides authorization a number of HTTP endpoints. Note that the some of these endpoints are used by the web UI, and thus using the web UI in a cluster with authorization enabled will require that ACLs be set appropriately. Please refer to the <a href="/documentation/latest/./authorization/">authorization documentation</a> for details.</li>
+</ul>
+
+
 <p>In order to upgrade a running cluster:</p>
 
 <ol>

Modified: mesos/site/publish/documentation/latest/versioning/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/versioning/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/versioning/index.html (original)
+++ mesos/site/publish/documentation/latest/versioning/index.html Mon Jun 13 19:19:12 2016
@@ -184,6 +184,8 @@
 </ul>
 
 
+<p><a name="api-compatibility"></a></p>
+
 <h3>API Compatibility</h3>
 
 <p>The API compatibility is determined by the corresponding protobuf guarantees.</p>

Modified: mesos/site/publish/documentation/markdown-style-guide/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/markdown-style-guide/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/markdown-style-guide/index.html (original)
+++ mesos/site/publish/documentation/markdown-style-guide/index.html Mon Jun 13 19:19:12 2016
@@ -184,7 +184,7 @@ Continued longer note.
 &lt;/table&gt;
 </code></pre>
 
-<h2>Indendation and Whitespace</h2>
+<h2>Indentation and Whitespace</h2>
 
 <p>We use no extra indentation in markdown files.
 We have one new line after section headings and two blank lines

Modified: mesos/site/publish/documentation/mesos-containerizer/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/mesos-containerizer/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/mesos-containerizer/index.html (original)
+++ mesos/site/publish/documentation/mesos-containerizer/index.html Mon Jun 13 19:19:12 2016
@@ -167,7 +167,7 @@ specify <code>--enforce_container_disk_q
 
 <p>The Posix Disk isolator reports disk usage for each sandbox by
 periodically running the <code>du</code> command. The disk usage can be retrieved
-from the resource statistics endpoint (<a href="/documentation/latest/./endpoints/monitor/statistics/">/monitor/statistics</a>).</p>
+from the resource statistics endpoint (<a href="/documentation/latest/./endpoints/slave/monitor/statistics/">/monitor/statistics</a>).</p>
 
 <p>The interval between two <code>du</code>s can be controlled by the agent flag
 <code>--container_disk_watch_interval</code>. For example,
@@ -362,7 +362,7 @@ secondary handle to the net_cls cgroup a
 by writing to <code>net_cls.classid</code>. The cgroups/net_cls isolator exposes
 the assigned net_cls handle to operators by exposing the handle as
 part of the <code>ContainerStatus</code> &mdash;associated with any task running within
-the container&mdash; in the agent&rsquo;s <code>state</code> endpoint.</p>
+the container&mdash; in the agent&rsquo;s <a href="/documentation/latest/./endpoints/slave/state/">/state</a> endpoint.</p>
 
   </div>
 </div>

Modified: mesos/site/publish/documentation/monitoring/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/monitoring/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/monitoring/index.html (original)
+++ mesos/site/publish/documentation/monitoring/index.html Mon Jun 13 19:19:12 2016
@@ -125,13 +125,9 @@ above or below a threshold for a sustain
 
 <h2>Master Nodes</h2>
 
-<p>Metrics from the master node are available at the following URL:</p>
-
-<pre><code>http://&lt;mesos-master-ip&gt;:5050/metrics/snapshot
-</code></pre>
-
-<p>The response is a JSON object that contains metrics names and values as
-key-value pairs.</p>
+<p>Metrics from each master node are available via the
+<a href="/documentation/latest/./endpoints/metrics/snapshot/">/metrics/snapshot</a> master endpoint.  The response
+is a JSON object that contains metrics names and values as key-value pairs.</p>
 
 <h3>Observability metrics</h3>
 
@@ -1196,13 +1192,9 @@ failures, bugs in one of the frameworks,
 
 <h2>Agent Nodes</h2>
 
-<p>Metrics from each agent node are available at the following URL:</p>
-
-<pre><code>http://&lt;mesos-agent&gt;:5051/metrics/snapshot
-</code></pre>
-
-<p>The response is a JSON object that contains metrics names and values as key-
-value pairs.</p>
+<p>Metrics from each agent node are available via the
+<a href="/documentation/latest/./endpoints/metrics/snapshot/">/metrics/snapshot</a> agent endpoint.  The response
+is a JSON object that contains metrics names and values as key-value pairs.</p>
 
 <h3>Observability Metrics</h3>
 

Modified: mesos/site/publish/documentation/network-monitoring/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/network-monitoring/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/network-monitoring/index.html (original)
+++ mesos/site/publish/documentation/network-monitoring/index.html Mon Jun 13 19:19:12 2016
@@ -98,7 +98,7 @@
 isolation. The network isolation prevents a single container from exhausting the
 available network ports, consuming an unfair share of the network bandwidth or
 significantly delaying packet transmission for others. Network statistics for
-each active container are published through the <a href="/documentation/latest/./endpoints/monitor/statistics/">/monitor/statistics</a>
+each active container are published through the <a href="/documentation/latest/./endpoints/slave/monitor/statistics/">/monitor/statistics</a>
 endpoint on the agent. The network isolation is transparent for the majority of
 tasks running on a agent (those that bind to port 0 and let the kernel allocate
 their port).</p>
@@ -286,7 +286,7 @@ enabled would thus be:</p>
 <h2>Monitoring container network statistics</h2>
 
 <p>Mesos exposes statistics from the Linux network stack for each container network
-on the <a href="/documentation/latest/./endpoints/monitor/statistics/">/monitor/statistics</a> agent endpoint.</p>
+on the <a href="/documentation/latest/./endpoints/slave/monitor/statistics/">/monitor/statistics</a> agent endpoint.</p>
 
 <p>From the network interface inside the container, we report the following
 counters (since container creation) under the <code>statistics</code> key:</p>

Modified: mesos/site/publish/documentation/operational-guide/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/operational-guide/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/operational-guide/index.html (original)
+++ mesos/site/publish/documentation/operational-guide/index.html Mon Jun 13 19:19:12 2016
@@ -201,7 +201,7 @@ information, quota information, etc). To
 
 <h2>HTTP requests to non-leading master</h2>
 
-<p>HTTP requests to some master endpoints (e.g., <a href="/documentation/latest/./master/state/">/state</a>, <a href="/documentation/latest/./master/machine/down/">/machine/down</a>) can only be answered by the leading master. Such requests made to a non-leading master will result in either a <code>307 Temporary Redirect</code> (with the location of the leading master) or <code>503 Service Unavailable</code> (if the master does not know who the current leader is).</p>
+<p>HTTP requests to some master endpoints (e.g., <a href="/documentation/latest/./endpoints/master/state/">/state</a>, <a href="/documentation/latest/./endpoints/master/machine/down/">/machine/down</a>) can only be answered by the leading master. Such requests made to a non-leading master will result in either a <code>307 Temporary Redirect</code> (with the location of the leading master) or <code>503 Service Unavailable</code> (if the master does not know who the current leader is).</p>
 
   </div>
 </div>

Modified: mesos/site/publish/documentation/persistent-volume/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/persistent-volume/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/persistent-volume/index.html (original)
+++ mesos/site/publish/documentation/persistent-volume/index.html Mon Jun 13 19:19:12 2016
@@ -151,6 +151,8 @@ interfaces described above.</p>
 
 <h2>Framework Scheduler API</h2>
 
+<p><a name="offer-operation-create"></a></p>
+
 <h3><code>Offer::Operation::Create</code></h3>
 
 <p>A framework can create volumes through the resource offer cycle.  Suppose we
@@ -256,7 +258,7 @@ persistent volume:</p>
 <h3><code>Offer::Operation::Destroy</code></h3>
 
 <p>A framework can destroy persistent volumes through the resource offer cycle. In
-<a href="#offeroperationcreate">Offer::Operation::Create</a>, we created a persistent
+<a href="#offer-operation-create">Offer::Operation::Create</a>, we created a persistent
 volume from 2048 MB of disk resources. The volume will continue to exist until
 it is explicitly destroyed. Suppose we would like to destroy the volume we
 created. First, we receive a resource offer (copy/pasted from above):</p>
@@ -493,6 +495,15 @@ volumes:</p>
 <li><p>A single <code>acceptOffers</code> call can be used to both create a new dynamic
 reservation (via <code>Offer::Operation::Reserve</code>) and create a new persistent
 volume on those newly reserved resources (via <code>Offer::Operation::Create</code>).</p></li>
+<li><p>Volume IDs must be unique per role on each agent. However, it is strongly
+recommended that frameworks use globally unique volume IDs, to avoid potential
+confusion between volumes on different agents that use the same volume
+ID. Note also that the agent ID where a volume resides might change over
+time. For example, suppose a volume is created on an agent and then the
+agent&rsquo;s host machine is rebooted. When the agent registers with Mesos after
+the reboot, it will be assigned a new AgentID&mdash;but it will retain the same
+volume it had previouly. Hence, frameworks should not assume that using the
+pair &lt;AgentID, VolumeID> is a stable way to identify a volume in a cluster.</p></li>
 <li><p>Attempts to dynamically reserve resources or create persistent volumes might
 fail&mdash;for example, because the network message containing the operation did
 not reach the master or because the master rejected the operation.

Modified: mesos/site/publish/documentation/reservation/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/reservation/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/reservation/index.html (original)
+++ mesos/site/publish/documentation/reservation/index.html Mon Jun 13 19:19:12 2016
@@ -102,6 +102,8 @@ and authorized <strong>frameworks</stron
 
 <p>In both types of reservations, resources are reserved for a <a href="/documentation/latest/./roles/"><strong>role</strong></a>.</p>
 
+<p><a name="static-reservation"></a></p>
+
 <h2>Static Reservation</h2>
 
 <p>An operator can configure a slave with resources reserved for a role.
@@ -128,7 +130,7 @@ We start the slave like so:</p>
 
 <h2>Dynamic Reservation</h2>
 
-<p>As mentioned in <a href="#static-reservation-since-0140">Static Reservation</a>, specifying
+<p>As mentioned in <a href="#static-reservation">Static Reservation</a>, specifying
 the reserved resources via the <code>--resources</code> flag makes the reservation static.
 That is, statically reserved resources cannot be reserved for another role nor
 be unreserved. Dynamic reservation enables operators and authorized frameworks
@@ -181,6 +183,8 @@ same slave and use the same role.</p>
 
 <h3>Framework Scheduler API</h3>
 
+<p><a name="offer-operation-reserve"></a></p>
+
 <h4><code>Offer::Operation::Reserve</code></h4>
 
 <p>A framework can reserve resources through the resource offer cycle.  Suppose we
@@ -281,7 +285,7 @@ following reserved resources:</p>
 <h4><code>Offer::Operation::Unreserve</code></h4>
 
 <p>A framework can unreserve resources through the resource offer cycle.
-In <a href="#offeroperationreserve">Offer::Operation::Reserve</a>, we reserved 8 CPUs
+In <a href="#offer-operation-reserve">Offer::Operation::Reserve</a>, we reserved 8 CPUs
 and 4096 MB of RAM on a particular slave for our <code>role</code>. The master will
 continue to only offer these resources to our <code>role</code>. Suppose we would like to
 unreserve these resources. First, we receive a resource offer (copy/pasted

Modified: mesos/site/publish/documentation/scheduler-http-api/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/scheduler-http-api/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/scheduler-http-api/index.html (original)
+++ mesos/site/publish/documentation/scheduler-http-api/index.html Mon Jun 13 19:19:12 2016
@@ -98,12 +98,7 @@
 
 <h2>Overview</h2>
 
-<p>The scheduler interacts with Mesos via  &ldquo;/api/v1/scheduler&rdquo; endpoint hosted by the Mesos master. The fully qualified URL of the endpoint might look like:</p>
-
-<pre><code>http://masterhost:5050/api/v1/scheduler
-</code></pre>
-
-<p>Note that we refer to this endpoint with its suffix &ldquo;/scheduler&rdquo; in the rest of this document. This endpoint accepts HTTP POST requests with data encoded as JSON (Content-Type: application/json) or binary Protobuf (Content-Type: application/x-protobuf). The first request that a scheduler sends to &ldquo;/scheduler&rdquo; endpoint is called SUBSCRIBE and results in a streaming response (&ldquo;200 OK&rdquo; status code with Transfer-Encoding: chunked). <strong>Schedulers are expected to keep the subscription connection open as long as possible (barring errors in network, software, hardware etc.) and incrementally process the response</strong> (NOTE: HTTP client libraries that can only parse the response after the connection is closed cannot be used). For the encoding used, please refer to <strong>Events</strong> section below.</p>
+<p>The scheduler interacts with Mesos via the <a href="/documentation/latest/./endpoints/master/api/v1/scheduler/">/api/v1/scheduler</a> master endpoint. Note that we refer to this endpoint with its suffix &ldquo;/scheduler&rdquo; in the rest of this document. This endpoint accepts HTTP POST requests with data encoded as JSON (Content-Type: application/json) or binary Protobuf (Content-Type: application/x-protobuf). The first request that a scheduler sends to &ldquo;/scheduler&rdquo; endpoint is called SUBSCRIBE and results in a streaming response (&ldquo;200 OK&rdquo; status code with Transfer-Encoding: chunked). <strong>Schedulers are expected to keep the subscription connection open as long as possible (barring errors in network, software, hardware etc.) and incrementally process the response</strong> (NOTE: HTTP client libraries that can only parse the response after the connection is closed cannot be used). For the encoding used, please refer to <strong>Events</strong> section 
 below.</p>
 
 <p>All the subsequent (non-<code>SUBSCRIBE</code>) requests to &ldquo;/scheduler&rdquo; endpoint (see details below in <strong>Calls</strong> section) must be sent using a different connection(s) than the one being used for subscription. Master responds to these HTTP POST requests with &ldquo;202 Accepted&rdquo; status codes (or, for unsuccessful requests, with 4xx or 5xx status codes; details in later sections). The &ldquo;202 Accepted&rdquo; response means that a request has been accepted for processing, not that the processing of the request has been completed. The request might or might not be acted upon by Mesos (e.g., master fails during the processing of the request). Any asynchronous responses from these requests will be streamed on the long-lived subscription connection.</p>
 
@@ -458,7 +453,7 @@ HTTP/1.1 202 Accepted
 
 <p>Scheduler is expected to keep a <strong>persistent</strong> connection open to &ldquo;/scheduler&rdquo; endpoint even after getting a SUBSCRIBED HTTP Response event. This is indicated by &ldquo;Connection: keep-alive&rdquo; and &ldquo;Transfer-Encoding: chunked&rdquo; headers with <em>no</em> &ldquo;Content-Length&rdquo; header set. All subsequent events that are relevant to this framework  generated by Mesos are streamed on this connection. Master encodes each Event in RecordIO format, i.e., string representation of length of the event in bytes followed by JSON or binary Protobuf  (possibly compressed) encoded event. Note that the value of length will never be &lsquo;0&rsquo; and the size of the length will be the size of unsigned integer (i.e., 64 bits). Also, note that the RecordIO encoding should be decoded by the scheduler whereas the underlying HTTP chunked encoding is typically invisible at the application (scheduler) layer. The type of content encoding used for the events
  will be determined by the accept header of the POST request (e.g., Accept: application/json).</p>
 
-<p>The following events are currently sent by the master. The canonical source of this information is at <a href="include/mesos/v1/scheduler/scheduler.proto">scheduler.proto</a>. Note that when sending JSON encoded events, master encodes raw bytes in Base64 and strings in UTF-8.</p>
+<p>The following events are currently sent by the master. The canonical source of this information is at <a href="https://github.com/apache/mesos/blob/master/include/mesos/v1/scheduler/scheduler.proto">scheduler.proto</a>. Note that when sending JSON encoded events, master encodes raw bytes in Base64 and strings in UTF-8.</p>
 
 <h3>SUBSCRIBED</h3>
 
@@ -469,6 +464,7 @@ HTTP/1.1 202 Accepted
 <p>Sent by the master whenever there are new resources that can be offered to the framework. Each offer corresponds to a set of resources on an agent. Until the scheduler &lsquo;Accept&rsquo;s or 'Decline&rsquo;s an offer the resources are considered allocated to the scheduler, unless the offer is otherwise rescinded, e.g. due to a lost agent or <code>--offer_timeout</code>.</p>
 
 <pre><code>OFFERS Event (JSON)
+
 &lt;event-length&gt;
 {
   "type"    : "OFFERS",
@@ -491,6 +487,7 @@ HTTP/1.1 202 Accepted
 <p>Sent by the master when a particular offer is no longer valid (e.g., the agent corresponding to the offer has been removed) and hence needs to be rescinded. Any future calls (<code>ACCEPT</code> / <code>DECLINE</code>) made by the scheduler regarding this offer will be invalid.</p>
 
 <pre><code>RESCIND Event (JSON)
+
 &lt;event-length&gt;
 {
   "type"    : "RESCIND",
@@ -587,7 +584,7 @@ HTTP/1.1 202 Accepted
 
 <p>If master realizes that the subscription connection is broken, it marks the scheduler as &ldquo;disconnected&rdquo; and starts a failover timeout (failover timeout is part of FrameworkInfo). It also drops any pending events in its queue. Additionally, it rejects subsequent non-subscribe HTTP requests to &ldquo;/scheduler&rdquo; with &ldquo;403 Forbidden&rdquo;, until the scheduler subscribes again with &ldquo;/scheduler&rdquo;. If the scheduler <em>does not</em> re-subscribe within the failover timeout, the master considers the scheduler gone forever and shuts down all its executors, thus killing all its tasks. Therefore, all production schedulers are recommended to use a high value (e.g., 4 weeks) for the failover timeout.</p>
 
-<p>NOTE: To force shutdown of a framework before the failover timeout elapses (e.g., during framework development and testing), either the framework can send the <code>TEARDOWN</code> call (part of the Scheduler API) or an operator can use the &ldquo;/master/teardown&rdquo; endpoint (part of the Operator API).</p>
+<p>NOTE: To force shutdown of a framework before the failover timeout elapses (e.g., during framework development and testing), either the framework can send the <code>TEARDOWN</code> call (part of the Scheduler API) or an operator can use the <a href="/documentation/latest/./endpoints/master/teardown/">/teardown</a> master endpoint (part of the Operator API).</p>
 
 <p>If the scheduler realizes that its subscription connection to &ldquo;/scheduler&rdquo; is broken or the master has changed (e.g., via ZooKeeper), it should resubscribe (using a backoff strategy). This is done by sending a <code>SUBSCRIBE</code> request (with framework ID set) on a <strong>new</strong> persistent connection to the &ldquo;/scheduler&rdquo; endpoint on the (possibly new) master. It should not send new non-subscribe HTTP requests to &ldquo;/scheduler&rdquo; unless it receives a <code>SUBSCRIBED</code> event; such requests will result in &ldquo;403 Forbidden&rdquo;.</p>
 

Modified: mesos/site/publish/documentation/upgrades/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/upgrades/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/upgrades/index.html (original)
+++ mesos/site/publish/documentation/upgrades/index.html Mon Jun 13 19:19:12 2016
@@ -133,24 +133,37 @@ R Removed feature/behavior
   </thead>
 <tr>
   <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Version-->
-  0.29.x
+  1.0.x
   </td>
   <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Mesos Core-->
     <ul style="padding-left:10px;">
-      <li>CD <a href="#0-29-x-allocator-metrics">Allocator Metrics</a></li>
-      <li>D <a href="#0-29-x-credentials">--credential(s) (plain text format)</a></li>
+      <li>CD <a href="#1-0-x-allocator-metrics">Allocator Metrics</a></li>
+      <li>C <a href="#1-0-x-persistent-volume">Destruction of persistent volumes</a></li>
+      <li>C <a href="#1-0-x-slave">Slave to Agent rename</a></li>
+      <li>C <a href="#1-0-x-quota-acls">Quota ACLs</a></li>
     </ul>
   </td>
   <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Flags-->
     <ul style="padding-left:10px;">
-      <li>CD <a href="#0-29-x-quota-authorization">Quota Authorization</a></li>
+      <li>D <a href="#1-0-x-docker-timeout-flag">docker_stop_timeout</a></li>
+      <li>D <a href="#1-0-x-credentials-file">credential(s) (plain text format)</a></li>
+      <li>C <a href="#1-0-x-slave">Slave to Agent rename</a></li>
+      <li>R <a href="#1-0-x-workdir">work_dir default value</a></li>
     </ul>
   </td>
   <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Framework API-->
+      <li>DC <a href="#1-0-x-executorinfo">ExecutorInfo.source</a></li>
+      <li>N <a href="#1-0-x-v1-commandinfo">CommandInfo.URI output_file</a></li>
+      <li>C <a href="#1-0-x-scheduler-proto">scheduler.proto optional fields</a></li>
+      <li>C <a href="#1-0-x-executor-proto">executor.proto optional fields</a></li>
   </td>
   <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Module API-->
+    <li>C <a href="#1-0-x-authorizer">Authorizer</a></li>
   </td>
   <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Endpoints-->
+    <li>C <a href="#1-0-x-status-code">HTTP return codes</a></li>
+    <li>R <a href="#1-0-x-status-code">/observe</a></li>
+    <li>C <a href="#1-0-x-endpoint-authorization">Added authorization</a></li>
   </td>
 </tr>
 <tr>
@@ -249,10 +262,106 @@ R Removed feature/behavior
 
 <h2>Upgrading from 0.28.x to 1.0.x</h2>
 
+<p><a name="1-0-x-allocator-metrics"></a></p>
+
+<ul>
+<li>The allocator metric named <code>allocator/event_queue_dispatches</code> is now deprecated. The new name is <code>allocator/mesos/event_queue_dispatches</code> to better support metrics for alternative allocator implementations.</li>
+</ul>
+
+
+<p><a name="1-0-x-docker-timeout-flag"></a></p>
+
+<ul>
+<li>The &ndash;docker_stop_timeout agent flag is deprecated.</li>
+</ul>
+
+
+<p><a name="1-0-x-executorinfo"></a></p>
+
+<ul>
+<li>The ExecutorInfo.source field is deprecated in favor of ExecutorInfo.labels.</li>
+</ul>
+
+
+<p><a name="1-0-x-slave"></a></p>
+
+<p>Mesos 1.0 deprecates the &lsquo;slave&rsquo; keyword in favor of &lsquo;agent&rsquo; at number of places
+  * Deprecated flags with keyword &lsquo;slave&rsquo; in favor of &lsquo;agent&rsquo;.
+  * Deprecated sandbox links with &lsquo;slave&rsquo; keyword in the WebUI.
+  * Deprecated <code>slave</code> subcommand for mesos-cli.</p>
+
+<p><a name="1-0-x-workdir"></a></p>
+
+<p>Mesos 1.0 removes the default value for the agent <code>work_dir</code>. This flag is now required, and the agent will exit immediately if it is not provided.</p>
+
+<p><a name="1-0-x-credentials-file"></a></p>
+
+<ul>
+<li>Mesos 1.0 deprecates the use of plain text credential files in favor of JSON-formatted credential files.</li>
+</ul>
+
+
+<p><a name="1-0-x-persistent-volume"></a></p>
+
+<ul>
+<li>When a persistent volume is destroyed, Mesos will now remove any data that was stored on the volume from the filesystem of the appropriate slave. In prior versions of Mesos, destroying a volume would not delete data (this was a known missing feature that has now been implemented).</li>
+</ul>
+
+
+<p><a name="1-0-x-status-code"></a></p>
+
+<ul>
+<li>Mesos 1.0 changes the HTTP status code of the following endpoints from <code>200 OK</code> to <code>202 Accepted</code>:
+
+<ul>
+<li><code>/reserve</code></li>
+<li><code>/unreserve</code></li>
+<li><code>/create-volumes</code></li>
+<li><code>/destroy-volumes</code></li>
+</ul>
+</li>
+</ul>
+
+
+<p><a name="1-0-x-v1-commandinfo"></a></p>
+
 <ul>
-<li><p>The allocator metric named <code>allocator/event_queue_dispatches</code> is now deprecated. The new name is <code>allocator/mesos/event_queue_dispatches</code> to better support metrics for alternative allocator implementations.</p></li>
-<li><p>Mesos 1.0 deprecates the use of plain text credential files in favor of JSON-formatted credential files.</p></li>
-<li><p>Mesos 1.0 deprecates <code>SET_QUOTA_WITH_ROLE</code> and <code>DESTROY_QUOTA_WITH_PRINCIPAL</code> actions with <code>UPDATE_QUOTA_WITH_ROLE</code>, as well as the <code>SetQuota</code> and <code>RemoveQuota</code> ACLs with <code>UpdateQuota</code> ACL, to control which principal(s) is authorized to set, remove and (in future releases) update quota for role(s). A new <code>GET_QUOTA_WITH_ROLE</code> action and <code>get_quotas</code> ACL are introduced to control which principal(s) can query quota status for given role(s). This affects <code>--acls</code> flag for local authorizer in the following way:</p>
+<li>Added &lsquo;output_file&rsquo; field to CommandInfo.URI in Scheduler API and v1 Scheduler HTTP API.</li>
+</ul>
+
+
+<p><a name="1-0-x-scheduler-proto"></a></p>
+
+<ul>
+<li>Changed Call and Event Type enums in scheduler.proto from required to optional for the purpose of backwards compatibility.</li>
+</ul>
+
+
+<p><a name="1-0-x-executor-proto"></a></p>
+
+<ul>
+<li>Changed Call and Event Type enums in executor.proto from required to optional for the purpose of backwards compatibility.</li>
+</ul>
+
+
+<p><a name="1-0-x-nonterminal"></a></p>
+
+<ul>
+<li>Added non-terminal task metadata to the container resource usage information.</li>
+</ul>
+
+
+<p><a name="1-0-x-observe-endpoint"></a></p>
+
+<ul>
+<li>Deleted the /observe HTTP endpoint.</li>
+</ul>
+
+
+<p><a name="1-0-x-quota-acls"></a></p>
+
+<ul>
+<li>Mesos 1.0 deprecates <code>SET_QUOTA_WITH_ROLE</code> and <code>DESTROY_QUOTA_WITH_PRINCIPAL</code> actions with <code>UPDATE_QUOTA_WITH_ROLE</code>, as well as the <code>SetQuota</code> and <code>RemoveQuota</code> ACLs with <code>UpdateQuota</code> ACL, to control which principal(s) is authorized to set, remove and (in future releases) update quota for role(s). A new <code>GET_QUOTA_WITH_ROLE</code> action and <code>get_quotas</code> ACL are introduced to control which principal(s) can query quota status for given role(s). This affects <code>--acls</code> flag for local authorizer in the following way:
 
 <ul>
 <li>It is not allowed to specify <code>update_quotas</code> and any of <code>set_quotas</code> or <code>remove_quotas</code> at the same time. Local authorizor will error out in such case;</li>
@@ -261,19 +370,30 @@ R Removed feature/behavior
 <li>If desired, operator can use <code>get_quotas</code> after upgrade to control which principal(s) is allowed to query quota status for given role(s).</li>
 </ul>
 </li>
-<li><p>When a persistent volume is destroyed, Mesos will now remove any data that was stored on the volume from the filesystem of the appropriate slave. In prior versions of Mesos, destroying a volume would not delete data (this was a known missing feature that has now been implemented).</p></li>
-<li><p>Mesos 1.0 changes the HTTP status code of the following endpoints from <code>200 OK</code> to <code>202 Accepted</code>:</p>
+</ul>
+
+
+<p><a name="1-0-x-authorizer"></a></p>
 
 <ul>
-<li><code>/reserve</code></li>
-<li><code>/unreserve</code></li>
-<li><code>/create-volumes</code></li>
-<li><code>/destroy-volumes</code></li>
+<li>Mesos 1.0 contains a number of authorizer changes especially effecting authorizer modules:
+
+<ul>
+<li>The authorizer interface has been refactored in order to decouple the ACLs definition language from the interface. It additionally includes the option of retrieving <code>ObjectApprover</code>. An <code>ObjectApprover</code> can be used to synchronously check authorizations for a given object and is hence useful when authorizing a large number of objects and/or large objects (which need to be copied using request based authorization). NOTE: This is a <strong>breaking change</strong> for authorizer modules.</li>
+<li>Authorization based HTTP endpoint filtering enables operators to restrict what part of the cluster state a user is authorized to see. Consider for example the <code>/state</code> master endpoint: an operator can now authorize users to only see a subset of the running frameworks, tasks, or executors.</li>
+<li>Fields (i.e, <code>subject</code> and <code>object</code>) in authorization::Request protobuf are changed to optional. If these fields are not set, the request should be allowed only for ACLs with <code>ANY</code> semantics. NOTE: This is a semantic change for authorizer modules.</li>
 </ul>
 </li>
 </ul>
 
 
+<p><a name="1-0-x-endpoint-authorization"></a></p>
+
+<ul>
+<li>Mesos provides authorization a number of HTTP endpoints. Note that the some of these endpoints are used by the web UI, and thus using the web UI in a cluster with authorization enabled will require that ACLs be set appropriately. Please refer to the <a href="/documentation/latest/./authorization/">authorization documentation</a> for details.</li>
+</ul>
+
+
 <p>In order to upgrade a running cluster:</p>
 
 <ol>

Modified: mesos/site/publish/documentation/versioning/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/versioning/index.html?rev=1748304&r1=1748303&r2=1748304&view=diff
==============================================================================
--- mesos/site/publish/documentation/versioning/index.html (original)
+++ mesos/site/publish/documentation/versioning/index.html Mon Jun 13 19:19:12 2016
@@ -184,6 +184,8 @@
 </ul>
 
 
+<p><a name="api-compatibility"></a></p>
+
 <h3>API Compatibility</h3>
 
 <p>The API compatibility is determined by the corresponding protobuf guarantees.</p>



Mime
View raw message