Author: bmahler
Date: Mon Feb 8 16:43:52 2016
New Revision: 1729207
URL: http://svn.apache.org/viewvc?rev=1729207&view=rev
Log:
Added HTTP endpoint documentation.
Added:
mesos/site/publish/documentation/latest/endpoints/
mesos/site/publish/documentation/latest/endpoints/files/
mesos/site/publish/documentation/latest/endpoints/files/browse/
mesos/site/publish/documentation/latest/endpoints/files/browse.json/
mesos/site/publish/documentation/latest/endpoints/files/browse.json/index.html
mesos/site/publish/documentation/latest/endpoints/files/browse/index.html
mesos/site/publish/documentation/latest/endpoints/files/debug/
mesos/site/publish/documentation/latest/endpoints/files/debug.json/
mesos/site/publish/documentation/latest/endpoints/files/debug.json/index.html
mesos/site/publish/documentation/latest/endpoints/files/debug/index.html
mesos/site/publish/documentation/latest/endpoints/files/download/
mesos/site/publish/documentation/latest/endpoints/files/download.json/
mesos/site/publish/documentation/latest/endpoints/files/download.json/index.html
mesos/site/publish/documentation/latest/endpoints/files/download/index.html
mesos/site/publish/documentation/latest/endpoints/files/read/
mesos/site/publish/documentation/latest/endpoints/files/read.json/
mesos/site/publish/documentation/latest/endpoints/files/read.json/index.html
mesos/site/publish/documentation/latest/endpoints/files/read/index.html
mesos/site/publish/documentation/latest/endpoints/index.html
mesos/site/publish/documentation/latest/endpoints/logging/
mesos/site/publish/documentation/latest/endpoints/logging/toggle/
mesos/site/publish/documentation/latest/endpoints/logging/toggle/index.html
mesos/site/publish/documentation/latest/endpoints/master/
mesos/site/publish/documentation/latest/endpoints/master/api/
mesos/site/publish/documentation/latest/endpoints/master/api/v1/
mesos/site/publish/documentation/latest/endpoints/master/api/v1/scheduler/
mesos/site/publish/documentation/latest/endpoints/master/api/v1/scheduler/index.html
mesos/site/publish/documentation/latest/endpoints/master/create-volumes/
mesos/site/publish/documentation/latest/endpoints/master/create-volumes/index.html
mesos/site/publish/documentation/latest/endpoints/master/destroy-volumes/
mesos/site/publish/documentation/latest/endpoints/master/destroy-volumes/index.html
mesos/site/publish/documentation/latest/endpoints/master/flags/
mesos/site/publish/documentation/latest/endpoints/master/flags/index.html
mesos/site/publish/documentation/latest/endpoints/master/frameworks/
mesos/site/publish/documentation/latest/endpoints/master/frameworks/index.html
mesos/site/publish/documentation/latest/endpoints/master/health/
mesos/site/publish/documentation/latest/endpoints/master/health/index.html
mesos/site/publish/documentation/latest/endpoints/master/machine/
mesos/site/publish/documentation/latest/endpoints/master/machine/down/
mesos/site/publish/documentation/latest/endpoints/master/machine/down/index.html
mesos/site/publish/documentation/latest/endpoints/master/machine/up/
mesos/site/publish/documentation/latest/endpoints/master/machine/up/index.html
mesos/site/publish/documentation/latest/endpoints/master/maintenance/
mesos/site/publish/documentation/latest/endpoints/master/maintenance/schedule/
mesos/site/publish/documentation/latest/endpoints/master/maintenance/schedule/index.html
mesos/site/publish/documentation/latest/endpoints/master/maintenance/status/
mesos/site/publish/documentation/latest/endpoints/master/maintenance/status/index.html
mesos/site/publish/documentation/latest/endpoints/master/observe/
mesos/site/publish/documentation/latest/endpoints/master/observe/index.html
mesos/site/publish/documentation/latest/endpoints/master/quota/
mesos/site/publish/documentation/latest/endpoints/master/quota/index.html
mesos/site/publish/documentation/latest/endpoints/master/redirect/
mesos/site/publish/documentation/latest/endpoints/master/redirect/index.html
mesos/site/publish/documentation/latest/endpoints/master/reserve/
mesos/site/publish/documentation/latest/endpoints/master/reserve/index.html
mesos/site/publish/documentation/latest/endpoints/master/roles/
mesos/site/publish/documentation/latest/endpoints/master/roles.json/
mesos/site/publish/documentation/latest/endpoints/master/roles.json/index.html
mesos/site/publish/documentation/latest/endpoints/master/roles/index.html
mesos/site/publish/documentation/latest/endpoints/master/slaves/
mesos/site/publish/documentation/latest/endpoints/master/slaves/index.html
mesos/site/publish/documentation/latest/endpoints/master/state/
mesos/site/publish/documentation/latest/endpoints/master/state-summary/
mesos/site/publish/documentation/latest/endpoints/master/state-summary/index.html
mesos/site/publish/documentation/latest/endpoints/master/state.json/
mesos/site/publish/documentation/latest/endpoints/master/state.json/index.html
mesos/site/publish/documentation/latest/endpoints/master/state/index.html
mesos/site/publish/documentation/latest/endpoints/master/tasks/
mesos/site/publish/documentation/latest/endpoints/master/tasks.json/
mesos/site/publish/documentation/latest/endpoints/master/tasks.json/index.html
mesos/site/publish/documentation/latest/endpoints/master/tasks/index.html
mesos/site/publish/documentation/latest/endpoints/master/teardown/
mesos/site/publish/documentation/latest/endpoints/master/teardown/index.html
mesos/site/publish/documentation/latest/endpoints/master/unreserve/
mesos/site/publish/documentation/latest/endpoints/master/unreserve/index.html
mesos/site/publish/documentation/latest/endpoints/metrics/
mesos/site/publish/documentation/latest/endpoints/metrics/snapshot/
mesos/site/publish/documentation/latest/endpoints/metrics/snapshot/index.html
mesos/site/publish/documentation/latest/endpoints/monitor/
mesos/site/publish/documentation/latest/endpoints/monitor/statistics/
mesos/site/publish/documentation/latest/endpoints/monitor/statistics.json/
mesos/site/publish/documentation/latest/endpoints/monitor/statistics.json/index.html
mesos/site/publish/documentation/latest/endpoints/monitor/statistics/index.html
mesos/site/publish/documentation/latest/endpoints/profiler/
mesos/site/publish/documentation/latest/endpoints/profiler/start/
mesos/site/publish/documentation/latest/endpoints/profiler/start/index.html
mesos/site/publish/documentation/latest/endpoints/profiler/stop/
mesos/site/publish/documentation/latest/endpoints/profiler/stop/index.html
mesos/site/publish/documentation/latest/endpoints/registrar/
mesos/site/publish/documentation/latest/endpoints/registrar/registry/
mesos/site/publish/documentation/latest/endpoints/registrar/registry/index.html
mesos/site/publish/documentation/latest/endpoints/slave/
mesos/site/publish/documentation/latest/endpoints/slave/api/
mesos/site/publish/documentation/latest/endpoints/slave/api/v1/
mesos/site/publish/documentation/latest/endpoints/slave/api/v1/executor/
mesos/site/publish/documentation/latest/endpoints/slave/api/v1/executor/index.html
mesos/site/publish/documentation/latest/endpoints/slave/flags/
mesos/site/publish/documentation/latest/endpoints/slave/flags/index.html
mesos/site/publish/documentation/latest/endpoints/slave/health/
mesos/site/publish/documentation/latest/endpoints/slave/health/index.html
mesos/site/publish/documentation/latest/endpoints/slave/state/
mesos/site/publish/documentation/latest/endpoints/slave/state.json/
mesos/site/publish/documentation/latest/endpoints/slave/state.json/index.html
mesos/site/publish/documentation/latest/endpoints/slave/state/index.html
mesos/site/publish/documentation/latest/endpoints/system/
mesos/site/publish/documentation/latest/endpoints/system/stats.json/
mesos/site/publish/documentation/latest/endpoints/system/stats.json/index.html
mesos/site/publish/documentation/latest/endpoints/version/
mesos/site/publish/documentation/latest/endpoints/version/index.html
Modified:
mesos/site/publish/community/user-groups/index.html
mesos/site/publish/documentation/allocation-module/index.html
mesos/site/publish/documentation/app-framework-development-guide/index.html
mesos/site/publish/documentation/architecture/index.html
mesos/site/publish/documentation/attributes-resources/index.html
mesos/site/publish/documentation/authentication/index.html
mesos/site/publish/documentation/authorization/index.html
mesos/site/publish/documentation/c++-style-guide/index.html
mesos/site/publish/documentation/clang-format/index.html
mesos/site/publish/documentation/committers/index.html
mesos/site/publish/documentation/configuration/index.html
mesos/site/publish/documentation/containerizer-internals/index.html
mesos/site/publish/documentation/containerizer/index.html
mesos/site/publish/documentation/deploy-scripts/index.html
mesos/site/publish/documentation/documentation-guide/index.html
mesos/site/publish/documentation/effective-code-reviewing/index.html
mesos/site/publish/documentation/executor-http-api/index.html
mesos/site/publish/documentation/fetcher-cache-internals/index.html
mesos/site/publish/documentation/fetcher/index.html
mesos/site/publish/documentation/high-availability-framework-guide/index.html
mesos/site/publish/documentation/high-availability/index.html
mesos/site/publish/documentation/index.html
mesos/site/publish/documentation/latest/allocation-module/index.html
mesos/site/publish/documentation/latest/app-framework-development-guide/index.html
mesos/site/publish/documentation/latest/architecture/index.html
mesos/site/publish/documentation/latest/attributes-resources/index.html
mesos/site/publish/documentation/latest/authentication/index.html
mesos/site/publish/documentation/latest/authorization/index.html
mesos/site/publish/documentation/latest/c++-style-guide/index.html
mesos/site/publish/documentation/latest/clang-format/index.html
mesos/site/publish/documentation/latest/committers/index.html
mesos/site/publish/documentation/latest/configuration/index.html
mesos/site/publish/documentation/latest/containerizer-internals/index.html
mesos/site/publish/documentation/latest/containerizer/index.html
mesos/site/publish/documentation/latest/deploy-scripts/index.html
mesos/site/publish/documentation/latest/documentation-guide/index.html
mesos/site/publish/documentation/latest/effective-code-reviewing/index.html
mesos/site/publish/documentation/latest/executor-http-api/index.html
mesos/site/publish/documentation/latest/fetcher-cache-internals/index.html
mesos/site/publish/documentation/latest/fetcher/index.html
mesos/site/publish/documentation/latest/high-availability-framework-guide/index.html
mesos/site/publish/documentation/latest/high-availability/index.html
mesos/site/publish/documentation/latest/index.html
mesos/site/publish/documentation/latest/logging/index.html
mesos/site/publish/documentation/latest/mesos-provisioner/index.html
mesos/site/publish/documentation/latest/networking-for-mesos-managed-containers/index.html
mesos/site/publish/documentation/latest/newbie-guide/index.html
mesos/site/publish/documentation/latest/operational-guide/index.html
mesos/site/publish/documentation/latest/oversubscription/index.html
mesos/site/publish/documentation/latest/persistent-volume/index.html
mesos/site/publish/documentation/latest/powered-by-mesos/index.html
mesos/site/publish/documentation/latest/quota/index.html
mesos/site/publish/documentation/latest/release-guide/index.html
mesos/site/publish/documentation/latest/reporting-a-bug/index.html
mesos/site/publish/documentation/latest/reservation/index.html
mesos/site/publish/documentation/latest/roles/index.html
mesos/site/publish/documentation/latest/sandbox/index.html
mesos/site/publish/documentation/latest/scheduler-http-api/index.html
mesos/site/publish/documentation/latest/slave-recovery/index.html
mesos/site/publish/documentation/latest/submitting-a-patch/index.html
mesos/site/publish/documentation/latest/tools/index.html
mesos/site/publish/documentation/latest/upgrades/index.html
mesos/site/publish/documentation/latest/versioning/index.html
mesos/site/publish/documentation/logging/index.html
mesos/site/publish/documentation/mesos-provisioner/index.html
mesos/site/publish/documentation/networking-for-mesos-managed-containers/index.html
mesos/site/publish/documentation/newbie-guide/index.html
mesos/site/publish/documentation/operational-guide/index.html
mesos/site/publish/documentation/oversubscription/index.html
mesos/site/publish/documentation/persistent-volume/index.html
mesos/site/publish/documentation/powered-by-mesos/index.html
mesos/site/publish/documentation/quota/index.html
mesos/site/publish/documentation/release-guide/index.html
mesos/site/publish/documentation/reporting-a-bug/index.html
mesos/site/publish/documentation/reservation/index.html
mesos/site/publish/documentation/roles/index.html
mesos/site/publish/documentation/sandbox/index.html
mesos/site/publish/documentation/scheduler-http-api/index.html
mesos/site/publish/documentation/slave-recovery/index.html
mesos/site/publish/documentation/submitting-a-patch/index.html
mesos/site/publish/documentation/tools/index.html
mesos/site/publish/documentation/upgrades/index.html
mesos/site/publish/documentation/versioning/index.html
mesos/site/publish/sitemap.xml
Modified: mesos/site/publish/community/user-groups/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/community/user-groups/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/community/user-groups/index.html (original)
+++ mesos/site/publish/community/user-groups/index.html Mon Feb 8 16:43:52 2016
@@ -108,6 +108,13 @@
</ul>
+<h3>India</h3>
+
+<ul>
+<li><a href="http://www.meetup.com/Pune-Mesos-Users-Group/";>Pune</a></li>
+</ul>
+
+
<h3>Poland</h3>
<ul>
Modified: mesos/site/publish/documentation/allocation-module/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/allocation-module/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/allocation-module/index.html (original)
+++ mesos/site/publish/documentation/allocation-module/index.html Mon Feb 8
16:43:52 2016
@@ -146,7 +146,7 @@ mesos::modules::Module<Allocator>
createExternalAllocator);
</code></pre>
-<p>Refer to the <a href="/documentation/latest/modules/">Mesos Modules
documentation</a> for instructions on how to compile and load a module in Mesos
master.</p>
+<p>Refer to the <a href="/documentation/latest/./modules/">Mesos Modules
documentation</a> for instructions on how to compile and load a module in Mesos
master.</p>
</div>
</div>
Modified:
mesos/site/publish/documentation/app-framework-development-guide/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/app-framework-development-guide/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/app-framework-development-guide/index.html
(original)
+++ mesos/site/publish/documentation/app-framework-development-guide/index.html
Mon Feb 8 16:43:52 2016
@@ -210,7 +210,7 @@ virtual void error(SchedulerDriver* driv
<h3>Handling Failures</h3>
-<p>How to build Mesos frameworks that remain available in the face of failures
is discussed in a <a
href="/documentation/latest/high-availability-framework-guide/">separate
document</a>.</p>
+<p>How to build Mesos frameworks that remain available in the face of failures
is discussed in a <a
href="/documentation/latest/./high-availability-framework-guide/">separate
document</a>.</p>
<h2>Working with Executors</h2>
@@ -310,7 +310,7 @@ virtual void error(ExecutorDriver* drive
<p>After creating your custom executor, you need to make it available to all
slaves in the cluster.</p>
-<p>One way to distribute your framework executor is to let the <a
href="/documentation/latest/fetcher/">Mesos fetcher</a> download it on-demand
when your scheduler launches tasks on that slave. <code>ExecutorInfo</code> is
a Protocol Buffer Message class (defined in
<code>include/mesos/mesos.proto</code>), and it contains a field of type
<code>CommandInfo</code>. <code>CommandInfo</code> allows schedulers to
specify, among other things, a number of resources as URIs. These resources are
fetched to a sandbox directory on the slave before attempting to execute the
<code>ExecutorInfo</code> command. Several URI schemes are supported, including
HTTP, FTP, HDFS, and S3 (e.g. see src/examples/java/TestFramework.java for an
example of this).</p>
+<p>One way to distribute your framework executor is to let the <a
href="/documentation/latest/./fetcher/">Mesos fetcher</a> download it on-demand
when your scheduler launches tasks on that slave. <code>ExecutorInfo</code> is
a Protocol Buffer Message class (defined in
<code>include/mesos/mesos.proto</code>), and it contains a field of type
<code>CommandInfo</code>. <code>CommandInfo</code> allows schedulers to
specify, among other things, a number of resources as URIs. These resources are
fetched to a sandbox directory on the slave before attempting to execute the
<code>ExecutorInfo</code> command. Several URI schemes are supported, including
HTTP, FTP, HDFS, and S3 (e.g. see src/examples/java/TestFramework.java for an
example of this).</p>
<p>Alternatively, you can pass the <code>frameworks_home</code> configuration
option (defaults to: <code>MESOS_HOME/frameworks</code>) to your
<code>mesos-slave</code> daemons when you launch them to specify where your
framework executors are stored (e.g. on an NFS mount that is available to all
slaves), then use a relative path in <code>CommandInfo.uris</code>, and the
slave will prepend the value of <code>frameworks_home</code> to the relative
path provided.</p>
Modified: mesos/site/publish/documentation/architecture/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/architecture/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/architecture/index.html (original)
+++ mesos/site/publish/documentation/architecture/index.html Mon Feb 8
16:43:52 2016
@@ -89,7 +89,7 @@
<p>The master enables fine-grained sharing of resources (CPU, RAM, …)
across frameworks by making them <em>resource offers</em>. Each resource offer
contains a list of <slave ID, resource1: amount1, resource2, amount2,
…>. The master decides <em>how many</em> resources to offer to each
framework according to a given organizational policy, such as fair sharing or
strict priority. To support a diverse set of policies, the master employs a
modular architecture that makes it easy to add new allocation modules via a
plugin mechanism.</p>
-<p>A framework running on top of Mesos consists of two components: a
<em>scheduler</em> that registers with the master to be offered resources, and
an <em>executor</em> process that is launched on slave nodes to run the
framework’s tasks (see the <a
href="/documentation/latest/app-framework-development-guide/">App/Framework
development guide</a> for more details about framework schedulers and
executors). While the master determines <strong>how many</strong> resources are
offered to each framework, the frameworks' schedulers select
<strong>which</strong> of the offered resources to use. When a frameworks
accepts offered resources, it passes to Mesos a description of the tasks it
wants to run on them. In turn, Mesos launches the tasks on the corresponding
slaves.</p>
+<p>A framework running on top of Mesos consists of two components: a
<em>scheduler</em> that registers with the master to be offered resources, and
an <em>executor</em> process that is launched on slave nodes to run the
framework’s tasks (see the <a
href="/documentation/latest/./app-framework-development-guide/">App/Framework
development guide</a> for more details about framework schedulers and
executors). While the master determines <strong>how many</strong> resources are
offered to each framework, the frameworks' schedulers select
<strong>which</strong> of the offered resources to use. When a frameworks
accepts offered resources, it passes to Mesos a description of the tasks it
wants to run on them. In turn, Mesos launches the tasks on the corresponding
slaves.</p>
<h2>Example of resource offer</h2>
Modified: mesos/site/publish/documentation/attributes-resources/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/attributes-resources/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/attributes-resources/index.html (original)
+++ mesos/site/publish/documentation/attributes-resources/index.html Mon Feb 8
16:43:52 2016
@@ -168,31 +168,33 @@ key : text ( "(" resourceRole ")" )?
resourceRole : text | "*"
</code></pre>
-<p>Note that <code>resourceRole</code> must be a valid role name; see the <a
href="/documentation/latest/roles/">roles</a> documentation for details.</p>
+<p>Note that <code>resourceRole</code> must be a valid role name; see the <a
href="/documentation/latest/./roles/">roles</a> documentation for details.</p>
<h2>Predefined Uses & Conventions</h2>
-<p>The Mesos master has a few resources that it pre-defines in how it handles
them. At the current time, this list consist of:</p>
+<p>There are several kinds of resources that have predefined behavior:</p>
<ul>
<li><code>cpus</code></li>
-<li><code>mem</code></li>
<li><code>disk</code></li>
+<li><code>mem</code></li>
<li><code>ports</code></li>
</ul>
-<p>In particular, a slave without <code>cpus</code> and <code>mem</code>
resources will never have its resources advertised to any frameworks. Also,
the Master’s user interface interprets the scalars in <code>mem</code>
and <code>disk</code> in terms of <em><code>MB</code></em>. IE: the value
<code>15000</code> is displayed as <code>14.65GB</code>.</p>
+<p>Note that <code>disk</code> and <code>mem</code> resources are specified in
megabytes. The master’s user interface will convert resource values into
a more human-readable format: for example, the value <code>15000</code> will be
displayed as <code>14.65GB</code>.</p>
+
+<p>A slave without <code>cpus</code> and <code>mem</code> resources will not
have its resources advertised to any frameworks.</p>
<h2>Examples</h2>
-<p>Here are some examples for configuring the Mesos slaves.</p>
+<p>By default, Mesos will try to autodetect the resources available at the
local machine when <code>mesos-slave</code> starts up. Alternatively, you can
explicitly configure which resources a slave should make available.</p>
+
+<p>Here are some examples of how to configure the resources at a Mesos
slave:</p>
<pre><code>--resources='cpus:24;mem:24576;disk:409600;ports:[21000-24000,30000-34000];bugs(debug_role):{a,b,c}'
--resources='[{"name":"cpus","type":"SCALAR","scalar":{"value":24}},{"name":"mem","type":"SCALAR","scalar":{"value":24576}},{"name":"disk","type":"SCALAR","scalar":{"value":409600}},{"name":"ports","type":"RANGES","ranges":{"range":[{"begin":21000,"end":24000},{"begin":30000,"end":34000}]}},{"name":"bugs","type":"SET","set":{"item":["a","b","c"]},"role":"debug_role"}]'
-
---attributes='rack:abc;zone:west;os:centos5;level:10;keys:[1000-1500]'
</code></pre>
<p>Or given a file <code>resources.txt</code> containing the following:</p>
@@ -268,7 +270,12 @@ resourceRole : text | "*"
</ul>
-<p>In the case of attributes, we end up with five attributes:</p>
+<p>To configure the attributes of a Mesos slave, you can use the
<code>--attributes</code> command-line flag of <code>mesos-slave</code>:</p>
+
+<pre><code>--attributes='rack:abc;zone:west;os:centos5;level:10;keys:[1000-1500]'
+</code></pre>
+
+<p>That will result in configuring the following five attributes:</p>
<ul>
<li><code>rack</code> with text value <code>abc</code></li>
Modified: mesos/site/publish/documentation/authentication/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/authentication/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/authentication/index.html (original)
+++ mesos/site/publish/documentation/authentication/index.html Mon Feb 8
16:43:52 2016
@@ -100,7 +100,7 @@
<h2>Configuration</h2>
-<p>The <a href="/documentation/latest/configuration/">configuration
options</a> that are used by the authentication mechanism are as follows:</p>
+<p>The <a href="/documentation/latest/./configuration/">configuration
options</a> that are used by the authentication mechanism are as follows:</p>
<h3>Masters</h3>
Modified: mesos/site/publish/documentation/authorization/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/authorization/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/authorization/index.html (original)
+++ mesos/site/publish/documentation/authorization/index.html Mon Feb 8
16:43:52 2016
@@ -132,7 +132,7 @@
<p>The currently supported <code>Objects</code> are:</p>
<ol>
-<li>“roles”: Resource <a
href="/documentation/latest/roles/">roles</a> that framework can register with
(used by “register_frameworks” and “set_quotas”
actions)</li>
+<li>“roles”: Resource <a
href="/documentation/latest/./roles/">roles</a> that framework can register
with (used by “register_frameworks” and “set_quotas”
actions)</li>
<li>“users”: Unix user to launch the task/executor as (used by
“run_tasks” actions)</li>
<li>“framework_principals”: Framework principals that can be torn
down by HTTP POST (used by “teardown_frameworks” actions).</li>
<li>“resources”: Resources that can be reserved. Currently the
only types considered by the default authorizer are <code>ANY</code> and
<code>NONE</code> (used by “reserves” action).</li>
@@ -303,7 +303,7 @@
<p>For more information on master command-line flags, see the
-<a href="/documentation/latest/configuration/">configuration</a> page.</p>
+<a href="/documentation/latest/./configuration/">configuration</a> page.</p>
</div>
</div>
Modified: mesos/site/publish/documentation/c++-style-guide/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/c%2B%2B-style-guide/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/c++-style-guide/index.html (original)
+++ mesos/site/publish/documentation/c++-style-guide/index.html Mon Feb 8
16:43:52 2016
@@ -83,7 +83,7 @@
<div class="col-md-8">
<h1>Mesos C++ Style Guide</h1>
-<p>The Mesos codebase follows the <a
href="http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml";>Google
C++ Style Guide</a> with some notable differences, as described below. Note
that the <a href="/documentation/latest/clang-format/">clang-format</a> tool
can be helpful to ensure that some of the mechanical style rules are obeyed.</p>
+<p>The Mesos codebase follows the <a
href="http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml";>Google
C++ Style Guide</a> with some notable differences, as described below. Note
that the <a href="/documentation/latest/./clang-format/">clang-format</a> tool
can be helpful to ensure that some of the mechanical style rules are obeyed.</p>
<h2>Scoping</h2>
Modified: mesos/site/publish/documentation/clang-format/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/clang-format/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/clang-format/index.html (original)
+++ mesos/site/publish/documentation/clang-format/index.html Mon Feb 8
16:43:52 2016
@@ -85,7 +85,7 @@
<p><a
href="http://llvm.org/releases/3.5.1/tools/clang/docs/ClangFormat.html";>ClangFormat</a>
is an automatic source code formatting tool which helps us focus on the code
rather than the formatting.</p>
-<blockquote><p>The provided configurations try to honor the <a
href="/documentation/latest/c++-style-guide/">Mesos C++ Style Guide</a> as much
as possible, but there are some limitations which require manual attention.
Even with these limitations however, ClangFormat will be extremely useful for
your workflow!</p></blockquote>
+<blockquote><p>The provided configurations try to honor the <a
href="/documentation/latest/./c++-style-guide/">Mesos C++ Style Guide</a> as
much as possible, but there are some limitations which require manual
attention. Even with these limitations however, ClangFormat will be extremely
useful for your workflow!</p></blockquote>
<h2>Setup</h2>
Modified: mesos/site/publish/documentation/committers/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/committers/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/committers/index.html (original)
+++ mesos/site/publish/documentation/committers/index.html Mon Feb 8 16:43:52
2016
@@ -87,7 +87,7 @@
<h2>Becoming a committer</h2>
-<p>Every new committer has to be proposed by a current committer and then
voted in by the members of the Mesos PMC. For details about this process and
for candidate requirements see the general <a
href="https://community.apache.org/newcommitter.html";>Apache guidelines for
assessing new candidates for committership</a>. Candidates prepare for their
nomination as committer by contributing to the Mesos project and its community,
by acting according to the <a href="http://theapacheway.com";>Apache Way</a>,
and by generally following the path <a
href="https://community.apache.org/contributors/";>from contributor to
committer</a> for Apache projects. Specifically for the Mesos project, you can
make use of the <a
href="/documentation/latest/committer-candidate-checklist/">Apache Mesos
Committer Candidate Checklist</a> for suggestions of what kind of contributions
and demonstrated behaviors can be instrumental, and to keep track of your
progress.</p>
+<p>Every new committer has to be proposed by a current committer and then
voted in by the members of the Mesos PMC. For details about this process and
for candidate requirements see the general <a
href="https://community.apache.org/newcommitter.html";>Apache guidelines for
assessing new candidates for committership</a>. Candidates prepare for their
nomination as committer by contributing to the Mesos project and its community,
by acting according to the <a href="http://theapacheway.com";>Apache Way</a>,
and by generally following the path <a
href="https://community.apache.org/contributors/";>from contributor to
committer</a> for Apache projects. Specifically for the Mesos project, you can
make use of the <a
href="/documentation/latest/./committer-candidate-checklist/">Apache Mesos
Committer Candidate Checklist</a> for suggestions of what kind of contributions
and demonstrated behaviors can be instrumental, and to keep track of your
progress.</p>
<h2>Current Committers</h2>
Modified: mesos/site/publish/documentation/configuration/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/configuration/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/configuration/index.html (original)
+++ mesos/site/publish/documentation/configuration/index.html Mon Feb 8
16:43:52 2016
@@ -294,7 +294,7 @@ Example:
<p><em>These logging options can also be supplied to both masters and
slaves.</em>
-For more about logging, see the <a
href="/documentation/latest/logging/">logging documentation</a>.</p>
+For more about logging, see the <a
href="/documentation/latest/./logging/">logging documentation</a>.</p>
<table class="table table-striped">
<thead>
Modified: mesos/site/publish/documentation/containerizer-internals/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/containerizer-internals/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/containerizer-internals/index.html
(original)
+++ mesos/site/publish/documentation/containerizer-internals/index.html Mon Feb
8 16:43:52 2016
@@ -112,9 +112,9 @@ generating executor information.</li>
<ul>
<li>Composing</li>
-<li><a href="/documentation/latest/docker-containerizer/">Docker</a></li>
-<li><a href="/documentation/latest/containerizer/">Mesos</a></li>
-<li><a href="/documentation/latest/external-containerizer/">External</a>
(deprecated)</li>
+<li><a href="/documentation/latest/./docker-containerizer/">Docker</a></li>
+<li><a href="/documentation/latest/./containerizer/">Mesos</a></li>
+<li><a href="/documentation/latest/./external-containerizer/">External</a>
(deprecated)</li>
</ul>
Modified: mesos/site/publish/documentation/containerizer/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/containerizer/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/containerizer/index.html (original)
+++ mesos/site/publish/documentation/containerizer/index.html Mon Feb 8
16:43:52 2016
@@ -154,7 +154,7 @@ containerizer is enabled when you config
<p>For more details, see
-<a href="/documentation/latest/docker-containerizer/">Docker
Containerizer</a>.</p>
+<a href="/documentation/latest/./docker-containerizer/">Docker
Containerizer</a>.</p>
<p><a name="Mesos"></a></p>
@@ -179,12 +179,12 @@ might not be provided by other container
<p>For more details, see
-<a href="/documentation/latest/mesos-containerizer/">Mesos
Containerizer</a>.</p>
+<a href="/documentation/latest/./mesos-containerizer/">Mesos
Containerizer</a>.</p>
<h2>References</h2>
<ul>
-<li><a href="/documentation/latest/containerizer-internals/">Containerizer
Internals</a> for
+<li><a href="/documentation/latest/./containerizer-internals/">Containerizer
Internals</a> for
implementation details of containerizers.</li>
</ul>
Modified: mesos/site/publish/documentation/deploy-scripts/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/deploy-scripts/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/deploy-scripts/index.html (original)
+++ mesos/site/publish/documentation/deploy-scripts/index.html Mon Feb 8
16:43:52 2016
@@ -95,7 +95,7 @@
<p>It is also possible to set environment variables, ulimits, etc that will
affect the master and slave by editing
<code>[install-prefix]/var/mesos/deploy/mesos-deploy-env.sh</code>. One
particularly useful setting is <code>LIBPROCESS_IP</code>, which tells the
master and slave binaries which IP address to bind to; in some installations,
the default interface that the hostname resolves to is not the machine’s
external IP address, so you can set the right IP through this variable. Besides
the common environment variables of master and slave configured in
<code>[install-prefix/var/mesos/deploy/mesos-deploy-env.sh</code>, it is also
possible to set master specific environment variables in
<code>[install-prefix]/var/mesos/deploy/mesos-master-env.sh</code>, slave
specific environment variables in
<code>[install-prefix]/var/mesos/deploy/mesos-slave-env.sh</code>.</p>
-<p>Finally, the deploy scripts do not use ZooKeeper by default. If you want to
configure Mesos to use ZooKeeper to coordinate multiple master nodes, please
see the <a href="/documentation/latest/high-availability/">High
Availability</a> documentation for details.</p>
+<p>Finally, the deploy scripts do not use ZooKeeper by default. If you want to
configure Mesos to use ZooKeeper to coordinate multiple master nodes, please
see the <a href="/documentation/latest/./high-availability/">High
Availability</a> documentation for details.</p>
<h2>Notes</h2>
Modified: mesos/site/publish/documentation/documentation-guide/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/documentation-guide/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/documentation-guide/index.html (original)
+++ mesos/site/publish/documentation/documentation-guide/index.html Mon Feb 8
16:43:52 2016
@@ -88,7 +88,7 @@
<p>We have three different kinds of documentation:</p>
<ol>
-<li><a href="/documentation/latest/markdown-style-guide/">MarkDown User
Guides</a></li>
+<li><a href="/documentation/latest/./markdown-style-guide/">MarkDown User
Guides</a></li>
</ol>
@@ -97,7 +97,7 @@
<p> We will accept small documentation changes on <a
href="https://github.com/apache/mesos";>Github via a pull request</a>, larger
documentation changes should go through the
(reviewboard)[https://reviews.apache.org/groups/mesos/]</p>
<ol>
-<li><a href="/documentation/latest/doxygen-style-guide/">Doxygen API
Documentation and Developer Guides as part of source code</a></li>
+<li><a href="/documentation/latest/./doxygen-style-guide/">Doxygen API
Documentation and Developer Guides as part of source code</a></li>
</ol>
Modified: mesos/site/publish/documentation/effective-code-reviewing/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/effective-code-reviewing/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/effective-code-reviewing/index.html
(original)
+++ mesos/site/publish/documentation/effective-code-reviewing/index.html Mon
Feb 8 16:43:52 2016
@@ -102,7 +102,7 @@ reviews based on commits. Become familia
change clear in the review request, so the reviewer is not left
guessing. It is highly recommended to attach a JIRA issue with your
review for additional context.</li>
-<li><strong>Follow the <a href="/documentation/latest/c++-style-guide/">style
guide</a>
+<li><strong>Follow the <a
href="/documentation/latest/./c++-style-guide/">style guide</a>
and the style of code around you</strong>.</li>
<li><strong>Do a self-review of your changes before publishing</strong>:
Approach it
from the perspective of a reviewer with no context. Is it easy to figure
Modified: mesos/site/publish/documentation/executor-http-api/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/executor-http-api/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/executor-http-api/index.html (original)
+++ mesos/site/publish/documentation/executor-http-api/index.html Mon Feb 8
16:43:52 2016
@@ -104,7 +104,7 @@
<p>This is the first step in the communication process between the executor
and agent. This is also to be considered as subscription to the
“/executor” events stream.</p>
-<p>To subscribe with the agent, the executor sends a HTTP POST request with
encoded <code>SUBSCRIBE</code> message. The HTTP response is a stream with <a
href="/documentation/latest/scheduler-http-api/#recordio-response-format">RecordIO</a>
encoding, with the first event being <code>SUBSCRIBED</code> event (see
details in <strong>Events</strong> section).</p>
+<p>To subscribe with the agent, the executor sends a HTTP POST request with
encoded <code>SUBSCRIBE</code> message. The HTTP response is a stream with <a
href="/documentation/latest/./scheduler-http-api/#recordio-response-format">RecordIO</a>
encoding, with the first event being <code>SUBSCRIBED</code> event (see
details in <strong>Events</strong> section).</p>
<p>Additionally, if the executor is connecting to the agent after a <a
href="#disconnections">disconnection</a>, it can also send a list of:</p>
@@ -276,7 +276,7 @@ HTTP/1.1 202 Accepted
<h2>Events</h2>
-<p>Executor is expected to keep a <strong>persistent</strong> connection open
to “/executor” endpoint even after getting a
<code>SUBSCRIBED</code> HTTP Response event. This is indicated by
“Connection: keep-alive” and “Transfer-Encoding:
chunked” headers with <em>no</em> “Content-Length” 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 typical
ly 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., “Accept: application/json”).</p>
+<p>Executor is expected to keep a <strong>persistent</strong> connection open
to “/executor” endpoint even after getting a
<code>SUBSCRIBED</code> HTTP Response event. This is indicated by
“Connection: keep-alive” and “Transfer-Encoding:
chunked” headers with <em>no</em> “Content-Length” 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., “Accept: application/json”).</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>
@@ -429,7 +429,7 @@ HTTP/1.1 202 Accepted
<h2>Agent Recovery</h2>
-<p>Upon agent startup, an agent performs <a
href="/documentation/latest/slave-recovery/">recovery</a>. This allows the
agent to recover status updates and reconnect with old executors. Currently,
the agent supports the following recovery mechanisms specified via the
<code>--recover</code> flag:</p>
+<p>Upon agent startup, an agent performs <a
href="/documentation/latest/./slave-recovery/">recovery</a>. This allows the
agent to recover status updates and reconnect with old executors. Currently,
the agent supports the following recovery mechanisms specified via the
<code>--recover</code> flag:</p>
<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>
Modified: mesos/site/publish/documentation/fetcher-cache-internals/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/fetcher-cache-internals/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/fetcher-cache-internals/index.html
(original)
+++ mesos/site/publish/documentation/fetcher-cache-internals/index.html Mon Feb
8 16:43:52 2016
@@ -83,7 +83,7 @@
<div class="col-md-8">
<h1>Mesos Fetcher Cache Internals</h1>
-<p>It assumed that readers of this document are familiar with the contents of
the <a href="/documentation/latest/fetcher/">Mesos fetcher user guide</a>. The
present document makes direct references to notions defined in the former.</p>
+<p>It assumed that readers of this document are familiar with the contents of
the <a href="/documentation/latest/./fetcher/">Mesos fetcher user guide</a>.
The present document makes direct references to notions defined in the
former.</p>
<h2>Design goals for the initial fetcher cache prototype:</h2>
Modified: mesos/site/publish/documentation/fetcher/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/fetcher/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/fetcher/index.html (original)
+++ mesos/site/publish/documentation/fetcher/index.html Mon Feb 8 16:43:52 2016
@@ -90,7 +90,7 @@ from local file systems.</p>
<h2>What is the Mesos fetcher?</h2>
-<p>The Mesos fetcher is a mechanism to download resources into the <a
href="/documentation/latest/sandbox/">sandbox
+<p>The Mesos fetcher is a mechanism to download resources into the <a
href="/documentation/latest/./sandbox/">sandbox
directory</a> of a task in preparation of running
the task. As part of a TaskInfo message, the framework ordering the
task’s
execution provides a list of <code>CommandInfo::URI</code> protobuf values,
which becomes
@@ -100,7 +100,7 @@ the input to the Mesos fetcher.</p>
supports the HTTP, HTTPS, FTP and FTPS protocols. If the requested URI is based
on some other protocol, then the fetcher tries to utilise a local Hadoop client
and hence supports any protocol supported by the Hadoop client, e.g., HDFS, S3.
-See the slave <a href="/documentation/latest/configuration/">configuration
documentation</a>
+See the slave <a href="/documentation/latest/./configuration/">configuration
documentation</a>
for how to configure the slave with a path to the Hadoop client.</p>
<p>By default, each requested URI is downloaded directly into the sandbox
directory
@@ -406,7 +406,7 @@ running the present task, right after fe
<h2>Implementation Details</h2>
-<p>The <a href="/documentation/latest/fetcher-cache-internals/">Mesos Fetcher
Cache Internals</a> describes how the fetcher cache is implemented.</p>
+<p>The <a href="/documentation/latest/./fetcher-cache-internals/">Mesos
Fetcher Cache Internals</a> describes how the fetcher cache is implemented.</p>
</div>
</div>
Modified:
mesos/site/publish/documentation/high-availability-framework-guide/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/high-availability-framework-guide/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
---
mesos/site/publish/documentation/high-availability-framework-guide/index.html
(original)
+++
mesos/site/publish/documentation/high-availability-framework-guide/index.html
Mon Feb 8 16:43:52 2016
@@ -91,7 +91,7 @@ should consider include:</p>
<ul>
<li><p>The Mesos master that a framework scheduler is connected to might fail,
for
example by crashing or by losing network connectivity. If the master has been
-configured to use <a
href="/documentation/latest/high-availability/">high-availability mode</a>,
this will
+configured to use <a
href="/documentation/latest/./high-availability/">high-availability mode</a>,
this will
result in promoting another Mesos master replica to become the current
leader. In this situation, the scheduler should re-register with the new
master and ensure that task state is consistent.</p></li>
@@ -127,7 +127,7 @@ launch a task, that message might not be
due to a transient network failure). To address this, the framework scheduler
should set a timeout after attempting to launch a new task. If the scheduler
hasn’t seen a status update for the new task before the timeout fires, it
-should take corrective action—for example, by performing <a
href="/documentation/latest/reconciliation/">task state reconciliation</a>,
+should take corrective action—for example, by performing <a
href="/documentation/latest/./reconciliation/">task state reconciliation</a>,
and then launching a new copy of the task if necessary.</p>
<ul>
@@ -250,7 +250,7 @@ initial state and several possible termi
<li><p>A task begins in the <code>TASK_STAGING</code> state. A task is in this
state when the
master has received the framework’s request to launch the task but the
task
has not yet started to run. In this state, the task’s dependencies are
-fetched—for example, using the <a
href="/documentation/latest/fetcher/">Mesos fetcher cache</a>.</p></li>
+fetched—for example, using the <a
href="/documentation/latest/./fetcher/">Mesos fetcher cache</a>.</p></li>
<li><p>The <code>TASK_STARTING</code> state is optional and intended primarily
for use by
custom executors. It can be used to describe the fact that a custom executor
has learned about the task (and maybe started fetching its dependencies) but
has
@@ -262,7 +262,7 @@ terminal states listed below).</p>
<ul>
<li><p>If a framework attempts to launch a task but does not receive a status
update for it within a timeout, the framework should perform
-<a href="/documentation/latest/reconciliation/">reconciliation</a>. That is,
it should ask the master for
+<a href="/documentation/latest/./reconciliation/">reconciliation</a>. That is,
it should ask the master for
the current state of the task. The master will reply with
<code>TASK_LOST</code> for
unknown tasks. The framework can then use this to distinguish between tasks
that are slow to launch and tasks that the master has never heard about
@@ -309,7 +309,7 @@ that the agent has failed and takes step
agent gets disconnected are as follows for each framework running on that
agent:</p>
<ul>
-<li><p>If the framework is <a
href="/documentation/latest/slave-recovery/">checkpointing</a>: No immediate
action is taken. The agent is
+<li><p>If the framework is <a
href="/documentation/latest/./slave-recovery/">checkpointing</a>: No immediate
action is taken. The agent is
given a chance to reconnect until health checks time out.</p></li>
<li><p>If the framework is not-checkpointing: All the framework’s tasks
and executors are considered lost. Master
immediately sends <code>TASK_LOST</code> status updates for the tasks. These
updates are not delivered reliably to the
Modified: mesos/site/publish/documentation/high-availability/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/high-availability/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/high-availability/index.html (original)
+++ mesos/site/publish/documentation/high-availability/index.html Mon Feb 8
16:43:52 2016
@@ -85,7 +85,7 @@
<p>If the Mesos master is unavailable, existing tasks can continue to execute,
but new resources cannot be allocated and new tasks cannot be launched. To
reduce the chance of this situation occurring, Mesos has a high-availability
mode that uses multiple Mesos masters: one active master (called the
<em>leader</em> or leading master) and several <em>backups</em> in case it
fails. The masters elect the leader, with <a
href="http://zookeeper.apache.org/";>Apache ZooKeeper</a> both coordinating the
election and handling leader detection by masters, slaves, and scheduler
drivers. More information regarding <a
href="http://zookeeper.apache.org/doc/trunk/recipes.html#sc_leaderElection";>how
leader election works</a> is available on the Apache Zookeeper website.</p>
-<p>This document describes how to configure Mesos to run in high-availability
mode. For more information on developing highly available frameworks, see a <a
href="/documentation/latest/high-availability-framework-guide/">companion
document</a>.</p>
+<p>This document describes how to configure Mesos to run in high-availability
mode. For more information on developing highly available frameworks, see a <a
href="/documentation/latest/./high-availability-framework-guide/">companion
document</a>.</p>
<p><strong>Note</strong>: This document assumes you know how to start, run,
and work with ZooKeeper, whose client library is included in the standard Mesos
build.</p>
@@ -100,7 +100,7 @@
<ul>
<li><p>Start the mesos-master binaries using the <code>--zk</code> flag, e.g.
<code>--zk=zk://host1:port1,host2:port2,.../path</code></p></li>
<li><p>Start the mesos-slave binaries with
<code>--master=zk://host1:port1,host2:port2,.../path</code></p></li>
-<li><p>Start any framework schedulers using the same <code>zk</code> path as
in the last two steps. The SchedulerDriver must be constructed with this path,
as shown in the <a
href="/documentation/latest/app-framework-development-guide/">Framework
Development Guide</a>.</p></li>
+<li><p>Start any framework schedulers using the same <code>zk</code> path as
in the last two steps. The SchedulerDriver must be constructed with this path,
as shown in the <a
href="/documentation/latest/./app-framework-development-guide/">Framework
Development Guide</a>.</p></li>
</ul>
</li>
</ol>
@@ -108,7 +108,7 @@
<p>From now on, the Mesos masters and slaves 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 slaves.</p>
-<p>Refer to the <a
href="/documentation/latest/app-framework-development-guide/">Scheduler API</a>
for how to deal with leadership changes.</p>
+<p>Refer to the <a
href="/documentation/latest/./app-framework-development-guide/">Scheduler
API</a> for how to deal with leadership changes.</p>
<h2>Component Disconnection Handling</h2>
@@ -136,7 +136,7 @@
<ul>
<li><p>The slave fails health checks from the leader.</p></li>
-<li><p>The leader marks the slave as deactivated and sends its tasks to the
LOST state. The <a
href="/documentation/latest/app-framework-development-guide/">Framework
Development Guide</a> describes these various task states.</p></li>
+<li><p>The leader marks the slave as deactivated and sends its tasks to the
LOST state. The <a
href="/documentation/latest/./app-framework-development-guide/">Framework
Development Guide</a> describes these various task states.</p></li>
<li><p>Deactivated slaves may not re-register with the leader and are told to
shut down upon any post-deactivation communication.</p></li>
</ul>
Modified: mesos/site/publish/documentation/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/index.html (original)
+++ mesos/site/publish/documentation/index.html Mon Feb 8 16:43:52 2016
@@ -86,115 +86,116 @@
<h2>Mesos Fundamentals</h2>
<ul>
-<li><a href="/documentation/latest/architecture/">Mesos Architecture</a>
providing an overview of Mesos concepts.</li>
-<li><a href="/documentation/latest/presentations/">Video and Slides of Mesos
Presentations</a></li>
+<li><a href="/documentation/latest/./architecture/">Mesos Architecture</a>
providing an overview of Mesos concepts.</li>
+<li><a href="/documentation/latest/./presentations/">Video and Slides of Mesos
Presentations</a></li>
</ul>
<h2>Running Mesos</h2>
<ul>
-<li><a href="/documentation/latest/getting-started/">Getting Started</a> for
basic instructions on compiling and installing Mesos.</li>
-<li><a href="/documentation/latest/upgrades/">Upgrades</a> for upgrading a
Mesos cluster.</li>
-<li><a href="/documentation/latest/configuration/">Configuration</a> for
command-line arguments.</li>
-<li><a href="/documentation/latest/containerizer/">Containerizer</a> for
containerizer overview and use cases.
+<li><a href="/documentation/latest/./getting-started/">Getting Started</a> for
basic instructions on compiling and installing Mesos.</li>
+<li><a href="/documentation/latest/./upgrades/">Upgrades</a> for upgrading a
Mesos cluster.</li>
+<li><a href="/documentation/latest/./configuration/">Configuration</a> for
command-line arguments.</li>
+<li><a href="endpoints/">HTTP Endpoints</a> for available HTTP endpoints.</li>
+<li><a href="/documentation/latest/./containerizer/">Containerizer</a> for
containerizer overview and use cases.
<ul>
-<li><a href="/documentation/latest/containerizer-internals/">Containerizer
Internals</a> for implementation details of containerizers.</li>
-<li><a href="/documentation/latest/mesos-containerizer/">Mesos
Containerizer</a> default containerizer, supports both Linux and POSIX
systems.</li>
-<li><a href="/documentation/latest/docker-containerizer/">Docker
Containerizer</a> for launching a Docker image as a Task, or as an
Executor.</li>
-<li><a href="/documentation/latest/external-containerizer/">External
Containerizer</a> for custom containerization implementations (deprecated).</li>
+<li><a href="/documentation/latest/./containerizer-internals/">Containerizer
Internals</a> for implementation details of containerizers.</li>
+<li><a href="/documentation/latest/./mesos-containerizer/">Mesos
Containerizer</a> default containerizer, supports both Linux and POSIX
systems.</li>
+<li><a href="/documentation/latest/./docker-containerizer/">Docker
Containerizer</a> for launching a Docker image as a Task, or as an
Executor.</li>
+<li><a href="/documentation/latest/./external-containerizer/">External
Containerizer</a> for custom containerization implementations (deprecated).</li>
</ul>
</li>
-<li><a href="/documentation/latest/roles/">Roles</a></li>
-<li><a href="/documentation/latest/authentication/">Framework
Authentication</a></li>
-<li><a href="/documentation/latest/authorization/">Framework
Authorization</a></li>
-<li><a href="/documentation/latest/framework-rate-limiting/">Framework Rate
Limiting</a></li>
-<li><a href="/documentation/latest/logging/">Logging</a></li>
-<li><a href="/documentation/latest/high-availability/">High Availability</a>
for running multiple masters simultaneously.</li>
-<li><a href="/documentation/latest/operational-guide/">Operational
Guide</a></li>
-<li><a href="/documentation/latest/monitoring/">Monitoring</a></li>
-<li><a href="/documentation/latest/network-monitoring/">Network Monitoring and
Isolation</a></li>
-<li><a href="/documentation/latest/slave-recovery/">Slave Recovery</a> for
doing seamless upgrades.</li>
-<li><a href="/documentation/latest/maintenance/">Maintenance</a> for
performing maintenance on a Mesos cluster.</li>
-<li><a href="/documentation/latest/tools/">Tools</a> for setting up and
running a Mesos cluster.</li>
-<li><a href="/documentation/latest/ssl/">SSL</a> for enabling and enforcing
SSL communication.</li>
-<li><a href="/documentation/latest/mesos-provisioner/">Mesos Image
Provisioner</a> for provisioning container filesystems from different image
formats.</li>
+<li><a href="/documentation/latest/./roles/">Roles</a></li>
+<li><a href="/documentation/latest/./authentication/">Framework
Authentication</a></li>
+<li><a href="/documentation/latest/./authorization/">Framework
Authorization</a></li>
+<li><a href="/documentation/latest/./framework-rate-limiting/">Framework Rate
Limiting</a></li>
+<li><a href="/documentation/latest/./logging/">Logging</a></li>
+<li><a href="/documentation/latest/./high-availability/">High Availability</a>
for running multiple masters simultaneously.</li>
+<li><a href="/documentation/latest/./operational-guide/">Operational
Guide</a></li>
+<li><a href="/documentation/latest/./monitoring/">Monitoring</a></li>
+<li><a href="/documentation/latest/./network-monitoring/">Network Monitoring
and Isolation</a></li>
+<li><a href="/documentation/latest/./slave-recovery/">Slave Recovery</a> for
doing seamless upgrades.</li>
+<li><a href="/documentation/latest/./maintenance/">Maintenance</a> for
performing maintenance on a Mesos cluster.</li>
+<li><a href="/documentation/latest/./tools/">Tools</a> for setting up and
running a Mesos cluster.</li>
+<li><a href="/documentation/latest/./ssl/">SSL</a> for enabling and enforcing
SSL communication.</li>
+<li><a href="/documentation/latest/./mesos-provisioner/">Mesos Image
Provisioner</a> for provisioning container filesystems from different image
formats.</li>
</ul>
<h2>Advanced Features</h2>
<ul>
-<li><a href="/documentation/latest/attributes-resources/">Attributes and
Resources</a> for how to describe the slaves that comprise a cluster.</li>
-<li><a href="/documentation/latest/fetcher/">Fetcher Cache</a> for how to
configure the Mesos fetcher cache.</li>
-<li><a
href="/documentation/latest/networking-for-mesos-managed-containers/">Networking
for Mesos-managed Containers</a></li>
-<li><a href="/documentation/latest/oversubscription/">Oversubscription</a> for
how to configure Mesos to take advantage of unused resources to launch
“best-effort” tasks.</li>
-<li><a href="/documentation/latest/persistent-volume/">Persistent Volume</a>
for how to allow tasks to access persistent storage resources.</li>
-<li><a href="/documentation/latest/quota/">Quota</a> for how to configure
Mesos to provide guaranteed resource allocations for use by a role.</li>
-<li><a href="/documentation/latest/reservation/">Reservation</a> for how
operators and frameworks can reserve resources on individual agents for use by
a role.</li>
+<li><a href="/documentation/latest/./attributes-resources/">Attributes and
Resources</a> for how to describe the slaves that comprise a cluster.</li>
+<li><a href="/documentation/latest/./fetcher/">Fetcher Cache</a> for how to
configure the Mesos fetcher cache.</li>
+<li><a
href="/documentation/latest/./networking-for-mesos-managed-containers/">Networking
for Mesos-managed Containers</a></li>
+<li><a href="/documentation/latest/./oversubscription/">Oversubscription</a>
for how to configure Mesos to take advantage of unused resources to launch
“best-effort” tasks.</li>
+<li><a href="/documentation/latest/./persistent-volume/">Persistent Volume</a>
for how to allow tasks to access persistent storage resources.</li>
+<li><a href="/documentation/latest/./quota/">Quota</a> for how to configure
Mesos to provide guaranteed resource allocations for use by a role.</li>
+<li><a href="/documentation/latest/./reservation/">Reservation</a> for how
operators and frameworks can reserve resources on individual agents for use by
a role.</li>
</ul>
<h2>Running Mesos Frameworks</h2>
<ul>
-<li><a href="/documentation/latest/frameworks/">Mesos frameworks</a> for a
list of apps built on top of Mesos and instructions on how to run them.</li>
-<li><a href="/documentation/latest/sandbox/">Sandbox</a> describes a useful
debugging arena for most users.</li>
+<li><a href="/documentation/latest/./frameworks/">Mesos frameworks</a> for a
list of apps built on top of Mesos and instructions on how to run them.</li>
+<li><a href="/documentation/latest/./sandbox/">Sandbox</a> describes a useful
debugging arena for most users.</li>
</ul>
<h2>Developing Mesos Frameworks</h2>
<ul>
-<li><a href="/documentation/latest/app-framework-development-guide/">Framework
Development Guide</a> describes how to build applications on top of Mesos.</li>
-<li><a
href="/documentation/latest/high-availability-framework-guide/">Designing
Highly Available Mesos Frameworks</a></li>
-<li><a href="/documentation/latest/reconciliation/">Reconciliation</a> for
ensuring a framework’s state remains eventually consistent in the face of
failures.</li>
-<li><a href="/documentation/latest/scheduler-http-api/">Scheduler HTTP API</a>
describes the new HTTP API for communication between schedulers and the Mesos
master.</li>
-<li><a href="/documentation/latest/executor-http-api/">Executor HTTP API</a>
describes the new HTTP API for communication between executors and the Mesos
agent.</li>
+<li><a
href="/documentation/latest/./app-framework-development-guide/">Framework
Development Guide</a> describes how to build applications on top of Mesos.</li>
+<li><a
href="/documentation/latest/./high-availability-framework-guide/">Designing
Highly Available Mesos Frameworks</a></li>
+<li><a href="/documentation/latest/./reconciliation/">Reconciliation</a> for
ensuring a framework’s state remains eventually consistent in the face of
failures.</li>
+<li><a href="/documentation/latest/./scheduler-http-api/">Scheduler HTTP
API</a> describes the new HTTP API for communication between schedulers and the
Mesos master.</li>
+<li><a href="/documentation/latest/./executor-http-api/">Executor HTTP API</a>
describes the new HTTP API for communication between executors and the Mesos
agent.</li>
<li><a href="/api/latest/java/">Javadoc</a> documents the Mesos Java API.</li>
<li><a href="/api/latest/c++/namespacemesos.html">Doxygen</a> documents the
Mesos C++ API.</li>
-<li><a href="/documentation/latest/tools/">Developer Tools</a> for hacking on
Mesos or writing frameworks.</li>
-<li><a href="/documentation/latest/versioning/">Versioning</a> describes how
Mesos does API and release versioning.</li>
+<li><a href="/documentation/latest/./tools/">Developer Tools</a> for hacking
on Mesos or writing frameworks.</li>
+<li><a href="/documentation/latest/./versioning/">Versioning</a> describes how
Mesos does API and release versioning.</li>
</ul>
<h2>Extending Mesos</h2>
<ul>
-<li><a href="/documentation/latest/modules/">Mesos Modules</a> for specifying
Mesos modules for master, slave and tests.</li>
-<li><a href="/documentation/latest/allocation-module/">Allocation Modules</a>
for how to write custom resource allocators.</li>
+<li><a href="/documentation/latest/./modules/">Mesos Modules</a> for
specifying Mesos modules for master, slave and tests.</li>
+<li><a href="/documentation/latest/./allocation-module/">Allocation
Modules</a> for how to write custom resource allocators.</li>
</ul>
<h2>Contributing to Mesos</h2>
<ul>
-<li><a href="/documentation/latest/reporting-a-bug/">Reporting an Issue,
Improvement, or Feature</a> for getting started with JIRA.</li>
-<li><a href="/documentation/latest/submitting-a-patch/">Submitting a Patch</a>
for getting started with ReviewBoard and our tooling around it.</li>
-<li><a href="/documentation/latest/testing-patterns/">Testing Patterns</a> for
tips and tricks used in Mesos tests.</li>
-<li><a href="/documentation/latest/effective-code-reviewing/">Effective Code
Reviewing</a> guidelines, tips, and learnings for how to do effective code
reviews.</li>
-<li><a
href="/documentation/latest/engineering-principles-and-practices/">Engineering
Principles and Practices</a> to serve as a shared set of project-level values
for the community.</li>
-<li><a href="/documentation/latest/committing/">Committing</a> guidelines for
committing changes.</li>
-<li><a href="/documentation/latest/committers/">Committers and Maintainers</a>
a listing of project committers and component maintainers; useful when seeking
feedback.</li>
+<li><a href="/documentation/latest/./reporting-a-bug/">Reporting an Issue,
Improvement, or Feature</a> for getting started with JIRA.</li>
+<li><a href="/documentation/latest/./submitting-a-patch/">Submitting a
Patch</a> for getting started with ReviewBoard and our tooling around it.</li>
+<li><a href="/documentation/latest/./testing-patterns/">Testing Patterns</a>
for tips and tricks used in Mesos tests.</li>
+<li><a href="/documentation/latest/./effective-code-reviewing/">Effective Code
Reviewing</a> guidelines, tips, and learnings for how to do effective code
reviews.</li>
+<li><a
href="/documentation/latest/./engineering-principles-and-practices/">Engineering
Principles and Practices</a> to serve as a shared set of project-level values
for the community.</li>
+<li><a href="/documentation/latest/./committing/">Committing</a> guidelines
for committing changes.</li>
+<li><a href="/documentation/latest/./committers/">Committers and
Maintainers</a> a listing of project committers and component maintainers;
useful when seeking feedback.</li>
<li><a href="/api/latest/c++/">Doxygen</a> documents the internal Mesos
APIs.</li>
-<li><a href="/documentation/latest/documentation-guide/">Documentation
Guide</a>
+<li><a href="/documentation/latest/./documentation-guide/">Documentation
Guide</a>
<ul>
-<li><a href="/documentation/latest/c++-style-guide/">C++ Style Guide</a></li>
-<li><a href="/documentation/latest/doxygen-style-guide/">Doxygen Style
Guide</a></li>
-<li><a href="/documentation/latest/markdown-style-guide/">Markdown Style
Guide</a></li>
+<li><a href="/documentation/latest/./c++-style-guide/">C++ Style Guide</a></li>
+<li><a href="/documentation/latest/./doxygen-style-guide/">Doxygen Style
Guide</a></li>
+<li><a href="/documentation/latest/./markdown-style-guide/">Markdown Style
Guide</a></li>
</ul>
</li>
-<li><a href="/documentation/latest/roadmap/">Development Roadmap</a></li>
-<li><a href="/documentation/latest/release-guide/">Release Guide</a></li>
+<li><a href="/documentation/latest/./roadmap/">Development Roadmap</a></li>
+<li><a href="/documentation/latest/./release-guide/">Release Guide</a></li>
</ul>
<h2>More Info about Mesos</h2>
<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="/documentation/latest/./powered-by-mesos/">Powered by Mesos</a>
lists organizations and software that are powered by Apache Mesos.</li>
<li>Academic Papers and Project History</li>
</ul>
Modified: mesos/site/publish/documentation/latest/allocation-module/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/allocation-module/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/allocation-module/index.html
(original)
+++ mesos/site/publish/documentation/latest/allocation-module/index.html Mon
Feb 8 16:43:52 2016
@@ -146,7 +146,7 @@ mesos::modules::Module<Allocator>
createExternalAllocator);
</code></pre>
-<p>Refer to the <a href="/documentation/latest/modules/">Mesos Modules
documentation</a> for instructions on how to compile and load a module in Mesos
master.</p>
+<p>Refer to the <a href="/documentation/latest/./modules/">Mesos Modules
documentation</a> for instructions on how to compile and load a module in Mesos
master.</p>
</div>
</div>
Modified:
mesos/site/publish/documentation/latest/app-framework-development-guide/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/app-framework-development-guide/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
---
mesos/site/publish/documentation/latest/app-framework-development-guide/index.html
(original)
+++
mesos/site/publish/documentation/latest/app-framework-development-guide/index.html
Mon Feb 8 16:43:52 2016
@@ -210,7 +210,7 @@ virtual void error(SchedulerDriver* driv
<h3>Handling Failures</h3>
-<p>How to build Mesos frameworks that remain available in the face of failures
is discussed in a <a
href="/documentation/latest/high-availability-framework-guide/">separate
document</a>.</p>
+<p>How to build Mesos frameworks that remain available in the face of failures
is discussed in a <a
href="/documentation/latest/./high-availability-framework-guide/">separate
document</a>.</p>
<h2>Working with Executors</h2>
@@ -310,7 +310,7 @@ virtual void error(ExecutorDriver* drive
<p>After creating your custom executor, you need to make it available to all
slaves in the cluster.</p>
-<p>One way to distribute your framework executor is to let the <a
href="/documentation/latest/fetcher/">Mesos fetcher</a> download it on-demand
when your scheduler launches tasks on that slave. <code>ExecutorInfo</code> is
a Protocol Buffer Message class (defined in
<code>include/mesos/mesos.proto</code>), and it contains a field of type
<code>CommandInfo</code>. <code>CommandInfo</code> allows schedulers to
specify, among other things, a number of resources as URIs. These resources are
fetched to a sandbox directory on the slave before attempting to execute the
<code>ExecutorInfo</code> command. Several URI schemes are supported, including
HTTP, FTP, HDFS, and S3 (e.g. see src/examples/java/TestFramework.java for an
example of this).</p>
+<p>One way to distribute your framework executor is to let the <a
href="/documentation/latest/./fetcher/">Mesos fetcher</a> download it on-demand
when your scheduler launches tasks on that slave. <code>ExecutorInfo</code> is
a Protocol Buffer Message class (defined in
<code>include/mesos/mesos.proto</code>), and it contains a field of type
<code>CommandInfo</code>. <code>CommandInfo</code> allows schedulers to
specify, among other things, a number of resources as URIs. These resources are
fetched to a sandbox directory on the slave before attempting to execute the
<code>ExecutorInfo</code> command. Several URI schemes are supported, including
HTTP, FTP, HDFS, and S3 (e.g. see src/examples/java/TestFramework.java for an
example of this).</p>
<p>Alternatively, you can pass the <code>frameworks_home</code> configuration
option (defaults to: <code>MESOS_HOME/frameworks</code>) to your
<code>mesos-slave</code> daemons when you launch them to specify where your
framework executors are stored (e.g. on an NFS mount that is available to all
slaves), then use a relative path in <code>CommandInfo.uris</code>, and the
slave will prepend the value of <code>frameworks_home</code> to the relative
path provided.</p>
Modified: mesos/site/publish/documentation/latest/architecture/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/architecture/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/architecture/index.html (original)
+++ mesos/site/publish/documentation/latest/architecture/index.html Mon Feb 8
16:43:52 2016
@@ -89,7 +89,7 @@
<p>The master enables fine-grained sharing of resources (CPU, RAM, …)
across frameworks by making them <em>resource offers</em>. Each resource offer
contains a list of <slave ID, resource1: amount1, resource2, amount2,
…>. The master decides <em>how many</em> resources to offer to each
framework according to a given organizational policy, such as fair sharing or
strict priority. To support a diverse set of policies, the master employs a
modular architecture that makes it easy to add new allocation modules via a
plugin mechanism.</p>
-<p>A framework running on top of Mesos consists of two components: a
<em>scheduler</em> that registers with the master to be offered resources, and
an <em>executor</em> process that is launched on slave nodes to run the
framework’s tasks (see the <a
href="/documentation/latest/app-framework-development-guide/">App/Framework
development guide</a> for more details about framework schedulers and
executors). While the master determines <strong>how many</strong> resources are
offered to each framework, the frameworks' schedulers select
<strong>which</strong> of the offered resources to use. When a frameworks
accepts offered resources, it passes to Mesos a description of the tasks it
wants to run on them. In turn, Mesos launches the tasks on the corresponding
slaves.</p>
+<p>A framework running on top of Mesos consists of two components: a
<em>scheduler</em> that registers with the master to be offered resources, and
an <em>executor</em> process that is launched on slave nodes to run the
framework’s tasks (see the <a
href="/documentation/latest/./app-framework-development-guide/">App/Framework
development guide</a> for more details about framework schedulers and
executors). While the master determines <strong>how many</strong> resources are
offered to each framework, the frameworks' schedulers select
<strong>which</strong> of the offered resources to use. When a frameworks
accepts offered resources, it passes to Mesos a description of the tasks it
wants to run on them. In turn, Mesos launches the tasks on the corresponding
slaves.</p>
<h2>Example of resource offer</h2>
Modified:
mesos/site/publish/documentation/latest/attributes-resources/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/attributes-resources/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/attributes-resources/index.html
(original)
+++ mesos/site/publish/documentation/latest/attributes-resources/index.html Mon
Feb 8 16:43:52 2016
@@ -168,31 +168,33 @@ key : text ( "(" resourceRole ")" )?
resourceRole : text | "*"
</code></pre>
-<p>Note that <code>resourceRole</code> must be a valid role name; see the <a
href="/documentation/latest/roles/">roles</a> documentation for details.</p>
+<p>Note that <code>resourceRole</code> must be a valid role name; see the <a
href="/documentation/latest/./roles/">roles</a> documentation for details.</p>
<h2>Predefined Uses & Conventions</h2>
-<p>The Mesos master has a few resources that it pre-defines in how it handles
them. At the current time, this list consist of:</p>
+<p>There are several kinds of resources that have predefined behavior:</p>
<ul>
<li><code>cpus</code></li>
-<li><code>mem</code></li>
<li><code>disk</code></li>
+<li><code>mem</code></li>
<li><code>ports</code></li>
</ul>
-<p>In particular, a slave without <code>cpus</code> and <code>mem</code>
resources will never have its resources advertised to any frameworks. Also,
the Master’s user interface interprets the scalars in <code>mem</code>
and <code>disk</code> in terms of <em><code>MB</code></em>. IE: the value
<code>15000</code> is displayed as <code>14.65GB</code>.</p>
+<p>Note that <code>disk</code> and <code>mem</code> resources are specified in
megabytes. The master’s user interface will convert resource values into
a more human-readable format: for example, the value <code>15000</code> will be
displayed as <code>14.65GB</code>.</p>
+
+<p>A slave without <code>cpus</code> and <code>mem</code> resources will not
have its resources advertised to any frameworks.</p>
<h2>Examples</h2>
-<p>Here are some examples for configuring the Mesos slaves.</p>
+<p>By default, Mesos will try to autodetect the resources available at the
local machine when <code>mesos-slave</code> starts up. Alternatively, you can
explicitly configure which resources a slave should make available.</p>
+
+<p>Here are some examples of how to configure the resources at a Mesos
slave:</p>
<pre><code>--resources='cpus:24;mem:24576;disk:409600;ports:[21000-24000,30000-34000];bugs(debug_role):{a,b,c}'
--resources='[{"name":"cpus","type":"SCALAR","scalar":{"value":24}},{"name":"mem","type":"SCALAR","scalar":{"value":24576}},{"name":"disk","type":"SCALAR","scalar":{"value":409600}},{"name":"ports","type":"RANGES","ranges":{"range":[{"begin":21000,"end":24000},{"begin":30000,"end":34000}]}},{"name":"bugs","type":"SET","set":{"item":["a","b","c"]},"role":"debug_role"}]'
-
---attributes='rack:abc;zone:west;os:centos5;level:10;keys:[1000-1500]'
</code></pre>
<p>Or given a file <code>resources.txt</code> containing the following:</p>
@@ -268,7 +270,12 @@ resourceRole : text | "*"
</ul>
-<p>In the case of attributes, we end up with five attributes:</p>
+<p>To configure the attributes of a Mesos slave, you can use the
<code>--attributes</code> command-line flag of <code>mesos-slave</code>:</p>
+
+<pre><code>--attributes='rack:abc;zone:west;os:centos5;level:10;keys:[1000-1500]'
+</code></pre>
+
+<p>That will result in configuring the following five attributes:</p>
<ul>
<li><code>rack</code> with text value <code>abc</code></li>
Modified: mesos/site/publish/documentation/latest/authentication/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/authentication/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/authentication/index.html (original)
+++ mesos/site/publish/documentation/latest/authentication/index.html Mon Feb
8 16:43:52 2016
@@ -100,7 +100,7 @@
<h2>Configuration</h2>
-<p>The <a href="/documentation/latest/configuration/">configuration
options</a> that are used by the authentication mechanism are as follows:</p>
+<p>The <a href="/documentation/latest/./configuration/">configuration
options</a> that are used by the authentication mechanism are as follows:</p>
<h3>Masters</h3>
Modified: mesos/site/publish/documentation/latest/authorization/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/authorization/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/authorization/index.html (original)
+++ mesos/site/publish/documentation/latest/authorization/index.html Mon Feb 8
16:43:52 2016
@@ -132,7 +132,7 @@
<p>The currently supported <code>Objects</code> are:</p>
<ol>
-<li>“roles”: Resource <a
href="/documentation/latest/roles/">roles</a> that framework can register with
(used by “register_frameworks” and “set_quotas”
actions)</li>
+<li>“roles”: Resource <a
href="/documentation/latest/./roles/">roles</a> that framework can register
with (used by “register_frameworks” and “set_quotas”
actions)</li>
<li>“users”: Unix user to launch the task/executor as (used by
“run_tasks” actions)</li>
<li>“framework_principals”: Framework principals that can be torn
down by HTTP POST (used by “teardown_frameworks” actions).</li>
<li>“resources”: Resources that can be reserved. Currently the
only types considered by the default authorizer are <code>ANY</code> and
<code>NONE</code> (used by “reserves” action).</li>
@@ -303,7 +303,7 @@
<p>For more information on master command-line flags, see the
-<a href="/documentation/latest/configuration/">configuration</a> page.</p>
+<a href="/documentation/latest/./configuration/">configuration</a> page.</p>
</div>
</div>
Modified: mesos/site/publish/documentation/latest/c++-style-guide/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/c%2B%2B-style-guide/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/c++-style-guide/index.html
(original)
+++ mesos/site/publish/documentation/latest/c++-style-guide/index.html Mon Feb
8 16:43:52 2016
@@ -83,7 +83,7 @@
<div class="col-md-8">
<h1>Mesos C++ Style Guide</h1>
-<p>The Mesos codebase follows the <a
href="http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml";>Google
C++ Style Guide</a> with some notable differences, as described below. Note
that the <a href="/documentation/latest/clang-format/">clang-format</a> tool
can be helpful to ensure that some of the mechanical style rules are obeyed.</p>
+<p>The Mesos codebase follows the <a
href="http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml";>Google
C++ Style Guide</a> with some notable differences, as described below. Note
that the <a href="/documentation/latest/./clang-format/">clang-format</a> tool
can be helpful to ensure that some of the mechanical style rules are obeyed.</p>
<h2>Scoping</h2>
Modified: mesos/site/publish/documentation/latest/clang-format/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/clang-format/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/clang-format/index.html (original)
+++ mesos/site/publish/documentation/latest/clang-format/index.html Mon Feb 8
16:43:52 2016
@@ -85,7 +85,7 @@
<p><a
href="http://llvm.org/releases/3.5.1/tools/clang/docs/ClangFormat.html";>ClangFormat</a>
is an automatic source code formatting tool which helps us focus on the code
rather than the formatting.</p>
-<blockquote><p>The provided configurations try to honor the <a
href="/documentation/latest/c++-style-guide/">Mesos C++ Style Guide</a> as much
as possible, but there are some limitations which require manual attention.
Even with these limitations however, ClangFormat will be extremely useful for
your workflow!</p></blockquote>
+<blockquote><p>The provided configurations try to honor the <a
href="/documentation/latest/./c++-style-guide/">Mesos C++ Style Guide</a> as
much as possible, but there are some limitations which require manual
attention. Even with these limitations however, ClangFormat will be extremely
useful for your workflow!</p></blockquote>
<h2>Setup</h2>
Modified: mesos/site/publish/documentation/latest/committers/index.html
URL:
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/committers/index.html?rev=1729207&r1=1729206&r2=1729207&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/committers/index.html (original)
+++ mesos/site/publish/documentation/latest/committers/index.html Mon Feb 8
16:43:52 2016
@@ -87,7 +87,7 @@
<h2>Becoming a committer</h2>
-<p>Every new committer has to be proposed by a current committer and then
voted in by the members of the Mesos PMC. For details about this process and
for candidate requirements see the general <a
href="https://community.apache.org/newcommitter.html";>Apache guidelines for
assessing new candidates for committership</a>. Candidates prepare for their
nomination as committer by contributing to the Mesos project and its community,
by acting according to the <a href="http://theapacheway.com";>Apache Way</a>,
and by generally following the path <a
href="https://community.apache.org/contributors/";>from contributor to
committer</a> for Apache projects. Specifically for the Mesos project, you can
make use of the <a
href="/documentation/latest/committer-candidate-checklist/">Apache Mesos
Committer Candidate Checklist</a> for suggestions of what kind of contributions
and demonstrated behaviors can be instrumental, and to keep track of your
progress.</p>
+<p>Every new committer has to be proposed by a current committer and then
voted in by the members of the Mesos PMC. For details about this process and
for candidate requirements see the general <a
href="https://community.apache.org/newcommitter.html";>Apache guidelines for
assessing new candidates for committership</a>. Candidates prepare for their
nomination as committer by contributing to the Mesos project and its community,
by acting according to the <a href="http://theapacheway.com";>Apache Way</a>,
and by generally following the path <a
href="https://community.apache.org/contributors/";>from contributor to
committer</a> for Apache projects. Specifically for the Mesos project, you can
make use of the <a
href="/documentation/latest/./committer-candidate-checklist/">Apache Mesos
Committer Candidate Checklist</a> for suggestions of what kind of contributions
and demonstrated behaviors can be instrumental, and to keep track of your
progress.</p>
<h2>Current Committers</h2>
