[
https://issues.apache.org/jira/browse/MESOS-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052396#comment-16052396
]
Michael Park commented on MESOS-7655:
-------------------------------------
{noformat}
commit 9cfae1bdea14ab07b879d5aba8ec2c8ac2f76693
Author: Michael Park <[email protected]>
Date: Tue Jun 13 16:35:30 2017 -0700
Updated `isAllocatableTo` to use the `roles::isStrictSubroleOf` utility.
This patch simplifies the `isAllocatableTo` function by leveraging
the `roles::isStrictSubroleOf` function introduced in
https://reviews.apache.org/r/60064.
Review: https://reviews.apache.org/r/60064
{noformat}
{noformat}
commit dfa37ed8af4647fbfb58471caa46acfcf8f5fba8
Author: Michael Park <[email protected]>
Date: Tue Jun 13 16:10:51 2017 -0700
Introduced `roles::isStrictSubroleOf` function.
This patch introduces a utility to determine whether
a role is a strict subrole of another role.
Review: https://reviews.apache.org/r/60063
{noformat}
> Reservation Refinement: Update the resources logic.
> ---------------------------------------------------
>
> Key: MESOS-7655
> URL: https://issues.apache.org/jira/browse/MESOS-7655
> Project: Mesos
> Issue Type: Bug
> Reporter: Michael Park
> Assignee: Michael Park
>
> With reservation refinement, there is a new framework capability called
> {{RESERVATION_REFINEMENT}}. The framework is required to use the
> {{Resource.reservations}} field to express reservations if the capability is
> set, otherwise it is required to use the {{Resource.role}} and
> {{Resource.reservation}} fields.
> After the validation, we transform the resources from the old format to the
> new format and deal with the new format internally.
> This allows us to only deal with the old format at the validation phase, and
> update the code to only consider the new format for all other
> Resources-related functions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
