Author: dlester
Date: Fri Aug 14 06:03:28 2015
New Revision: 1695820

URL: http://svn.apache.org/r1695820
Log:
Update Mesos documentation

Added:
    mesos/site/publish/documentation/authentication/
    mesos/site/publish/documentation/authentication/index.html
    mesos/site/publish/documentation/latest/authentication/
    mesos/site/publish/documentation/latest/authentication/index.html
    mesos/site/source/documentation/latest/authentication.md
Modified:
    mesos/site/publish/documentation/clang-format/index.html
    mesos/site/publish/documentation/configuration/index.html
    mesos/site/publish/documentation/latest/clang-format/index.html
    mesos/site/publish/documentation/latest/configuration/index.html
    mesos/site/publish/documentation/latest/mesos-c++-style-guide/index.html
    mesos/site/publish/documentation/latest/operational-guide/index.html
    mesos/site/publish/documentation/latest/powered-by-mesos/index.html
    mesos/site/publish/documentation/mesos-c++-style-guide/index.html
    mesos/site/publish/documentation/operational-guide/index.html
    mesos/site/publish/documentation/powered-by-mesos/index.html
    mesos/site/publish/sitemap.xml
    mesos/site/source/documentation/latest/clang-format.md
    mesos/site/source/documentation/latest/configuration.md
    mesos/site/source/documentation/latest/mesos-c++-style-guide.md
    mesos/site/source/documentation/latest/operational-guide.md
    mesos/site/source/documentation/latest/powered-by-mesos.md

Added: mesos/site/publish/documentation/authentication/index.html
URL: 
http://svn.apache.org/viewvc/mesos/site/publish/documentation/authentication/index.html?rev=1695820&view=auto
==============================================================================
--- mesos/site/publish/documentation/authentication/index.html (added)
+++ mesos/site/publish/documentation/authentication/index.html Fri Aug 14 
06:03:28 2015
@@ -0,0 +1,168 @@
+<!DOCTYPE html>
+<html>
+    <head>
+        <meta charset="utf-8">
+        <title></title>
+                   <meta name="viewport" content="width=device-width, 
initial-scale=1.0">
+
+                   <link 
href="//netdna.bootstrapcdn.com/bootstrap/3.1.1/css/bootstrap.min.css" 
rel="stylesheet">
+                   <link rel="alternate" type="application/atom+xml" 
title="Apache Mesos Blog" href="/blog/feed.xml">
+                   
+                   <link href="../../assets/css/main.css" media="screen" 
rel="stylesheet" type="text/css" />
+                               
+                   
+                       
+                       <!-- Google Analytics Magic -->
+                       <script type="text/javascript">
+                         var _gaq = _gaq || [];
+                         _gaq.push(['_setAccount', 'UA-20226872-1']);
+                         _gaq.push(['_setDomainName', 'apache.org']);
+                         _gaq.push(['_trackPageview']);
+
+                         (function() {
+                           var ga = document.createElement('script'); ga.type 
= 'text/javascript'; ga.async = true;
+                           ga.src = ('https:' == document.location.protocol ? 
'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+                           var s = document.getElementsByTagName('script')[0]; 
s.parentNode.insertBefore(ga, s);
+                         })();
+                       </script>
+    </head>
+    <body>
+                       <!-- magical breadcrumbs -->
+                       <div class="topnav">
+                       <ul class="breadcrumb">
+                         <li>
+                                       <div class="dropdown">
+                                         <a data-toggle="dropdown" 
href="#">Apache Software Foundation <span class="caret"></span></a>
+                                         <ul class="dropdown-menu" role="menu" 
aria-labelledby="dLabel">
+                                                       <li><a 
href="http://www.apache.org";>Apache Homepage</a></li>
+                                                       <li><a 
href="http://www.apache.org/licenses/";>License</a></li>
+                                               <li><a 
href="http://www.apache.org/foundation/sponsorship.html";>Sponsorship</a></li>  
+                                               <li><a 
href="http://www.apache.org/foundation/thanks.html";>Thanks</a></li>
+                                                       <li><a 
href="http://www.apache.org/security/";>Security</a></li>
+                                         </ul>
+                                       </div>
+                               </li>
+                               <li><a href="http://mesos.apache.org";>Apache 
Mesos</a></li>
+                               
+                               
+                                       <li><a href="/documentation
+/">Documentation
+</a></li>
+                               
+                               
+                       </ul><!-- /breadcrumb -->
+                       </div>
+                       
+                       <!-- navbar excitement -->
+           <div class="navbar navbar-static-top" role="navigation">
+             <div class="navbar-inner">
+               <div class="container">
+                                               <a href="/" class="logo"><img 
src="/assets/img/mesos_logo.png" alt="Apache Mesos logo" /></a>
+                                       <div class="nav-collapse">
+                                               <ul class="nav nav-pills 
navbar-right">
+                                                 <li><a 
href="/gettingstarted/">Getting Started</a></li>
+                                                 <li><a 
href="/documentation/latest/">Documentation</a></li>
+                                                 <li><a 
href="/downloads/">Downloads</a></li>
+                                                 <li><a 
href="/community/">Community</a></li>
+                                               </ul>
+                                       </div>
+               </div>
+             </div>
+           </div><!-- /.navbar -->
+
+      <div class="container">
+
+                       <div class="row-fluid">
+       <div class="col-md-4">
+               <h4>If you're new to Mesos</h4>
+               <p>See the <a href="/gettingstarted/">getting started</a> page 
for more information about downloading, building, and deploying Mesos.</p>
+               
+               <h4>If you'd like to get involved or you're looking for 
support</h4>
+               <p>See our <a href="/community/">community</a> page for more 
details.</p>
+       </div>
+       <div class="col-md-8">
+               <h1>Authentication</h1>
+
+<p>Mesos 0.15.0 added support for framework authentication, and 0.19.0 added 
slave authentication.  Authentication permits only trusted entities to interact 
with the Mesos cluster.</p>
+
+<p>Authentication is used by Mesos in three ways:</p>
+
+<ol>
+<li>Require that frameworks must be authenticated in order to register with 
the master.</li>
+<li>Require that slaves must be authenticated in order to offer resources to 
the master.</li>
+<li>To restrict access to the /teardown endpoint.</li>
+</ol>
+
+
+<h2>How Does It Work?</h2>
+
+<p>Mesos uses the <a href="http://asg.web.cmu.edu/sasl/";>Cyrus SASL 
library</a> to implement authentication.  SASL is a very flexible 
authentication framework that allows two endpoints to authenticate with each 
other and also has support for various authentication mechanisms (ANONYMOUS, 
PLAIN, CRAM-MD5, GSSAPI etc).  Currently, Mesos provides support for CRAM-MD5 
authentication, but users can provide their own authentication modules.  
CRAM-MD5 makes use of a <strong>principal</strong> and <strong>secret</strong> 
pair, with the principal representing the framework&rsquo;s identity.  Note 
that this is different from the framework <em>user</em>, which is the account 
used by the executor to run tasks, and the <em>role</em> which is used to 
determine what resources frameworks can use.</p>
+
+<h2>Configuration</h2>
+
+<p>The <a 
href="http://mesos.apache.org/documentation/latest/configuration/";>configuration
 options</a> that are used by the authentication mechanism are as follows:</p>
+
+<h3>Masters</h3>
+
+<ul>
+<li>&ndash;[no-]authenticate - If authenticate is &lsquo;true&rsquo; only 
authenticated frameworks are allowed to register. If &lsquo;false&rsquo; 
unauthenticated frameworks are also allowed to register.</li>
+<li>&ndash;[no-]authenticate_slaves - If &lsquo;true&rsquo; only authenticated 
slaves are allowed to register. If &lsquo;false&rsquo; unauthenticated slaves 
are also allowed to register.</li>
+<li>&ndash;authenticators - Specifies which authenticator module to use.  The 
default is crammd5, but additional modules can be added with the &ndash;modules 
option.</li>
+<li>&ndash;credentials - The path to the text file which contains a list 
(either plain text or JSON) of accepted credentials.  This may be optional 
depending on the authenticator being used.  However, if specified, the 
credentials will be valid for the /teardown endpoint regardless of which 
authenticator is used.</li>
+</ul>
+
+
+<h3>Slaves</h3>
+
+<ul>
+<li>&ndash;authenticatee - Analog to the master &ndash;authenticators option 
to specify what module to use.  Defaults to crammd5.</li>
+<li>&ndash;credential - Just like the master &ndash;credentials option, except 
only one credential is allowed, since this credential is used to identify the 
slave to the master.</li>
+</ul>
+
+
+<h2>CRAM-MD5 Example</h2>
+
+<ol>
+<li><p>First, create a credentials file for the masters, the contents of which 
should look like this:</p>
+
+<pre><code> principal1 secret1
+ principal2 secret2
+</code></pre></li>
+<li><p>Now, start the master process using your credentials file (assuming the 
file is ~/credentials):</p>
+
+<pre><code> ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos 
--authenticate --authenticate_slaves --credentials=~/credentials
+</code></pre></li>
+<li><p>Now create another file with a single credential in it 
(~/slave_credential):</p>
+
+<pre><code> principal1 secret1
+</code></pre></li>
+<li><p>That file will be used to identify the slave process.  Start the 
slave:</p>
+
+<pre><code>./bin/mesos-slave.sh --master=127.0.0.1:5050 
--credential=~/slave_credential
+</code></pre></li>
+<li><p>Your new slave should have now successfully authenticated with the 
master.  With these settings, any framework that you&rsquo;d like to use must 
also authenticate against the Mesos master.  The method of configuring 
framework authentication may vary by framework, but is simple to implement as 
the scheduler driver will handle authentication when a Credential object is 
passed to its constructor.  You can test out framework authentication using the 
test framework provided with Mesos as follows:</p>
+
+<pre><code>MESOS_AUTHENTICATE=true DEFAULT_PRINCIPAL=principal2 
DEFAULT_SECRET=secret2 ./src/test-framework --master=127.0.0.1:5050
+</code></pre></li>
+</ol>
+
+
+       </div>
+</div>
+
+                       
+             <hr>
+
+                               <!-- footer -->
+             <div class="footer">
+               <p>&copy; 2012-2015 <a href="http://apache.org";>The Apache 
Software Foundation</a>.
+               Apache Mesos, the Apache feather logo, and the Apache Mesos 
project logo are trademarks of The Apache Software Foundation.<p>
+             </div><!-- /footer -->
+
+           </div> <!-- /container -->
+
+           <!-- JS -->
+           <script src="//code.jquery.com/jquery-1.11.0.min.js" 
type="text/javascript"></script>
+                       <script 
src="//netdna.bootstrapcdn.com/bootstrap/3.1.1/js/bootstrap.min.js" 
type="text/javascript"></script>
+    </body>
+</html>

Modified: mesos/site/publish/documentation/clang-format/index.html
URL: 
http://svn.apache.org/viewvc/mesos/site/publish/documentation/clang-format/index.html?rev=1695820&r1=1695819&r2=1695820&view=diff
==============================================================================
--- mesos/site/publish/documentation/clang-format/index.html (original)
+++ mesos/site/publish/documentation/clang-format/index.html Fri Aug 14 
06:03:28 2015
@@ -170,11 +170,7 @@ imap &lt;C-K&gt; &lt;c-o&gt;:pyf /usr/lo
 <h2>Known Limitations</h2>
 
 <ul>
-<li>The braces after <code>namespace</code>s should not be wrapped.</li>
-<li>The braces after <code>struct</code>s and <code>union</code>s should be 
wrapped.</li>
 <li>Parameters and arguments should be indented by 4 spaces rather than 2.</li>
-<li>Overloaded operators should be padded with spaces.
-(e.g. <code>Foo operator + (...);</code>)</li>
 <li>Should not follow Google&rsquo;s style of wrapping on open parentheses, we 
should
 try to reduce &ldquo;jaggedness&rdquo; in the code.</li>
 </ul>

Modified: mesos/site/publish/documentation/configuration/index.html
URL: 
http://svn.apache.org/viewvc/mesos/site/publish/documentation/configuration/index.html?rev=1695820&r1=1695819&r2=1695820&view=diff
==============================================================================
--- mesos/site/publish/documentation/configuration/index.html (original)
+++ mesos/site/publish/documentation/configuration/index.html Fri Aug 14 
06:03:28 2015
@@ -253,6 +253,25 @@
         Explanation
       </th>
   </thead>
+   <tr>
+     <td>
+      --advertise_ip=VALUE
+    </td>
+    <td>
+      IP address advertised to reach mesos master. Mesos master does not bind 
using this
+      IP address. However, this IP address may be used to access Mesos master.
+    </td>
+  </tr>
+  <tr>
+    <td>
+      --advertise_port=VALUE
+    </td>
+    <td>
+      Port advertised to reach mesos master (alongwith advertise_ip). Mesos 
master does not
+      bind using this port. However, this port (alongwith advertise_ip) may be 
used to
+      access Mesos master.
+    </td>
+  </tr>
   <tr>
     <td>
       --quorum=VALUE
@@ -390,6 +409,23 @@ file:///path/to/file (where file contain
     </td>
   </tr>
   <tr>
+    <td>
+      --authorizers=VALUE
+    </td>
+    <td>
+      Authorizer implementation to use when authorizating actions that
+      required it. Use the default <code>local</code>, or load an alternate
+      authorizer module using <code>--modules</code>.
+      <br/>
+      Note that if the flag <code>--authorizers</code> is provided with a
+      value different than the default <code>local</code>, the ACLs passed
+      through the <code>--acls</code> flag will be ignored.
+      <br/>
+      Currently there's no support for multiple authorizers.<br/>
+      (default: <code>local</code>)
+    </td>
+  </tr>
+  <tr>
     <td>
       --cluster=VALUE
     </td>

Added: mesos/site/publish/documentation/latest/authentication/index.html
URL: 
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/authentication/index.html?rev=1695820&view=auto
==============================================================================
--- mesos/site/publish/documentation/latest/authentication/index.html (added)
+++ mesos/site/publish/documentation/latest/authentication/index.html Fri Aug 
14 06:03:28 2015
@@ -0,0 +1,168 @@
+<!DOCTYPE html>
+<html>
+    <head>
+        <meta charset="utf-8">
+        <title></title>
+                   <meta name="viewport" content="width=device-width, 
initial-scale=1.0">
+
+                   <link 
href="//netdna.bootstrapcdn.com/bootstrap/3.1.1/css/bootstrap.min.css" 
rel="stylesheet">
+                   <link rel="alternate" type="application/atom+xml" 
title="Apache Mesos Blog" href="/blog/feed.xml">
+                   
+                   <link href="../../../assets/css/main.css" media="screen" 
rel="stylesheet" type="text/css" />
+                               
+                   
+                       
+                       <!-- Google Analytics Magic -->
+                       <script type="text/javascript">
+                         var _gaq = _gaq || [];
+                         _gaq.push(['_setAccount', 'UA-20226872-1']);
+                         _gaq.push(['_setDomainName', 'apache.org']);
+                         _gaq.push(['_trackPageview']);
+
+                         (function() {
+                           var ga = document.createElement('script'); ga.type 
= 'text/javascript'; ga.async = true;
+                           ga.src = ('https:' == document.location.protocol ? 
'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+                           var s = document.getElementsByTagName('script')[0]; 
s.parentNode.insertBefore(ga, s);
+                         })();
+                       </script>
+    </head>
+    <body>
+                       <!-- magical breadcrumbs -->
+                       <div class="topnav">
+                       <ul class="breadcrumb">
+                         <li>
+                                       <div class="dropdown">
+                                         <a data-toggle="dropdown" 
href="#">Apache Software Foundation <span class="caret"></span></a>
+                                         <ul class="dropdown-menu" role="menu" 
aria-labelledby="dLabel">
+                                                       <li><a 
href="http://www.apache.org";>Apache Homepage</a></li>
+                                                       <li><a 
href="http://www.apache.org/licenses/";>License</a></li>
+                                               <li><a 
href="http://www.apache.org/foundation/sponsorship.html";>Sponsorship</a></li>  
+                                               <li><a 
href="http://www.apache.org/foundation/thanks.html";>Thanks</a></li>
+                                                       <li><a 
href="http://www.apache.org/security/";>Security</a></li>
+                                         </ul>
+                                       </div>
+                               </li>
+                               <li><a href="http://mesos.apache.org";>Apache 
Mesos</a></li>
+                               
+                               
+                                       <li><a href="/documentation
+/">Documentation
+</a></li>
+                               
+                               
+                       </ul><!-- /breadcrumb -->
+                       </div>
+                       
+                       <!-- navbar excitement -->
+           <div class="navbar navbar-static-top" role="navigation">
+             <div class="navbar-inner">
+               <div class="container">
+                                               <a href="/" class="logo"><img 
src="/assets/img/mesos_logo.png" alt="Apache Mesos logo" /></a>
+                                       <div class="nav-collapse">
+                                               <ul class="nav nav-pills 
navbar-right">
+                                                 <li><a 
href="/gettingstarted/">Getting Started</a></li>
+                                                 <li><a 
href="/documentation/latest/">Documentation</a></li>
+                                                 <li><a 
href="/downloads/">Downloads</a></li>
+                                                 <li><a 
href="/community/">Community</a></li>
+                                               </ul>
+                                       </div>
+               </div>
+             </div>
+           </div><!-- /.navbar -->
+
+      <div class="container">
+
+                       <div class="row-fluid">
+       <div class="col-md-4">
+               <h4>If you're new to Mesos</h4>
+               <p>See the <a href="/gettingstarted/">getting started</a> page 
for more information about downloading, building, and deploying Mesos.</p>
+               
+               <h4>If you'd like to get involved or you're looking for 
support</h4>
+               <p>See our <a href="/community/">community</a> page for more 
details.</p>
+       </div>
+       <div class="col-md-8">
+               <h1>Authentication</h1>
+
+<p>Mesos 0.15.0 added support for framework authentication, and 0.19.0 added 
slave authentication.  Authentication permits only trusted entities to interact 
with the Mesos cluster.</p>
+
+<p>Authentication is used by Mesos in three ways:</p>
+
+<ol>
+<li>Require that frameworks must be authenticated in order to register with 
the master.</li>
+<li>Require that slaves must be authenticated in order to offer resources to 
the master.</li>
+<li>To restrict access to the /teardown endpoint.</li>
+</ol>
+
+
+<h2>How Does It Work?</h2>
+
+<p>Mesos uses the <a href="http://asg.web.cmu.edu/sasl/";>Cyrus SASL 
library</a> to implement authentication.  SASL is a very flexible 
authentication framework that allows two endpoints to authenticate with each 
other and also has support for various authentication mechanisms (ANONYMOUS, 
PLAIN, CRAM-MD5, GSSAPI etc).  Currently, Mesos provides support for CRAM-MD5 
authentication, but users can provide their own authentication modules.  
CRAM-MD5 makes use of a <strong>principal</strong> and <strong>secret</strong> 
pair, with the principal representing the framework&rsquo;s identity.  Note 
that this is different from the framework <em>user</em>, which is the account 
used by the executor to run tasks, and the <em>role</em> which is used to 
determine what resources frameworks can use.</p>
+
+<h2>Configuration</h2>
+
+<p>The <a 
href="http://mesos.apache.org/documentation/latest/configuration/";>configuration
 options</a> that are used by the authentication mechanism are as follows:</p>
+
+<h3>Masters</h3>
+
+<ul>
+<li>&ndash;[no-]authenticate - If authenticate is &lsquo;true&rsquo; only 
authenticated frameworks are allowed to register. If &lsquo;false&rsquo; 
unauthenticated frameworks are also allowed to register.</li>
+<li>&ndash;[no-]authenticate_slaves - If &lsquo;true&rsquo; only authenticated 
slaves are allowed to register. If &lsquo;false&rsquo; unauthenticated slaves 
are also allowed to register.</li>
+<li>&ndash;authenticators - Specifies which authenticator module to use.  The 
default is crammd5, but additional modules can be added with the &ndash;modules 
option.</li>
+<li>&ndash;credentials - The path to the text file which contains a list 
(either plain text or JSON) of accepted credentials.  This may be optional 
depending on the authenticator being used.  However, if specified, the 
credentials will be valid for the /teardown endpoint regardless of which 
authenticator is used.</li>
+</ul>
+
+
+<h3>Slaves</h3>
+
+<ul>
+<li>&ndash;authenticatee - Analog to the master &ndash;authenticators option 
to specify what module to use.  Defaults to crammd5.</li>
+<li>&ndash;credential - Just like the master &ndash;credentials option, except 
only one credential is allowed, since this credential is used to identify the 
slave to the master.</li>
+</ul>
+
+
+<h2>CRAM-MD5 Example</h2>
+
+<ol>
+<li><p>First, create a credentials file for the masters, the contents of which 
should look like this:</p>
+
+<pre><code> principal1 secret1
+ principal2 secret2
+</code></pre></li>
+<li><p>Now, start the master process using your credentials file (assuming the 
file is ~/credentials):</p>
+
+<pre><code> ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos 
--authenticate --authenticate_slaves --credentials=~/credentials
+</code></pre></li>
+<li><p>Now create another file with a single credential in it 
(~/slave_credential):</p>
+
+<pre><code> principal1 secret1
+</code></pre></li>
+<li><p>That file will be used to identify the slave process.  Start the 
slave:</p>
+
+<pre><code>./bin/mesos-slave.sh --master=127.0.0.1:5050 
--credential=~/slave_credential
+</code></pre></li>
+<li><p>Your new slave should have now successfully authenticated with the 
master.  With these settings, any framework that you&rsquo;d like to use must 
also authenticate against the Mesos master.  The method of configuring 
framework authentication may vary by framework, but is simple to implement as 
the scheduler driver will handle authentication when a Credential object is 
passed to its constructor.  You can test out framework authentication using the 
test framework provided with Mesos as follows:</p>
+
+<pre><code>MESOS_AUTHENTICATE=true DEFAULT_PRINCIPAL=principal2 
DEFAULT_SECRET=secret2 ./src/test-framework --master=127.0.0.1:5050
+</code></pre></li>
+</ol>
+
+
+       </div>
+</div>
+
+                       
+             <hr>
+
+                               <!-- footer -->
+             <div class="footer">
+               <p>&copy; 2012-2015 <a href="http://apache.org";>The Apache 
Software Foundation</a>.
+               Apache Mesos, the Apache feather logo, and the Apache Mesos 
project logo are trademarks of The Apache Software Foundation.<p>
+             </div><!-- /footer -->
+
+           </div> <!-- /container -->
+
+           <!-- JS -->
+           <script src="//code.jquery.com/jquery-1.11.0.min.js" 
type="text/javascript"></script>
+                       <script 
src="//netdna.bootstrapcdn.com/bootstrap/3.1.1/js/bootstrap.min.js" 
type="text/javascript"></script>
+    </body>
+</html>

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=1695820&r1=1695819&r2=1695820&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/clang-format/index.html (original)
+++ mesos/site/publish/documentation/latest/clang-format/index.html Fri Aug 14 
06:03:28 2015
@@ -170,11 +170,7 @@ imap &lt;C-K&gt; &lt;c-o&gt;:pyf /usr/lo
 <h2>Known Limitations</h2>
 
 <ul>
-<li>The braces after <code>namespace</code>s should not be wrapped.</li>
-<li>The braces after <code>struct</code>s and <code>union</code>s should be 
wrapped.</li>
 <li>Parameters and arguments should be indented by 4 spaces rather than 2.</li>
-<li>Overloaded operators should be padded with spaces.
-(e.g. <code>Foo operator + (...);</code>)</li>
 <li>Should not follow Google&rsquo;s style of wrapping on open parentheses, we 
should
 try to reduce &ldquo;jaggedness&rdquo; in the code.</li>
 </ul>

Modified: mesos/site/publish/documentation/latest/configuration/index.html
URL: 
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/configuration/index.html?rev=1695820&r1=1695819&r2=1695820&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/configuration/index.html (original)
+++ mesos/site/publish/documentation/latest/configuration/index.html Fri Aug 14 
06:03:28 2015
@@ -253,6 +253,25 @@
         Explanation
       </th>
   </thead>
+   <tr>
+     <td>
+      --advertise_ip=VALUE
+    </td>
+    <td>
+      IP address advertised to reach mesos master. Mesos master does not bind 
using this
+      IP address. However, this IP address may be used to access Mesos master.
+    </td>
+  </tr>
+  <tr>
+    <td>
+      --advertise_port=VALUE
+    </td>
+    <td>
+      Port advertised to reach mesos master (alongwith advertise_ip). Mesos 
master does not
+      bind using this port. However, this port (alongwith advertise_ip) may be 
used to
+      access Mesos master.
+    </td>
+  </tr>
   <tr>
     <td>
       --quorum=VALUE
@@ -390,6 +409,23 @@ file:///path/to/file (where file contain
     </td>
   </tr>
   <tr>
+    <td>
+      --authorizers=VALUE
+    </td>
+    <td>
+      Authorizer implementation to use when authorizating actions that
+      required it. Use the default <code>local</code>, or load an alternate
+      authorizer module using <code>--modules</code>.
+      <br/>
+      Note that if the flag <code>--authorizers</code> is provided with a
+      value different than the default <code>local</code>, the ACLs passed
+      through the <code>--acls</code> flag will be ignored.
+      <br/>
+      Currently there's no support for multiple authorizers.<br/>
+      (default: <code>local</code>)
+    </td>
+  </tr>
+  <tr>
     <td>
       --cluster=VALUE
     </td>

Modified: 
mesos/site/publish/documentation/latest/mesos-c++-style-guide/index.html
URL: 
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/mesos-c%2B%2B-style-guide/index.html?rev=1695820&r1=1695819&r2=1695820&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/mesos-c++-style-guide/index.html 
(original)
+++ mesos/site/publish/documentation/latest/mesos-c++-style-guide/index.html 
Fri Aug 14 06:03:28 2015
@@ -126,7 +126,6 @@ void Slave::statusUpdate(StatusUpdate up
 
 <ul>
 <li>We use <a 
href="http://en.wikipedia.org/wiki/CamelCase#Variations_and_synonyms";>lowerCamelCase</a>
 for function names (Google uses mixed case for regular functions; and their 
accessors and mutators match the name of the variable).</li>
-<li>Leave spaces around overloaded operators, e.g. <code>operator + 
(...);</code> rather than <code>operator+(...);</code></li>
 </ul>
 
 
@@ -156,7 +155,7 @@ void Slave::statusUpdate(StatusUpdate up
 <h2>Breaks</h2>
 
 <ul>
-<li>Break before braces on function, class, struct and union definitions. 
(Google attaches braces to the surrounding context)</li>
+<li>Break before braces on enum, function, and record (i.e. struct, class, 
union) definitions.</li>
 </ul>
 
 
@@ -696,43 +695,44 @@ auto lambda = [
 
 <p><code>constexpr</code> behaves as a combination of <code>inline</code> and 
<code>const</code> and hence must be defined before use in another 
<code>constexpr</code>.</p>
 
-<p>Prefer <code>constexpr to</code>const<code>for all constant POD 
declarations,</code>constexpr<code></code>char<code>arrays are preferred 
to</code>const<code></code>string` literals.
-```
-// OK
-constexpr char LITERAL[] = &ldquo;value&rdquo;;</p>
-
-<p>// Not OK - not available at compile time for optimization and
-// definition required in a separate compilation module.
-const char LITERAL[];</p>
-
-<p>// Not OK - uncertain initialization order, cannot be used in other
-// constexpr statements.
-const string LITERAL(&ldquo;value&rdquo;);</p>
-
-<pre><code>`constexpr` functions are evaluated at compile time if all their 
arguments are constant expressions. Otherwise they default to initialization at 
runtime. However `constexpr` functions are limited in that they cannot perform 
dynamic casts, memory allocation or calls to non-constexpr functions.  Prefer 
`constexpr` over const inline functions.
-</code></pre>
-
-<p>constexpr size_t MIN = 200;
-constexpr size_t MAX = 1000;
-constexpr size_t SPAN() { return MAX-MIN; }
-int array[SPAN()];
-<code>
-Const expression constructors allow object initialization at compile time 
provided that all the constructor arguments are constexpr and the constuctor 
body is empty, i.e. all initialization is performed in the initialization list. 
 Classes which provide constexpr constructors should normally also provide 
constexpr copy constructors to allow the class to be used in the return value 
from a constexpr function.
-</code>
-class C
-{
-public:
-  constexpr C(int <em>i) : i(</em>i) {};
-  constexpr C(const C&amp; c) : i(c.i) {}
-private:
-  const int i;
-};</p>
-
-<p>```
-C++11 does not provide constexpr string or containers in the STL and hence 
constexpr cannot be used for any class using stout&rsquo;s Error() 
class.</p></li>
+<p>Prefer <code>constexpr</code> to <code>const</code> for all constant POD 
declarations, <code>constexpr</code> <code>char</code> arrays are preferred to 
<code>const</code> <code>string</code> literals.</p></li>
 </ul>
 
 
+<pre><code class="{.cpp}">  // OK
+  constexpr char LITERAL[] = "value";
+
+  // Not OK - not available at compile time for optimization and
+  // definition required in a separate compilation module.
+  const char LITERAL[];
+
+  // Not OK - uncertain initialization order, cannot be used in other
+  // constexpr statements.
+  const string LITERAL("value");
+</code></pre>
+
+<p>  <code>constexpr</code> functions are evaluated at compile time if all 
their arguments are constant expressions. Otherwise they default to 
initialization at runtime. However <code>constexpr</code> functions are limited 
in that they cannot perform dynamic casts, memory allocation or calls to 
non-constexpr functions.  Prefer <code>constexpr</code> over const inline 
functions.</p>
+
+<pre><code class="{.cpp}">  constexpr size_t MIN = 200;
+  constexpr size_t MAX = 1000;
+  constexpr size_t SPAN() { return MAX-MIN; }
+  int array[SPAN()];
+</code></pre>
+
+<p>Const expression constructors allow object initialization at compile time 
provided that all the constructor arguments are <code>constexpr</code> and the 
constuctor body is empty, i.e. all initialization is performed in the 
initialization list.  Classes which provide <code>constexpr</code> constructors 
should normally also provide <code>constexpr</code> copy constructors to allow 
the class to be used in the return value from a <code>constexpr</code> 
function.</p>
+
+<pre><code class="{.cpp}">  class C
+  {
+  public:
+    constexpr C(int _i) : i(_i) {};
+    constexpr C(const C&amp; c) : i(c.i) {}
+  private:
+    const int i;
+  };
+</code></pre>
+
+<p>  C++11 does not provide <code>constexpr string</code> or 
<code>constexpr</code> containers in the STL and hence <code>constexpr</code> 
cannot be used for any class using stout&rsquo;s Error() class.</p>
+
        </div>
 </div>
 

Modified: mesos/site/publish/documentation/latest/operational-guide/index.html
URL: 
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/operational-guide/index.html?rev=1695820&r1=1695819&r2=1695820&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/operational-guide/index.html 
(original)
+++ mesos/site/publish/documentation/latest/operational-guide/index.html Fri 
Aug 14 06:03:28 2015
@@ -178,6 +178,10 @@ information, quota information, etc). To
 
 <p>Please see the NOTE section above. So long as the failed master is 
guaranteed to not re-join the ensemble, it is safe to start a new master 
<em>with an empty log</em> and allow it to catch up.</p>
 
+<h2>External access for mesos master</h2>
+
+<p>If the default ip (or the command line arg <code>--ip</code>) points to an 
internal IP, then external entities such as framework scheduler would not be 
able to reach the master. To address that scenario, an externally accessible 
IP:port can be setup via the <code>--advertise_ip</code> and 
<code>--advertise_port</code> command line arguments of mesos master. If 
configured, external entities such as framework scheduler interact with the 
advertise_ip:advertise_port from where the request needs to be proxied to the 
internal IP:Port on which mesos master is listening.</p>
+
        </div>
 </div>
 

Modified: mesos/site/publish/documentation/latest/powered-by-mesos/index.html
URL: 
http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/powered-by-mesos/index.html?rev=1695820&r1=1695819&r2=1695820&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/powered-by-mesos/index.html 
(original)
+++ mesos/site/publish/documentation/latest/powered-by-mesos/index.html Fri Aug 
14 06:03:28 2015
@@ -98,6 +98,7 @@
 <li><a href="http://www.brandingbrand.com";>Branding Brand</a></li>
 <li><a href="http://www.brigade.com";>Brigade</a></li>
 <li><a href="http://categorize.co";>Categorize</a></li>
+<li><a href="http://cern.ch";>CERN</a></li>
 <li><a href="http://www.cisco.com";>Cisco</a></li>
 <li><a href="http://cloudphysics.com";>CloudPhysics</a></li>
 <li><a href="http://www.conviva.com";>Conviva</a></li>
@@ -119,6 +120,7 @@
 <li><a href="http://www.iqiyi.com/";>iQIYI</a></li>
 <li><a href="http://www.learnium.net/";>Learnium</a></li>
 <li><a href="http://lifx.co";>LIFX</a></li>
+<li><a href="http://www.linkernetworks.com";>Linkernetworks</a></li>
 <li><a href="http://www.localsensor.com";>Localsensor</a></li>
 <li><a href="https://magine.com";>Magine TV</a></li>
 <li><a href="http://www.medallia.com";>Medallia</a></li>
@@ -162,6 +164,7 @@
 <li><a href="http://www.yelp.com";>Yelp</a></li>
 <li><a href="http://www.yieldbot.com";>Yieldbot</a></li>
 <li><a href="http://www.yodle.com";>Yodle</a></li>
+<li><a href="http://www.xiaomi.com";>Xiaomi</a></li>
 <li><a href="http://www.xogito.com";>Xogito</a></li>
 </ul>
 

Modified: mesos/site/publish/documentation/mesos-c++-style-guide/index.html
URL: 
http://svn.apache.org/viewvc/mesos/site/publish/documentation/mesos-c%2B%2B-style-guide/index.html?rev=1695820&r1=1695819&r2=1695820&view=diff
==============================================================================
--- mesos/site/publish/documentation/mesos-c++-style-guide/index.html (original)
+++ mesos/site/publish/documentation/mesos-c++-style-guide/index.html Fri Aug 
14 06:03:28 2015
@@ -126,7 +126,6 @@ void Slave::statusUpdate(StatusUpdate up
 
 <ul>
 <li>We use <a 
href="http://en.wikipedia.org/wiki/CamelCase#Variations_and_synonyms";>lowerCamelCase</a>
 for function names (Google uses mixed case for regular functions; and their 
accessors and mutators match the name of the variable).</li>
-<li>Leave spaces around overloaded operators, e.g. <code>operator + 
(...);</code> rather than <code>operator+(...);</code></li>
 </ul>
 
 
@@ -156,7 +155,7 @@ void Slave::statusUpdate(StatusUpdate up
 <h2>Breaks</h2>
 
 <ul>
-<li>Break before braces on function, class, struct and union definitions. 
(Google attaches braces to the surrounding context)</li>
+<li>Break before braces on enum, function, and record (i.e. struct, class, 
union) definitions.</li>
 </ul>
 
 
@@ -696,43 +695,44 @@ auto lambda = [
 
 <p><code>constexpr</code> behaves as a combination of <code>inline</code> and 
<code>const</code> and hence must be defined before use in another 
<code>constexpr</code>.</p>
 
-<p>Prefer <code>constexpr to</code>const<code>for all constant POD 
declarations,</code>constexpr<code></code>char<code>arrays are preferred 
to</code>const<code></code>string` literals.
-```
-// OK
-constexpr char LITERAL[] = &ldquo;value&rdquo;;</p>
-
-<p>// Not OK - not available at compile time for optimization and
-// definition required in a separate compilation module.
-const char LITERAL[];</p>
-
-<p>// Not OK - uncertain initialization order, cannot be used in other
-// constexpr statements.
-const string LITERAL(&ldquo;value&rdquo;);</p>
-
-<pre><code>`constexpr` functions are evaluated at compile time if all their 
arguments are constant expressions. Otherwise they default to initialization at 
runtime. However `constexpr` functions are limited in that they cannot perform 
dynamic casts, memory allocation or calls to non-constexpr functions.  Prefer 
`constexpr` over const inline functions.
-</code></pre>
-
-<p>constexpr size_t MIN = 200;
-constexpr size_t MAX = 1000;
-constexpr size_t SPAN() { return MAX-MIN; }
-int array[SPAN()];
-<code>
-Const expression constructors allow object initialization at compile time 
provided that all the constructor arguments are constexpr and the constuctor 
body is empty, i.e. all initialization is performed in the initialization list. 
 Classes which provide constexpr constructors should normally also provide 
constexpr copy constructors to allow the class to be used in the return value 
from a constexpr function.
-</code>
-class C
-{
-public:
-  constexpr C(int <em>i) : i(</em>i) {};
-  constexpr C(const C&amp; c) : i(c.i) {}
-private:
-  const int i;
-};</p>
-
-<p>```
-C++11 does not provide constexpr string or containers in the STL and hence 
constexpr cannot be used for any class using stout&rsquo;s Error() 
class.</p></li>
+<p>Prefer <code>constexpr</code> to <code>const</code> for all constant POD 
declarations, <code>constexpr</code> <code>char</code> arrays are preferred to 
<code>const</code> <code>string</code> literals.</p></li>
 </ul>
 
 
+<pre><code class="{.cpp}">  // OK
+  constexpr char LITERAL[] = "value";
+
+  // Not OK - not available at compile time for optimization and
+  // definition required in a separate compilation module.
+  const char LITERAL[];
+
+  // Not OK - uncertain initialization order, cannot be used in other
+  // constexpr statements.
+  const string LITERAL("value");
+</code></pre>
+
+<p>  <code>constexpr</code> functions are evaluated at compile time if all 
their arguments are constant expressions. Otherwise they default to 
initialization at runtime. However <code>constexpr</code> functions are limited 
in that they cannot perform dynamic casts, memory allocation or calls to 
non-constexpr functions.  Prefer <code>constexpr</code> over const inline 
functions.</p>
+
+<pre><code class="{.cpp}">  constexpr size_t MIN = 200;
+  constexpr size_t MAX = 1000;
+  constexpr size_t SPAN() { return MAX-MIN; }
+  int array[SPAN()];
+</code></pre>
+
+<p>Const expression constructors allow object initialization at compile time 
provided that all the constructor arguments are <code>constexpr</code> and the 
constuctor body is empty, i.e. all initialization is performed in the 
initialization list.  Classes which provide <code>constexpr</code> constructors 
should normally also provide <code>constexpr</code> copy constructors to allow 
the class to be used in the return value from a <code>constexpr</code> 
function.</p>
+
+<pre><code class="{.cpp}">  class C
+  {
+  public:
+    constexpr C(int _i) : i(_i) {};
+    constexpr C(const C&amp; c) : i(c.i) {}
+  private:
+    const int i;
+  };
+</code></pre>
+
+<p>  C++11 does not provide <code>constexpr string</code> or 
<code>constexpr</code> containers in the STL and hence <code>constexpr</code> 
cannot be used for any class using stout&rsquo;s Error() class.</p>
+
        </div>
 </div>
 

Modified: mesos/site/publish/documentation/operational-guide/index.html
URL: 
http://svn.apache.org/viewvc/mesos/site/publish/documentation/operational-guide/index.html?rev=1695820&r1=1695819&r2=1695820&view=diff
==============================================================================
--- mesos/site/publish/documentation/operational-guide/index.html (original)
+++ mesos/site/publish/documentation/operational-guide/index.html Fri Aug 14 
06:03:28 2015
@@ -178,6 +178,10 @@ information, quota information, etc). To
 
 <p>Please see the NOTE section above. So long as the failed master is 
guaranteed to not re-join the ensemble, it is safe to start a new master 
<em>with an empty log</em> and allow it to catch up.</p>
 
+<h2>External access for mesos master</h2>
+
+<p>If the default ip (or the command line arg <code>--ip</code>) points to an 
internal IP, then external entities such as framework scheduler would not be 
able to reach the master. To address that scenario, an externally accessible 
IP:port can be setup via the <code>--advertise_ip</code> and 
<code>--advertise_port</code> command line arguments of mesos master. If 
configured, external entities such as framework scheduler interact with the 
advertise_ip:advertise_port from where the request needs to be proxied to the 
internal IP:Port on which mesos master is listening.</p>
+
        </div>
 </div>
 

Modified: mesos/site/publish/documentation/powered-by-mesos/index.html
URL: 
http://svn.apache.org/viewvc/mesos/site/publish/documentation/powered-by-mesos/index.html?rev=1695820&r1=1695819&r2=1695820&view=diff
==============================================================================
--- mesos/site/publish/documentation/powered-by-mesos/index.html (original)
+++ mesos/site/publish/documentation/powered-by-mesos/index.html Fri Aug 14 
06:03:28 2015
@@ -98,6 +98,7 @@
 <li><a href="http://www.brandingbrand.com";>Branding Brand</a></li>
 <li><a href="http://www.brigade.com";>Brigade</a></li>
 <li><a href="http://categorize.co";>Categorize</a></li>
+<li><a href="http://cern.ch";>CERN</a></li>
 <li><a href="http://www.cisco.com";>Cisco</a></li>
 <li><a href="http://cloudphysics.com";>CloudPhysics</a></li>
 <li><a href="http://www.conviva.com";>Conviva</a></li>
@@ -119,6 +120,7 @@
 <li><a href="http://www.iqiyi.com/";>iQIYI</a></li>
 <li><a href="http://www.learnium.net/";>Learnium</a></li>
 <li><a href="http://lifx.co";>LIFX</a></li>
+<li><a href="http://www.linkernetworks.com";>Linkernetworks</a></li>
 <li><a href="http://www.localsensor.com";>Localsensor</a></li>
 <li><a href="https://magine.com";>Magine TV</a></li>
 <li><a href="http://www.medallia.com";>Medallia</a></li>
@@ -162,6 +164,7 @@
 <li><a href="http://www.yelp.com";>Yelp</a></li>
 <li><a href="http://www.yieldbot.com";>Yieldbot</a></li>
 <li><a href="http://www.yodle.com";>Yodle</a></li>
+<li><a href="http://www.xiaomi.com";>Xiaomi</a></li>
 <li><a href="http://www.xogito.com";>Xogito</a></li>
 </ul>
 


Reply via email to