You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by gi...@apache.org on 2018/01/25 22:42:29 UTC
mesos-site git commit: Updated the website built from mesos SHA:
fa0314c.
Repository: mesos-site
Updated Branches:
refs/heads/asf-site 26e038656 -> 5482583aa
Updated the website built from mesos SHA: fa0314c.
Project: http://git-wip-us.apache.org/repos/asf/mesos-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos-site/commit/5482583a
Tree: http://git-wip-us.apache.org/repos/asf/mesos-site/tree/5482583a
Diff: http://git-wip-us.apache.org/repos/asf/mesos-site/diff/5482583a
Branch: refs/heads/asf-site
Commit: 5482583aa7cc47e2119f4a8fff66960d5c732115
Parents: 26e0386
Author: jenkins <bu...@apache.org>
Authored: Thu Jan 25 22:42:27 2018 +0000
Committer: jenkins <bu...@apache.org>
Committed: Thu Jan 25 22:42:27 2018 +0000
----------------------------------------------------------------------
content/blog/feed.xml | 2 +-
.../index.html | 2 +-
content/documentation/latest/modules/index.html | 89 +++++++++++++++++++-
content/documentation/modules/index.html | 89 +++++++++++++++++++-
4 files changed, 176 insertions(+), 6 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/5482583a/content/blog/feed.xml
----------------------------------------------------------------------
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index 2da939b..b31fddf 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -168,7 +168,7 @@ To learn more about CSI work in Mesos, you can dig into the design document <
</ul>
-<p>If you are a user and would like to suggest some areas for performance improvement, please let us know by emailing <a href="&#109;&#x61;&#105;&#108;&#116;&#x6f;&#x3a;&#100;&#x65;&#x76;&#64;&#x61;&#112;&#x61;&#x63;&#104;&#101;&#x2e;&#109;&#x65;&#x73;&#111;&#x73;&#x2e;&#x6f;&#114;&#x67;">&#100;&#x65;&#x76;&#x40;&#97;&#112;&#x61;&#99;&#104;&#101;&#x2e;&#x6d;&#x65;&#115;&#x6f;&#x73;&#46;&#x6f;&#114;&#x67;</a>.</p>
+<p>If you are a user and would like to suggest some areas for performance improvement, please let us know by emailing <a href="&#109;&#97;&#x69;&#108;&#x74;&#111;&#58;&#x64;&#x65;&#118;&#64;&#x61;&#x70;&#x61;&#99;&#104;&#x65;&#46;&#109;&#101;&#x73;&#x6f;&#x73;&#x2e;&#x6f;&#114;&#103;">&#x64;&#x65;&#x76;&#64;&#x61;&#x70;&#x61;&#x63;&#104;&#x65;&#x2e;&#109;&#x65;&#x73;&#111;&#115;&#46;&#x6f;&#114;&#x67;</a>.</p>
</content>
</entry>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/5482583a/content/blog/performance-working-group-progress-report/index.html
----------------------------------------------------------------------
diff --git a/content/blog/performance-working-group-progress-report/index.html b/content/blog/performance-working-group-progress-report/index.html
index f0a64c8..d3612fa 100644
--- a/content/blog/performance-working-group-progress-report/index.html
+++ b/content/blog/performance-working-group-progress-report/index.html
@@ -248,7 +248,7 @@
</ul>
-<p>If you are a user and would like to suggest some areas for performance improvement, please let us know by emailing <a href="mailto:dev@apache.mesos.org">dev@apache.mesos.org</a>.</p>
+<p>If you are a user and would like to suggest some areas for performance improvement, please let us know by emailing <a href="mailto:dev@apache.mesos.org">dev@apache.mesos.org</a>.</p>
</div>
</div>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/5482583a/content/documentation/latest/modules/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/modules/index.html b/content/documentation/latest/modules/index.html
index a6cc32f..4d69574 100644
--- a/content/documentation/latest/modules/index.html
+++ b/content/documentation/latest/modules/index.html
@@ -246,6 +246,82 @@ searched in the standard library paths or directories pointed to by the
<p>Here are the various module kinds currently available.</p>
+<table>
+<thead>
+<tr>
+<th> kind </th>
+<th> description </th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td> <a href="#allocator"><code>Allocator</code></a> </td>
+<td> Provides available resources to schedulers. </td>
+</tr>
+<tr>
+<td> <a href="#anonymous"><code>Anonymous</code></a> </td>
+<td> Coexists with parent process without providing any callbacks. </td>
+</tr>
+<tr>
+<td> <a href="#authentication"><code>Authenticatee</code></a> </td>
+<td> Provides the client side of an RPC authentication. </td>
+</tr>
+<tr>
+<td> <a href="#authentication"><code>Authenticator</code></a> </td>
+<td> Provides the server side of an RPC authentication. </td>
+</tr>
+<tr>
+<td> <a href="#authorization"><code>Authorizer</code></a> </td>
+<td> Allows certain principals to perform specific actions. </td>
+</tr>
+<tr>
+<td> <code>ContainerLogger</code> </td>
+<td> Container logger modules implement container log management. </td>
+</tr>
+<tr>
+<td> <a href="#hook"><code>Hook</code></a> </td>
+<td> Provides means of tying into specific callbacks. </td>
+</tr>
+<tr>
+<td> <a href="#authentication"><code>HttpAuthenticatee</code></a> </td>
+<td> Provides the client side of an HTTP authentication. </td>
+</tr>
+<tr>
+<td> <a href="#authentication"><code>HttpAuthenticator</code></a> </td>
+<td> Provides the server side of an HTTP authentication. </td>
+</tr>
+<tr>
+<td> <a href="#isolator"><code>Isolator</code></a> </td>
+<td> Enables experimenting with specialized isolation and monitoring. </td>
+</tr>
+<tr>
+<td> <a href="#master_contender_and_detector"><code>MasterContender</code></a> </td>
+<td> Contender modules allow implementing custom leader election mechanisms. </td>
+</tr>
+<tr>
+<td> <a href="#master_contender_and_detector"><code>MasterDetector</code></a> </td>
+<td> Detector modules allow implementing custom master detection mechanisms. </td>
+</tr>
+<tr>
+<td> <code>QoSController</code> </td>
+<td> QoS modules allow providing task performance guarantees. </td>
+</tr>
+<tr>
+<td> <code>ResourceEstimator</code> </td>
+<td> Estimator modules allow predicting the resources total used. </td>
+</tr>
+<tr>
+<td> <code>SecretResolver</code> </td>
+<td> Secret resolver modules allow interfacing with secure data providers. </td>
+</tr>
+<tr>
+<td> <code>TestModule</code> </td>
+<td> Used internally for testing purposes only. </td>
+</tr>
+</tbody>
+</table>
+
+
<h3>Allocator</h3>
<p>The Mesos master’s <em>allocator</em> periodically determines which framework(s) should be offered the cluster’s available resources. Allocator modules enable experimenting with specialized resource allocation algorithms. An example of these could be an allocator that provides a feature currently not supported by the built-in Hierarchical Dominant Resource Fairness allocator, like oversubscription with preemption.</p>
@@ -283,6 +359,15 @@ they are immediately instantiated when getting loaded via the
develop and plug-in new authentication methods. An example for such modules
could be to support PAM (LDAP, MySQL, NIS, UNIX) backed authentication.</p>
+<p>Mesos currently supports two variants of authentication; RPC authentication
+as used by schedulers and agents to authenticate against the master and HTTP
+authentication for securing all kinds of HTTP endpoints. See <a href="/documentation/latest/./authentication/">Authentication</a> for more.</p>
+
+<h3>Authorization</h3>
+
+<p>The authorization subsystem permits operators to configure the actions that certain
+principals are allowed to perform. See <a href="/documentation/latest/./authorization/">Authorization</a> for more.</p>
+
<h3>Hook</h3>
<p>Similar to Apache Webserver Modules, hooks allows module writers to tie into
@@ -291,9 +376,9 @@ modules but rather lets them define actions on so-called hooks.</p>
<p>The available hooks API is defined in mesos/hook.hpp and for each hook defines
the insertion point and available context. An example of this context is the
-task information which is passed to masterLaunchTaskHook.</p>
+task information which is passed to <code>masterLaunchTaskHook</code>.</p>
-<p>Some hooks take in an object (e.g. TaskInfo) and return all or part of that
+<p>Some hooks take in an object (e.g. <code>TaskInfo</code>) and return all or part of that
object (e.g. task labels), so that the hook can modify or replace the contents
in-flight. These hooks are referred to as <em>decorators</em>.</p>
http://git-wip-us.apache.org/repos/asf/mesos-site/blob/5482583a/content/documentation/modules/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/modules/index.html b/content/documentation/modules/index.html
index a4ea5cd..3e230b8 100644
--- a/content/documentation/modules/index.html
+++ b/content/documentation/modules/index.html
@@ -246,6 +246,82 @@ searched in the standard library paths or directories pointed to by the
<p>Here are the various module kinds currently available.</p>
+<table>
+<thead>
+<tr>
+<th> kind </th>
+<th> description </th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td> <a href="#allocator"><code>Allocator</code></a> </td>
+<td> Provides available resources to schedulers. </td>
+</tr>
+<tr>
+<td> <a href="#anonymous"><code>Anonymous</code></a> </td>
+<td> Coexists with parent process without providing any callbacks. </td>
+</tr>
+<tr>
+<td> <a href="#authentication"><code>Authenticatee</code></a> </td>
+<td> Provides the client side of an RPC authentication. </td>
+</tr>
+<tr>
+<td> <a href="#authentication"><code>Authenticator</code></a> </td>
+<td> Provides the server side of an RPC authentication. </td>
+</tr>
+<tr>
+<td> <a href="#authorization"><code>Authorizer</code></a> </td>
+<td> Allows certain principals to perform specific actions. </td>
+</tr>
+<tr>
+<td> <code>ContainerLogger</code> </td>
+<td> Container logger modules implement container log management. </td>
+</tr>
+<tr>
+<td> <a href="#hook"><code>Hook</code></a> </td>
+<td> Provides means of tying into specific callbacks. </td>
+</tr>
+<tr>
+<td> <a href="#authentication"><code>HttpAuthenticatee</code></a> </td>
+<td> Provides the client side of an HTTP authentication. </td>
+</tr>
+<tr>
+<td> <a href="#authentication"><code>HttpAuthenticator</code></a> </td>
+<td> Provides the server side of an HTTP authentication. </td>
+</tr>
+<tr>
+<td> <a href="#isolator"><code>Isolator</code></a> </td>
+<td> Enables experimenting with specialized isolation and monitoring. </td>
+</tr>
+<tr>
+<td> <a href="#master_contender_and_detector"><code>MasterContender</code></a> </td>
+<td> Contender modules allow implementing custom leader election mechanisms. </td>
+</tr>
+<tr>
+<td> <a href="#master_contender_and_detector"><code>MasterDetector</code></a> </td>
+<td> Detector modules allow implementing custom master detection mechanisms. </td>
+</tr>
+<tr>
+<td> <code>QoSController</code> </td>
+<td> QoS modules allow providing task performance guarantees. </td>
+</tr>
+<tr>
+<td> <code>ResourceEstimator</code> </td>
+<td> Estimator modules allow predicting the resources total used. </td>
+</tr>
+<tr>
+<td> <code>SecretResolver</code> </td>
+<td> Secret resolver modules allow interfacing with secure data providers. </td>
+</tr>
+<tr>
+<td> <code>TestModule</code> </td>
+<td> Used internally for testing purposes only. </td>
+</tr>
+</tbody>
+</table>
+
+
<h3>Allocator</h3>
<p>The Mesos master’s <em>allocator</em> periodically determines which framework(s) should be offered the cluster’s available resources. Allocator modules enable experimenting with specialized resource allocation algorithms. An example of these could be an allocator that provides a feature currently not supported by the built-in Hierarchical Dominant Resource Fairness allocator, like oversubscription with preemption.</p>
@@ -283,6 +359,15 @@ they are immediately instantiated when getting loaded via the
develop and plug-in new authentication methods. An example for such modules
could be to support PAM (LDAP, MySQL, NIS, UNIX) backed authentication.</p>
+<p>Mesos currently supports two variants of authentication; RPC authentication
+as used by schedulers and agents to authenticate against the master and HTTP
+authentication for securing all kinds of HTTP endpoints. See <a href="/documentation/latest/./authentication/">Authentication</a> for more.</p>
+
+<h3>Authorization</h3>
+
+<p>The authorization subsystem permits operators to configure the actions that certain
+principals are allowed to perform. See <a href="/documentation/latest/./authorization/">Authorization</a> for more.</p>
+
<h3>Hook</h3>
<p>Similar to Apache Webserver Modules, hooks allows module writers to tie into
@@ -291,9 +376,9 @@ modules but rather lets them define actions on so-called hooks.</p>
<p>The available hooks API is defined in mesos/hook.hpp and for each hook defines
the insertion point and available context. An example of this context is the
-task information which is passed to masterLaunchTaskHook.</p>
+task information which is passed to <code>masterLaunchTaskHook</code>.</p>
-<p>Some hooks take in an object (e.g. TaskInfo) and return all or part of that
+<p>Some hooks take in an object (e.g. <code>TaskInfo</code>) and return all or part of that
object (e.g. task labels), so that the hook can modify or replace the contents
in-flight. These hooks are referred to as <em>decorators</em>.</p>