Repository: mesos-site Updated Branches: refs/heads/asf-site 9d780b084 -> 131ab2d2b
Updated the website built from mesos SHA: 2402f99. Project: http://git-wip-us.apache.org/repos/asf/mesos-site/repo Commit: http://git-wip-us.apache.org/repos/asf/mesos-site/commit/131ab2d2 Tree: http://git-wip-us.apache.org/repos/asf/mesos-site/tree/131ab2d2 Diff: http://git-wip-us.apache.org/repos/asf/mesos-site/diff/131ab2d2 Branch: refs/heads/asf-site Commit: 131ab2d2b0fae3e7907956a85bf899b26161ba03 Parents: 9d780b0 Author: jenkins <[email protected]> Authored: Thu May 3 21:53:18 2018 +0000 Committer: jenkins <[email protected]> Committed: Thu May 3 21:53:18 2018 +0000 ---------------------------------------------------------------------- content/blog/feed.xml | 2 +- .../index.html | 2 +- content/documentation/csi/index.html | 6 +- content/documentation/latest/csi/index.html | 6 +- .../documentation/latest/upgrades/index.html | 58 ++++++++++++++++++-- content/documentation/upgrades/index.html | 58 ++++++++++++++++++-- 6 files changed, 116 insertions(+), 16 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mesos-site/blob/131ab2d2/content/blog/feed.xml ---------------------------------------------------------------------- diff --git a/content/blog/feed.xml b/content/blog/feed.xml index d28c088..26295fc 100644 --- a/content/blog/feed.xml +++ b/content/blog/feed.xml @@ -292,7 +292,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;&#97;&#105;&#108;&#x74;&#x6f;&#x3a;&#x64;&#x65;&#118;&#x40;&#97;&#x70;&#x61;&#99;&#104;&#101;&#x2e;&#109;&#x65;&#x73;&#111;&#x73;&#46;&#x6f;&#114;&#x67;">&#100;&#101;&#x76;&#x40;&#97;&#x70;&#x61;&#99;&#104;&#x65;&#x2e;&#109;&#101;&#115;&#x6f;&#115;&#x2e;&#111;&#x72;&#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="&#x6d;&#x61;&#105;&#108;&#x74;&#111;&#x3a;&#x64;&#101;&#x76;&#x40;&#x61;&#112;&#97;&#99;&#104;&#101;&#x2e;&#109;&#x65;&#x73;&#x6f;&#115;&#x2e;&#x6f;&#114;&#103;">&#100;&#101;&#118;&#64;&#x61;&#x70;&#97;&#x63;&#x68;&#101;&#x2e;&#109;&#101;&#115;&#x6f;&#115;&#46;&#x6f;&#114;&#103;</a>.</p> </content> </entry> http://git-wip-us.apache.org/repos/asf/mesos-site/blob/131ab2d2/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 4186922..588eb7b 100644 --- a/content/blog/performance-working-group-progress-report/index.html +++ b/content/blog/performance-working-group-progress-report/index.html @@ -238,7 +238,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/131ab2d2/content/documentation/csi/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/csi/index.html b/content/documentation/csi/index.html index 6e9b297..7fdffea 100644 --- a/content/documentation/csi/index.html +++ b/content/documentation/csi/index.html @@ -112,7 +112,9 @@ <p>This document describes the <a href="https://github.com/container-storage-interface/spec";>Container Storage Interface</a> (CSI) support in Mesos.</p> -<p>Currently, only CSI spec version 0.1 is supported.</p> +<p>Currently, only CSI spec version 0.2 is supported in Mesos 1.6 due to +incompatible changes between CSI version 0.1 and version 0.2. CSI version 0.1 is +supported in Mesos 1.5.</p> <h2>Motivation</h2> @@ -283,7 +285,7 @@ if the disk resource is backed by a <a href="https://github.com/container-storag from a CSI plugin. This field must not be set by frameworks.</li> <li><code>metadata</code>: This maps to CSI <a href="https://github.com/container-storage-interface/spec/blob/v0.1.0/spec.md#createvolume";>Volume Attributes</a> if the disk resource is backed by a <a href="https://github.com/container-storage-interface/spec/blob/v0.1.0/spec.md#terminology";>Volume</a> -from a CSI plugin. This field must not be set by framweworks.</li> +from a CSI plugin. This field must not be set by frameworks.</li> </ul> http://git-wip-us.apache.org/repos/asf/mesos-site/blob/131ab2d2/content/documentation/latest/csi/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/csi/index.html b/content/documentation/latest/csi/index.html index a7d42cc..fae7eeb 100644 --- a/content/documentation/latest/csi/index.html +++ b/content/documentation/latest/csi/index.html @@ -112,7 +112,9 @@ <p>This document describes the <a href="https://github.com/container-storage-interface/spec";>Container Storage Interface</a> (CSI) support in Mesos.</p> -<p>Currently, only CSI spec version 0.1 is supported.</p> +<p>Currently, only CSI spec version 0.2 is supported in Mesos 1.6 due to +incompatible changes between CSI version 0.1 and version 0.2. CSI version 0.1 is +supported in Mesos 1.5.</p> <h2>Motivation</h2> @@ -283,7 +285,7 @@ if the disk resource is backed by a <a href="https://github.com/container-storag from a CSI plugin. This field must not be set by frameworks.</li> <li><code>metadata</code>: This maps to CSI <a href="https://github.com/container-storage-interface/spec/blob/v0.1.0/spec.md#createvolume";>Volume Attributes</a> if the disk resource is backed by a <a href="https://github.com/container-storage-interface/spec/blob/v0.1.0/spec.md#terminology";>Volume</a> -from a CSI plugin. This field must not be set by framweworks.</li> +from a CSI plugin. This field must not be set by frameworks.</li> </ul> http://git-wip-us.apache.org/repos/asf/mesos-site/blob/131ab2d2/content/documentation/latest/upgrades/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/latest/upgrades/index.html b/content/documentation/latest/upgrades/index.html index c16d837..f4c68ea 100644 --- a/content/documentation/latest/upgrades/index.html +++ b/content/documentation/latest/upgrades/index.html @@ -148,6 +148,38 @@ R Removed feature/behavior </thead> <tr> <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Version--> + 1.6.x + </td> + + <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Mesos Core--> + <ul style="padding-left:10px;"> + <li>C <a href="#1-6-x-grpc-requirement">Requirement for gRPC library</a></li> + <li>C <a href="#1-6-x-csi-support">CSI v0.2 Support</a></li> + </ul> + </td> + + <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Flags--> + <ul style="padding-left:10px;"> + </ul> + </td> + + <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Framework API--> + <ul style="padding-left:10px;"> + </ul> + </td> + + <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Module API--> + <ul style="padding-left:10px;"> + </ul> + </td> + + <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Endpoints--> + <ul style="padding-left:10px;"> + </ul> + </td> +</tr> +<tr> + <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Version--> 1.5.x </td> @@ -466,6 +498,22 @@ R Removed feature/behavior </table> +<h2>Upgrading from 1.5.x to 1.6.x</h2> + +<p><a name="1-6-x-grpc-requirement"></a></p> + +<ul> +<li>gRPC version 1.10+ is required to build Mesos when enabling gRPC-related features. Please upgrade your gRPC library if you are using an unbundled one.</li> +</ul> + + +<p><a name="1-6-x-csi-support"></a></p> + +<ul> +<li>CSI v0.2 is now supported as experimental. Due to the incompatibility between CSI v0.1 and v0.2, the experimental support for CSI v0.1 is deprecated, and the operator must remove all storage local resource providers within an agent before upgrading the agent. NOTE: This is a <strong>breaking change</strong> for storage local resource providers.</li> +</ul> + + <h2>Upgrading from 1.4.x to 1.5.x</h2> <p><a name="1-5-x-task-starting"></a></p> @@ -497,7 +545,7 @@ that caused a task to fail with a resource limitation reason.</li> <ul> <li><code>--container_ports_watch_interval</code> specifies the interval at which the isolator reconciles port assignments.</li> -<li><code>--check_agent_port_range_only</code> excludes ports outside the agent’s range from port reconcilation.</li> +<li><code>--check_agent_port_range_only</code> excludes ports outside the agent’s range from port reconciliation.</li> </ul> </li> </ul> @@ -565,7 +613,7 @@ changed. Note that if this feature is used, the master version is required to be <p><a name="1-4-x-bounding-capabilities"></a></p> <ul> -<li>Explicitly setting the bounding capabilities of a task independently of the effective capabilities is now supported. Frameworks can specifiy the task bounding capabilities by using the <code>LinuxInfo.bounding_capabilities</code> message. Operators can specify the default bounding capabilities using the agent <code>--bounding_capabilities</code> flag. This flag also specifies the maximum bounding set that a framework is allowed to specify.</li> +<li>Explicitly setting the bounding capabilities of a task independently of the effective capabilities is now supported. Frameworks can specify the task bounding capabilities by using the <code>LinuxInfo.bounding_capabilities</code> message. Operators can specify the default bounding capabilities using the agent <code>--bounding_capabilities</code> flag. This flag also specifies the maximum bounding set that a framework is allowed to specify.</li> </ul> @@ -811,7 +859,7 @@ changed. Note that if this feature is used, the master version is required to be <p><a name="1-1-x-allocator-updateallocation"></a></p> <ul> -<li>Mesos 1.1 adds an <code>offeredResources</code> argument to the <code>Allocator::updateAllocation()</code> method. It is used to indicate the resources that the operations passed to <code>updateAllocation()</code> are applied to. <a href="https://issues.apache.org/jira/browse/MESOS-4431";>MESOS-4431</a> (paticularly <a href="https://reviews.apache.org/r/45961/";>/r/45961/</a>) has more details on the motivation.</li> +<li>Mesos 1.1 adds an <code>offeredResources</code> argument to the <code>Allocator::updateAllocation()</code> method. It is used to indicate the resources that the operations passed to <code>updateAllocation()</code> are applied to. <a href="https://issues.apache.org/jira/browse/MESOS-4431";>MESOS-4431</a> (particularly <a href="https://reviews.apache.org/r/45961/";>/r/45961/</a>) has more details on the motivation.</li> </ul> @@ -970,7 +1018,7 @@ changed. Note that if this feature is used, the master version is required to be <li>The <code>SetQuota</code> and <code>RemoveQuota</code> ACLs have been deprecated. To replace these, a new ACL <code>UpdateQuota</code> have been introduced. In addition, a new ACL <code>GetQuota</code> have been added; these control which principals are allowed to query quota information for which roles. These changes affect the <code>--acls</code> flag for the local authorizer in the following ways: <ul> -<li>The <code>update_quotas</code> ACL cannot be used in combination with either the <code>set_quotas</code> or <code>remove_quotas</code> ACL. The local authorizor will produce an error in such a case;</li> +<li>The <code>update_quotas</code> ACL cannot be used in combination with either the <code>set_quotas</code> or <code>remove_quotas</code> ACL. The local authorizer will produce an error in such a case;</li> <li>When upgrading a Mesos cluster that uses the <code>set_quotas</code> or <code>remove_quotas</code> ACLs, the operator should first upgrade the Mesos binaries. At this point, the deprecated ACLs will still be enforced. After the upgrade has been verified, the operator should replace deprecated values for <code>set_quotas</code> and <code>remove_quotas</code> with equivalent values for <code>update_quotas</code>;</li> <li>If desired, the operator can use the <code>get_quotas</code> ACL after the upgrade to control which principals are allowed to query quota information.</li> </ul> @@ -1009,7 +1057,7 @@ changed. Note that if this feature is used, the master version is required to be <p><a name="1-0-x-http-authentication-flags"></a></p> <ul> -<li>The <code>--authenticate_http</code> flag has been deprecated in favor of <code>--authenticate_http_readwrite</code>. Setting <code>--authenticate_http_readwrite</code> will now enable authentication for all endpoints which previously had authentication support. These happen to be the endpoints which allow modifiication of the cluster state, or “read-write” endpoints. Note that <code>/logging/toggle</code>, <code>/profiler/start</code>, <code>/profiler/stop</code>, <code>/maintenance/schedule</code>, <code>/machine/up</code>, and <code>/machine/down</code> previously did not have authentication support, but in 1.0 if either <code>--authenticate_http</code> or <code>--authenticate_http_readwrite</code> is set, those endpoints will now require authentication. A new flag has also been introduced, <code>--authenticate_http_readonly</code>, which enables authentication for endpoints which support authentication and do not allow modification of the state of the cluster, li ke <code>/state</code> or <code>/flags</code>.</li> +<li>The <code>--authenticate_http</code> flag has been deprecated in favor of <code>--authenticate_http_readwrite</code>. Setting <code>--authenticate_http_readwrite</code> will now enable authentication for all endpoints which previously had authentication support. These happen to be the endpoints which allow modification of the cluster state, or “read-write” endpoints. Note that <code>/logging/toggle</code>, <code>/profiler/start</code>, <code>/profiler/stop</code>, <code>/maintenance/schedule</code>, <code>/machine/up</code>, and <code>/machine/down</code> previously did not have authentication support, but in 1.0 if either <code>--authenticate_http</code> or <code>--authenticate_http_readwrite</code> is set, those endpoints will now require authentication. A new flag has also been introduced, <code>--authenticate_http_readonly</code>, which enables authentication for endpoints which support authentication and do not allow modification of the state of the cluster, lik e <code>/state</code> or <code>/flags</code>.</li> </ul> http://git-wip-us.apache.org/repos/asf/mesos-site/blob/131ab2d2/content/documentation/upgrades/index.html ---------------------------------------------------------------------- diff --git a/content/documentation/upgrades/index.html b/content/documentation/upgrades/index.html index f0fb627..7770425 100644 --- a/content/documentation/upgrades/index.html +++ b/content/documentation/upgrades/index.html @@ -148,6 +148,38 @@ R Removed feature/behavior </thead> <tr> <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Version--> + 1.6.x + </td> + + <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Mesos Core--> + <ul style="padding-left:10px;"> + <li>C <a href="#1-6-x-grpc-requirement">Requirement for gRPC library</a></li> + <li>C <a href="#1-6-x-csi-support">CSI v0.2 Support</a></li> + </ul> + </td> + + <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Flags--> + <ul style="padding-left:10px;"> + </ul> + </td> + + <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Framework API--> + <ul style="padding-left:10px;"> + </ul> + </td> + + <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Module API--> + <ul style="padding-left:10px;"> + </ul> + </td> + + <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Endpoints--> + <ul style="padding-left:10px;"> + </ul> + </td> +</tr> +<tr> + <td style="word-wrap: break-word; overflow-wrap: break-word;"><!--Version--> 1.5.x </td> @@ -466,6 +498,22 @@ R Removed feature/behavior </table> +<h2>Upgrading from 1.5.x to 1.6.x</h2> + +<p><a name="1-6-x-grpc-requirement"></a></p> + +<ul> +<li>gRPC version 1.10+ is required to build Mesos when enabling gRPC-related features. Please upgrade your gRPC library if you are using an unbundled one.</li> +</ul> + + +<p><a name="1-6-x-csi-support"></a></p> + +<ul> +<li>CSI v0.2 is now supported as experimental. Due to the incompatibility between CSI v0.1 and v0.2, the experimental support for CSI v0.1 is deprecated, and the operator must remove all storage local resource providers within an agent before upgrading the agent. NOTE: This is a <strong>breaking change</strong> for storage local resource providers.</li> +</ul> + + <h2>Upgrading from 1.4.x to 1.5.x</h2> <p><a name="1-5-x-task-starting"></a></p> @@ -497,7 +545,7 @@ that caused a task to fail with a resource limitation reason.</li> <ul> <li><code>--container_ports_watch_interval</code> specifies the interval at which the isolator reconciles port assignments.</li> -<li><code>--check_agent_port_range_only</code> excludes ports outside the agent’s range from port reconcilation.</li> +<li><code>--check_agent_port_range_only</code> excludes ports outside the agent’s range from port reconciliation.</li> </ul> </li> </ul> @@ -565,7 +613,7 @@ changed. Note that if this feature is used, the master version is required to be <p><a name="1-4-x-bounding-capabilities"></a></p> <ul> -<li>Explicitly setting the bounding capabilities of a task independently of the effective capabilities is now supported. Frameworks can specifiy the task bounding capabilities by using the <code>LinuxInfo.bounding_capabilities</code> message. Operators can specify the default bounding capabilities using the agent <code>--bounding_capabilities</code> flag. This flag also specifies the maximum bounding set that a framework is allowed to specify.</li> +<li>Explicitly setting the bounding capabilities of a task independently of the effective capabilities is now supported. Frameworks can specify the task bounding capabilities by using the <code>LinuxInfo.bounding_capabilities</code> message. Operators can specify the default bounding capabilities using the agent <code>--bounding_capabilities</code> flag. This flag also specifies the maximum bounding set that a framework is allowed to specify.</li> </ul> @@ -811,7 +859,7 @@ changed. Note that if this feature is used, the master version is required to be <p><a name="1-1-x-allocator-updateallocation"></a></p> <ul> -<li>Mesos 1.1 adds an <code>offeredResources</code> argument to the <code>Allocator::updateAllocation()</code> method. It is used to indicate the resources that the operations passed to <code>updateAllocation()</code> are applied to. <a href="https://issues.apache.org/jira/browse/MESOS-4431";>MESOS-4431</a> (paticularly <a href="https://reviews.apache.org/r/45961/";>/r/45961/</a>) has more details on the motivation.</li> +<li>Mesos 1.1 adds an <code>offeredResources</code> argument to the <code>Allocator::updateAllocation()</code> method. It is used to indicate the resources that the operations passed to <code>updateAllocation()</code> are applied to. <a href="https://issues.apache.org/jira/browse/MESOS-4431";>MESOS-4431</a> (particularly <a href="https://reviews.apache.org/r/45961/";>/r/45961/</a>) has more details on the motivation.</li> </ul> @@ -970,7 +1018,7 @@ changed. Note that if this feature is used, the master version is required to be <li>The <code>SetQuota</code> and <code>RemoveQuota</code> ACLs have been deprecated. To replace these, a new ACL <code>UpdateQuota</code> have been introduced. In addition, a new ACL <code>GetQuota</code> have been added; these control which principals are allowed to query quota information for which roles. These changes affect the <code>--acls</code> flag for the local authorizer in the following ways: <ul> -<li>The <code>update_quotas</code> ACL cannot be used in combination with either the <code>set_quotas</code> or <code>remove_quotas</code> ACL. The local authorizor will produce an error in such a case;</li> +<li>The <code>update_quotas</code> ACL cannot be used in combination with either the <code>set_quotas</code> or <code>remove_quotas</code> ACL. The local authorizer will produce an error in such a case;</li> <li>When upgrading a Mesos cluster that uses the <code>set_quotas</code> or <code>remove_quotas</code> ACLs, the operator should first upgrade the Mesos binaries. At this point, the deprecated ACLs will still be enforced. After the upgrade has been verified, the operator should replace deprecated values for <code>set_quotas</code> and <code>remove_quotas</code> with equivalent values for <code>update_quotas</code>;</li> <li>If desired, the operator can use the <code>get_quotas</code> ACL after the upgrade to control which principals are allowed to query quota information.</li> </ul> @@ -1009,7 +1057,7 @@ changed. Note that if this feature is used, the master version is required to be <p><a name="1-0-x-http-authentication-flags"></a></p> <ul> -<li>The <code>--authenticate_http</code> flag has been deprecated in favor of <code>--authenticate_http_readwrite</code>. Setting <code>--authenticate_http_readwrite</code> will now enable authentication for all endpoints which previously had authentication support. These happen to be the endpoints which allow modifiication of the cluster state, or “read-write” endpoints. Note that <code>/logging/toggle</code>, <code>/profiler/start</code>, <code>/profiler/stop</code>, <code>/maintenance/schedule</code>, <code>/machine/up</code>, and <code>/machine/down</code> previously did not have authentication support, but in 1.0 if either <code>--authenticate_http</code> or <code>--authenticate_http_readwrite</code> is set, those endpoints will now require authentication. A new flag has also been introduced, <code>--authenticate_http_readonly</code>, which enables authentication for endpoints which support authentication and do not allow modification of the state of the cluster, li ke <code>/state</code> or <code>/flags</code>.</li> +<li>The <code>--authenticate_http</code> flag has been deprecated in favor of <code>--authenticate_http_readwrite</code>. Setting <code>--authenticate_http_readwrite</code> will now enable authentication for all endpoints which previously had authentication support. These happen to be the endpoints which allow modification of the cluster state, or “read-write” endpoints. Note that <code>/logging/toggle</code>, <code>/profiler/start</code>, <code>/profiler/stop</code>, <code>/maintenance/schedule</code>, <code>/machine/up</code>, and <code>/machine/down</code> previously did not have authentication support, but in 1.0 if either <code>--authenticate_http</code> or <code>--authenticate_http_readwrite</code> is set, those endpoints will now require authentication. A new flag has also been introduced, <code>--authenticate_http_readonly</code>, which enables authentication for endpoints which support authentication and do not allow modification of the state of the cluster, lik e <code>/state</code> or <code>/flags</code>.</li> </ul>
