[
https://issues.apache.org/jira/browse/MESOS-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053489#comment-16053489
]
Michael Park edited comment on MESOS-7655 at 6/20/17 9:13 AM:
--------------------------------------------------------------
https://reviews.apache.org/r/60181/
https://reviews.apache.org/r/60182/
https://reviews.apache.org/r/60016/
https://reviews.apache.org/r/60184/
https://reviews.apache.org/r/60017/
https://reviews.apache.org/r/60040/
https://reviews.apache.org/r/60015/
was (Author: mcypark):
https://reviews.apache.org/r/60181/
https://reviews.apache.org/r/60182/
https://reviews.apache.org/r/60184/
https://reviews.apache.org/r/60016/
https://reviews.apache.org/r/60017/
https://reviews.apache.org/r/60040/
https://reviews.apache.org/r/60015/
> 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)
