[ 
https://issues.apache.org/jira/browse/MESOS-7575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052549#comment-16052549
 ] 

Michael Park commented on MESOS-7575:
-------------------------------------

{noformat}
commit 5821df6aa28b53b46cca37234f06dbd97eb48487
Author: Michael Park <[email protected]>
Date:   Fri Jun 16 14:50:52 2017 -0700

    Added protobuf changes for reservation refinement.

    With reservation refinement, we now represent the reservation state in
    `Resource.reservations` rather than with `Resource.role` and
    `Resource.reservation`. We also keep track of the type of reservation,
    and the role the reservation is for in the `Resource.ReservationInfo`.
    This patch introduces these changes and explains the different formats
    in detail.

    Review: https://reviews.apache.org/r/59861/
{noformat}

> Support reservation refinement for hierarchical roles.
> ------------------------------------------------------
>
>                 Key: MESOS-7575
>                 URL: https://issues.apache.org/jira/browse/MESOS-7575
>             Project: Mesos
>          Issue Type: Epic
>            Reporter: Michael Park
>            Assignee: Michael Park
>
> With the introduction of hierarchical roles, Mesos provides a mechanism to 
> delegate resources down a hierarchy.
> To complement this, we'll introduce a mechanism to *refine* the reservations 
> down the hierarchy.
> For example, given resources allocated to role {{foo}}, it can be further 
> reserved for {{foo/bar}}.
> When the resources allocated to {{foo/bar}} is unreserved, it goes back to 
> where it came from. In this case, back to role {{foo}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to