Updated the website built from mesos SHA: 3dc93d6.

Project: http://git-wip-us.apache.org/repos/asf/mesos-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos-site/commit/5682363e
Tree: http://git-wip-us.apache.org/repos/asf/mesos-site/tree/5682363e
Diff: http://git-wip-us.apache.org/repos/asf/mesos-site/diff/5682363e

Branch: refs/heads/asf-site
Commit: 5682363ea36543018d05978e05d484d83f4a9d97
Parents: 4721f41
Author: jenkins <[email protected]>
Authored: Tue Dec 12 00:18:36 2017 +0000
Committer: jenkins <[email protected]>
Committed: Tue Dec 12 00:18:36 2017 +0000

----------------------------------------------------------------------
 content/blog/feed.xml                           |    2 +-
 .../index.html                                  |    2 +-
 content/documentation/cmake-examples/index.html |   51 -
 .../latest/cmake-examples/index.html            |   51 -
 content/documentation/latest/windows/index.html |   82 +-
 content/documentation/windows/index.html        |   82 +-
 content/sitemap.xml                             | 8918 +++++++++---------
 7 files changed, 4603 insertions(+), 4585 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/mesos-site/blob/5682363e/content/blog/feed.xml
----------------------------------------------------------------------
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index 528ce67..ea200a2 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -117,7 +117,7 @@
 &lt;/ul&gt;
 
 
-&lt;p&gt;If you are a user and would like to suggest some areas for 
performance improvement, please let us know by emailing &lt;a 
href=&quot;&amp;#x6d;&amp;#x61;&amp;#x69;&amp;#x6c;&amp;#x74;&amp;#x6f;&amp;#x3a;&amp;#100;&amp;#101;&amp;#118;&amp;#64;&amp;#97;&amp;#112;&amp;#x61;&amp;#x63;&amp;#x68;&amp;#101;&amp;#46;&amp;#x6d;&amp;#101;&amp;#x73;&amp;#111;&amp;#x73;&amp;#x2e;&amp;#111;&amp;#114;&amp;#103;&quot;&gt;&amp;#x64;&amp;#101;&amp;#x76;&amp;#64;&amp;#x61;&amp;#112;&amp;#97;&amp;#x63;&amp;#x68;&amp;#x65;&amp;#46;&amp;#x6d;&amp;#x65;&amp;#115;&amp;#x6f;&amp;#x73;&amp;#46;&amp;#111;&amp;#114;&amp;#x67;&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;If you are a user and would like to suggest some areas for 
performance improvement, please let us know by emailing &lt;a 
href=&quot;&amp;#109;&amp;#97;&amp;#105;&amp;#x6c;&amp;#116;&amp;#x6f;&amp;#x3a;&amp;#x64;&amp;#x65;&amp;#x76;&amp;#x40;&amp;#x61;&amp;#x70;&amp;#x61;&amp;#99;&amp;#x68;&amp;#x65;&amp;#x2e;&amp;#109;&amp;#x65;&amp;#x73;&amp;#x6f;&amp;#x73;&amp;#46;&amp;#111;&amp;#x72;&amp;#x67;&quot;&gt;&amp;#100;&amp;#x65;&amp;#118;&amp;#x40;&amp;#x61;&amp;#112;&amp;#x61;&amp;#99;&amp;#104;&amp;#101;&amp;#x2e;&amp;#x6d;&amp;#101;&amp;#115;&amp;#x6f;&amp;#x73;&amp;#46;&amp;#111;&amp;#x72;&amp;#x67;&lt;/a&gt;.&lt;/p&gt;
 
        </content>
   </entry>

http://git-wip-us.apache.org/repos/asf/mesos-site/blob/5682363e/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 fdd8672..94864b1 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="&#x6d;&#x61;&#x69;&#x6c;&#x74;&#x6f;&#x3a;&#100;&#101;&#118;&#64;&#97;&#112;&#x61;&#x63;&#x68;&#101;&#46;&#x6d;&#101;&#x73;&#111;&#x73;&#x2e;&#111;&#114;&#103;">&#x64;&#101;&#x76;&#64;&#x61;&#112;&#97;&#x63;&#x68;&#x65;&#46;&#x6d;&#x65;&#115;&#x6f;&#x73;&#46;&#111;&#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;&#105;&#x6c;&#116;&#x6f;&#x3a;&#x64;&#x65;&#x76;&#x40;&#x61;&#x70;&#x61;&#99;&#x68;&#x65;&#x2e;&#109;&#x65;&#x73;&#x6f;&#x73;&#46;&#111;&#x72;&#x67;">&#100;&#x65;&#118;&#x40;&#x61;&#112;&#x61;&#99;&#104;&#101;&#x2e;&#x6d;&#101;&#115;&#x6f;&#x73;&#46;&#111;&#x72;&#x67;</a>.</p>
 
   </div>
 </div>

http://git-wip-us.apache.org/repos/asf/mesos-site/blob/5682363e/content/documentation/cmake-examples/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/cmake-examples/index.html 
b/content/documentation/cmake-examples/index.html
index 7e865b2..d51e8b3 100644
--- a/content/documentation/cmake-examples/index.html
+++ b/content/documentation/cmake-examples/index.html
@@ -451,57 +451,6 @@ libraries by default.</p>
 Windows is not yet supported, as it requires code change to import symbols
 properly.</p>
 
-<h2>Building with Java</h2>
-
-<p>When building with Java on Windows, you must add the <a 
href="https://maven.apache.org/guides/getting-started/windows-prerequisites.html";>Maven</a>
 build tool to
-your path. The <code>JAVA_HOME</code> environment variable must also be 
manually set.
-An installation of the Java SDK can be found form <a 
href="http://www.oracle.com/technetwork/java/javase/downloads/index.html";>Oracle</a>.</p>
-
-<p>As of this writing, Java 9 is not yet supported, but Java 8 has been 
tested.</p>
-
-<p>The Java build defaults to <code>OFF</code> because it is slow. To build 
the Java
-components on Windows, turn it <code>ON</code>:</p>
-
-<pre><code class="powershell">mkdir build; cd build
-$env:PATH += ";C:\...\apache-maven-3.3.9\bin\"
-$env:JAVA_HOME = "C:\Program Files\Java\jdk1.8.0_144"
-cmake .. -DENABLE_JAVA=ON -DENABLE_LIBEVENT=ON -G "Visual Studio 15 2017 
Win64" -T "host=x64"
-cmake --build . --target mesos-java
-</code></pre>
-
-<p>Note that the <code>mesos-java</code> library does not have to be manually 
built; as
-<code>libmesos</code> will link it when Java is enabled.</p>
-
-<p>Unfortunately, on Windows the <code>FindJNI</code> CMake module will 
populate <code>JAVA_JVM_LIBRARY</code> with
-the path to the static <code>jvm.lib</code>, but this variable must point to 
the shared
-library, <code>jvm.dll</code>, as it is loaded at runtime. Set it correctly 
like this:</p>
-
-<pre><code>$env:JAVA_JVM_LIBRARY = "C:\Program 
Files\Java\jdk1.8.0_144\jre\bin\server\jvm.dll"
-</code></pre>
-
-<p>The library may still fail to load at runtime with the following error:</p>
-
-<blockquote><p>&ldquo;The specified module could not be 
found.&rdquo;</p></blockquote>
-
-<p>If this is the case, and the path to <code>jvm.dll</code> is verified to be 
correct, then
-the error message actually indicates that the dependencies of 
<code>jvm.dll</code> could
-not be found. On Windows, the DLL search path includes the environment variable
-<code>PATH</code>, so add the <code>bin</code> folder which contains 
<code>server\jvm.dll</code> to <code>PATH</code>:</p>
-
-<pre><code>$env:PATH += ";C:\Program Files\Java\jdk1.8.0_144\jre\bin"
-</code></pre>
-
-<h2>Building with OpenSSL</h2>
-
-<p>When building with OpenSSL on Windows, you must build or install a 
distribution
-of OpenSSL for Windows. A commonly chosen distribution is <a 
href="https://slproweb.com/products/Win32OpenSSL.html";>Shining Light
-Productions' OpenSSL</a>.</p>
-
-<p>As of this writing, OpenSSL 1.1.x is not yet supported, but 1.0.2L has been
-tested.</p>
-
-<p>Use <code>-DENABLE_SSL=ON</code> when running CMake to build with 
OpenSSL.</p>
-
   </div>
 </div>
 

http://git-wip-us.apache.org/repos/asf/mesos-site/blob/5682363e/content/documentation/latest/cmake-examples/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/cmake-examples/index.html 
b/content/documentation/latest/cmake-examples/index.html
index 9b62859..0afff2b 100644
--- a/content/documentation/latest/cmake-examples/index.html
+++ b/content/documentation/latest/cmake-examples/index.html
@@ -451,57 +451,6 @@ libraries by default.</p>
 Windows is not yet supported, as it requires code change to import symbols
 properly.</p>
 
-<h2>Building with Java</h2>
-
-<p>When building with Java on Windows, you must add the <a 
href="https://maven.apache.org/guides/getting-started/windows-prerequisites.html";>Maven</a>
 build tool to
-your path. The <code>JAVA_HOME</code> environment variable must also be 
manually set.
-An installation of the Java SDK can be found form <a 
href="http://www.oracle.com/technetwork/java/javase/downloads/index.html";>Oracle</a>.</p>
-
-<p>As of this writing, Java 9 is not yet supported, but Java 8 has been 
tested.</p>
-
-<p>The Java build defaults to <code>OFF</code> because it is slow. To build 
the Java
-components on Windows, turn it <code>ON</code>:</p>
-
-<pre><code class="powershell">mkdir build; cd build
-$env:PATH += ";C:\...\apache-maven-3.3.9\bin\"
-$env:JAVA_HOME = "C:\Program Files\Java\jdk1.8.0_144"
-cmake .. -DENABLE_JAVA=ON -DENABLE_LIBEVENT=ON -G "Visual Studio 15 2017 
Win64" -T "host=x64"
-cmake --build . --target mesos-java
-</code></pre>
-
-<p>Note that the <code>mesos-java</code> library does not have to be manually 
built; as
-<code>libmesos</code> will link it when Java is enabled.</p>
-
-<p>Unfortunately, on Windows the <code>FindJNI</code> CMake module will 
populate <code>JAVA_JVM_LIBRARY</code> with
-the path to the static <code>jvm.lib</code>, but this variable must point to 
the shared
-library, <code>jvm.dll</code>, as it is loaded at runtime. Set it correctly 
like this:</p>
-
-<pre><code>$env:JAVA_JVM_LIBRARY = "C:\Program 
Files\Java\jdk1.8.0_144\jre\bin\server\jvm.dll"
-</code></pre>
-
-<p>The library may still fail to load at runtime with the following error:</p>
-
-<blockquote><p>&ldquo;The specified module could not be 
found.&rdquo;</p></blockquote>
-
-<p>If this is the case, and the path to <code>jvm.dll</code> is verified to be 
correct, then
-the error message actually indicates that the dependencies of 
<code>jvm.dll</code> could
-not be found. On Windows, the DLL search path includes the environment variable
-<code>PATH</code>, so add the <code>bin</code> folder which contains 
<code>server\jvm.dll</code> to <code>PATH</code>:</p>
-
-<pre><code>$env:PATH += ";C:\Program Files\Java\jdk1.8.0_144\jre\bin"
-</code></pre>
-
-<h2>Building with OpenSSL</h2>
-
-<p>When building with OpenSSL on Windows, you must build or install a 
distribution
-of OpenSSL for Windows. A commonly chosen distribution is <a 
href="https://slproweb.com/products/Win32OpenSSL.html";>Shining Light
-Productions' OpenSSL</a>.</p>
-
-<p>As of this writing, OpenSSL 1.1.x is not yet supported, but 1.0.2L has been
-tested.</p>
-
-<p>Use <code>-DENABLE_SSL=ON</code> when running CMake to build with 
OpenSSL.</p>
-
   </div>
 </div>
 

http://git-wip-us.apache.org/repos/asf/mesos-site/blob/5682363e/content/documentation/latest/windows/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/latest/windows/index.html 
b/content/documentation/latest/windows/index.html
index bbb6463..d321919 100644
--- a/content/documentation/latest/windows/index.html
+++ b/content/documentation/latest/windows/index.html
@@ -144,10 +144,7 @@ patches, or lint source code).</p></li>
 
 <p>Following are the instructions for Windows 10.</p>
 
-<pre><code># Start an administrative session of PowerShell
-# (required for creating symlinks when using the agent).
-
-# Clone (or extract) Mesos.
+<pre><code># Clone (or extract) Mesos.
 git clone https://git-wip-us.apache.org/repos/asf/mesos.git
 cd mesos
 
@@ -171,14 +168,15 @@ src\mesos-agent.exe --master=&lt;master&gt; 
--work_dir=&lt;work folder&gt; --lau
 <p>The current implementation is known to have the following limitations:</p>
 
 <ul>
-<li>Only the agent should be run on Windows.  The Mesos master can be
+<li><p>Only the agent should be run on Windows.  The Mesos master can be
 launched, but only for testing as the master does not support
-high-availability setups on Windows.</li>
-<li>While Mesos supports NTFS long paths internally, tasks which do not support
-long paths must be run on agent whose <code>--work_dir</code> is a short 
path.</li>
-<li>The Mesos agent must be run as Administrator, mainly due to symlinks.</li>
-<li>The <code>MesosContainerizer</code> currently does not provide any actual
-resource isolation (similar to running the Mesos agent on POSIX).</li>
+high-availability setups on Windows.</p></li>
+<li><p>While Mesos supports NTFS long paths internally, tasks which do not 
support
+long paths must be run on agent whose <code>--work_dir</code> is a short 
path.</p></li>
+<li><p>The minimum versions of Windows supported are: Windows 10 Creators 
Update (AKA
+version 1703, build number 15063), and <a 
href="https://docs.microsoft.com/en-us/windows-server/get-started/get-started-with-1709";>Windows
 Server, version 1709</a>.
+It is likely that this will increase, due to evolving Windows container
+support and developer features which ease porting.</p></li>
 </ul>
 
 
@@ -187,6 +185,68 @@ resource isolation (similar to running the Mesos agent on 
POSIX).</li>
 <p>For more information regarding the status of Windows support in Mesos,
 please refer to the <a 
href="https://issues.apache.org/jira/browse/MESOS-3094";>JIRA epic</a>.</p>
 
+<h2>Build Configuration Examples</h2>
+
+<h3>Building with Java</h3>
+
+<p>This enables more unit tests, but we do not yet officially produce
+<code>mesos-master</code>.</p>
+
+<p>When building with Java on Windows, you must add the <a 
href="https://maven.apache.org/guides/getting-started/windows-prerequisites.html";>Maven</a>
 build tool to
+your path. The <code>JAVA_HOME</code> environment variable must also be 
manually set.
+An installation of the Java SDK can be found form <a 
href="http://www.oracle.com/technetwork/java/javase/downloads/index.html";>Oracle</a>.</p>
+
+<p>As of this writing, Java 9 is not yet supported, but Java 8 has been 
tested.</p>
+
+<p>The Java build defaults to <code>OFF</code> because it is slow. To build 
the Java
+components on Windows, turn it <code>ON</code>:</p>
+
+<pre><code class="powershell">mkdir build; cd build
+$env:PATH += ";C:\...\apache-maven-3.3.9\bin\"
+$env:JAVA_HOME = "C:\Program Files\Java\jdk1.8.0_144"
+cmake .. -DENABLE_JAVA=ON -DENABLE_LIBEVENT=ON -G "Visual Studio 15 2017 
Win64" -T "host=x64"
+cmake --build . --target mesos-java
+</code></pre>
+
+<p>Note that the <code>mesos-java</code> library does not have to be manually 
built; as
+<code>libmesos</code> will link it when Java is enabled.</p>
+
+<p>Unfortunately, on Windows the <code>FindJNI</code> CMake module will 
populate <code>JAVA_JVM_LIBRARY</code> with
+the path to the static <code>jvm.lib</code>, but this variable must point to 
the shared
+library, <code>jvm.dll</code>, as it is loaded at runtime. Set it correctly 
like this:</p>
+
+<pre><code>$env:JAVA_JVM_LIBRARY = "C:\Program 
Files\Java\jdk1.8.0_144\jre\bin\server\jvm.dll"
+</code></pre>
+
+<p>The library may still fail to load at runtime with the following error:</p>
+
+<blockquote><p>&ldquo;The specified module could not be 
found.&rdquo;</p></blockquote>
+
+<p>If this is the case, and the path to <code>jvm.dll</code> is verified to be 
correct, then
+the error message actually indicates that the dependencies of 
<code>jvm.dll</code> could
+not be found. On Windows, the DLL search path includes the environment variable
+<code>PATH</code>, so add the <code>bin</code> folder which contains 
<code>server\jvm.dll</code> to <code>PATH</code>:</p>
+
+<pre><code>$env:PATH += ";C:\Program Files\Java\jdk1.8.0_144\jre\bin"
+</code></pre>
+
+<h3>Building with OpenSSL</h3>
+
+<p>When building with OpenSSL on Windows, you must build or install a 
distribution
+of OpenSSL for Windows. A commonly chosen distribution is
+<a href="https://slproweb.com/products/Win32OpenSSL.html";>Shining Light 
Productions' OpenSSL</a>.</p>
+
+<p>As of this writing, OpenSSL 1.1.x is not yet supported, but 1.0.2M has been
+tested.</p>
+
+<p>Use <code>-DENABLE_SSL=ON</code> when running CMake to build with 
OpenSSL.</p>
+
+<p>Note that it will link to OpenSSL dynamically, so if the built executables 
are
+deployed elsewhere, that machine also needs OpenSSL installed.</p>
+
+<p>Beware that the OpenSSL installation, nor Mesos itself, comes with a 
certificate
+bundle, and so it is likely that certificate verification will fail.</p>
+
   </div>
 </div>
 

http://git-wip-us.apache.org/repos/asf/mesos-site/blob/5682363e/content/documentation/windows/index.html
----------------------------------------------------------------------
diff --git a/content/documentation/windows/index.html 
b/content/documentation/windows/index.html
index 0d2b25a..2cd6c01 100644
--- a/content/documentation/windows/index.html
+++ b/content/documentation/windows/index.html
@@ -144,10 +144,7 @@ patches, or lint source code).</p></li>
 
 <p>Following are the instructions for Windows 10.</p>
 
-<pre><code># Start an administrative session of PowerShell
-# (required for creating symlinks when using the agent).
-
-# Clone (or extract) Mesos.
+<pre><code># Clone (or extract) Mesos.
 git clone https://git-wip-us.apache.org/repos/asf/mesos.git
 cd mesos
 
@@ -171,14 +168,15 @@ src\mesos-agent.exe --master=&lt;master&gt; 
--work_dir=&lt;work folder&gt; --lau
 <p>The current implementation is known to have the following limitations:</p>
 
 <ul>
-<li>Only the agent should be run on Windows.  The Mesos master can be
+<li><p>Only the agent should be run on Windows.  The Mesos master can be
 launched, but only for testing as the master does not support
-high-availability setups on Windows.</li>
-<li>While Mesos supports NTFS long paths internally, tasks which do not support
-long paths must be run on agent whose <code>--work_dir</code> is a short 
path.</li>
-<li>The Mesos agent must be run as Administrator, mainly due to symlinks.</li>
-<li>The <code>MesosContainerizer</code> currently does not provide any actual
-resource isolation (similar to running the Mesos agent on POSIX).</li>
+high-availability setups on Windows.</p></li>
+<li><p>While Mesos supports NTFS long paths internally, tasks which do not 
support
+long paths must be run on agent whose <code>--work_dir</code> is a short 
path.</p></li>
+<li><p>The minimum versions of Windows supported are: Windows 10 Creators 
Update (AKA
+version 1703, build number 15063), and <a 
href="https://docs.microsoft.com/en-us/windows-server/get-started/get-started-with-1709";>Windows
 Server, version 1709</a>.
+It is likely that this will increase, due to evolving Windows container
+support and developer features which ease porting.</p></li>
 </ul>
 
 
@@ -187,6 +185,68 @@ resource isolation (similar to running the Mesos agent on 
POSIX).</li>
 <p>For more information regarding the status of Windows support in Mesos,
 please refer to the <a 
href="https://issues.apache.org/jira/browse/MESOS-3094";>JIRA epic</a>.</p>
 
+<h2>Build Configuration Examples</h2>
+
+<h3>Building with Java</h3>
+
+<p>This enables more unit tests, but we do not yet officially produce
+<code>mesos-master</code>.</p>
+
+<p>When building with Java on Windows, you must add the <a 
href="https://maven.apache.org/guides/getting-started/windows-prerequisites.html";>Maven</a>
 build tool to
+your path. The <code>JAVA_HOME</code> environment variable must also be 
manually set.
+An installation of the Java SDK can be found form <a 
href="http://www.oracle.com/technetwork/java/javase/downloads/index.html";>Oracle</a>.</p>
+
+<p>As of this writing, Java 9 is not yet supported, but Java 8 has been 
tested.</p>
+
+<p>The Java build defaults to <code>OFF</code> because it is slow. To build 
the Java
+components on Windows, turn it <code>ON</code>:</p>
+
+<pre><code class="powershell">mkdir build; cd build
+$env:PATH += ";C:\...\apache-maven-3.3.9\bin\"
+$env:JAVA_HOME = "C:\Program Files\Java\jdk1.8.0_144"
+cmake .. -DENABLE_JAVA=ON -DENABLE_LIBEVENT=ON -G "Visual Studio 15 2017 
Win64" -T "host=x64"
+cmake --build . --target mesos-java
+</code></pre>
+
+<p>Note that the <code>mesos-java</code> library does not have to be manually 
built; as
+<code>libmesos</code> will link it when Java is enabled.</p>
+
+<p>Unfortunately, on Windows the <code>FindJNI</code> CMake module will 
populate <code>JAVA_JVM_LIBRARY</code> with
+the path to the static <code>jvm.lib</code>, but this variable must point to 
the shared
+library, <code>jvm.dll</code>, as it is loaded at runtime. Set it correctly 
like this:</p>
+
+<pre><code>$env:JAVA_JVM_LIBRARY = "C:\Program 
Files\Java\jdk1.8.0_144\jre\bin\server\jvm.dll"
+</code></pre>
+
+<p>The library may still fail to load at runtime with the following error:</p>
+
+<blockquote><p>&ldquo;The specified module could not be 
found.&rdquo;</p></blockquote>
+
+<p>If this is the case, and the path to <code>jvm.dll</code> is verified to be 
correct, then
+the error message actually indicates that the dependencies of 
<code>jvm.dll</code> could
+not be found. On Windows, the DLL search path includes the environment variable
+<code>PATH</code>, so add the <code>bin</code> folder which contains 
<code>server\jvm.dll</code> to <code>PATH</code>:</p>
+
+<pre><code>$env:PATH += ";C:\Program Files\Java\jdk1.8.0_144\jre\bin"
+</code></pre>
+
+<h3>Building with OpenSSL</h3>
+
+<p>When building with OpenSSL on Windows, you must build or install a 
distribution
+of OpenSSL for Windows. A commonly chosen distribution is
+<a href="https://slproweb.com/products/Win32OpenSSL.html";>Shining Light 
Productions' OpenSSL</a>.</p>
+
+<p>As of this writing, OpenSSL 1.1.x is not yet supported, but 1.0.2M has been
+tested.</p>
+
+<p>Use <code>-DENABLE_SSL=ON</code> when running CMake to build with 
OpenSSL.</p>
+
+<p>Note that it will link to OpenSSL dynamically, so if the built executables 
are
+deployed elsewhere, that machine also needs OpenSSL installed.</p>
+
+<p>Beware that the OpenSSL installation, nor Mesos itself, comes with a 
certificate
+bundle, and so it is likely that certificate verification will fail.</p>
+
   </div>
 </div>
 

Reply via email to