You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by ch...@apache.org on 2018/08/21 22:59:38 UTC

[mesos] 01/02: Removed sorter changes from `upgrades.md`.

This is an automated email from the ASF dual-hosted git repository.

chhsiao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mesos.git

commit 7928d443fb612fa35493cca0d46bc71bd74488f9
Author: Chun-Hung Hsiao <ch...@mesosphere.io>
AuthorDate: Tue Aug 21 15:19:09 2018 -0700

    Removed sorter changes from `upgrades.md`.
    
    The description for sorter changes has been removed since it's internal.
---
 docs/upgrades.md | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/docs/upgrades.md b/docs/upgrades.md
index ec9b3af..8da108c 100644
--- a/docs/upgrades.md
+++ b/docs/upgrades.md
@@ -70,7 +70,6 @@ We categorize the changes as follows:
     <ul style="padding-left:10px;">
       <li>C <a href="#1-7-x-container-logger">ContainerLogger module interface changes</a></li>
       <li>C <a href="#1-7-x-isolator-recover">Isolator::recover module interface change</a></li>
-      <li>C <a href="#1-7-x-sorter-update">Changed semantics of Sorter::update</a></li>
     </ul>
   </td>
 
@@ -465,10 +464,6 @@ We categorize the changes as follows:
 
 * `Isolator::recover()` has been updated to take an `std::vector` instead of `std::list` of container states.
 
-<a name="1-7-x-sorter-update"></a>
-
-* The semantics of `Sorter::update` has been changed so that resources can be removed from a client's allocation without removing the full agent in which they reside. Callers are expected to update the total resources of the agent as well by, e.g., removing the agent and adding it back with the new total resources.
-
 <a name="1-7-x-volume-mode-support"></a>
 
 * Previously the HOST_PATH/SANDBOX_PATH/IMAGE/SECRET/DOCKER_VOLUME volumes were always mounted for container in read-write mode, i.e., the `Volume.mode` field was not honored. Now we will mount these volumes based on the `Volume.mode` field so framework can choose to mount the volume for the container in either read-write mode or read-only mode.