[
https://issues.apache.org/jira/browse/MESOS-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052774#comment-16052774
]
Michael Park commented on MESOS-7655:
-------------------------------------
{noformat}
commit fe6a3eb48af793b5cf2e1308d9164cdec1c4875a
Author: Michael Park <[email protected]>
Date: Sat Jun 17 01:41:55 2017 -0700
Resources: Updated the validation logic.
This patch updates `Resources::validate`, and `resource::validate`.
The `Resources::validate` function ensures that the resources are
either in the 'pre-' or 'post-' reservation-refinement formats,
but not both.
The `resource::validate` function takes an optional framework
capabilities and ensures that the resources format matches
the framework's RESERVATION_REFINEMENT capbility.
Review: https://reviews.apache.org/r/60013/
{noformat}
{noformat}
commit 4f16535704ac6f8417dfcef6c6347658114db97e
Author: Michael Park <[email protected]>
Date: Wed Jun 14 21:28:04 2017 -0700
Resources: Added `toUnreserved()` and `(push|pop)Reservation`.
This patches introduces utilities `toUnreserved`, `pushReservation` and
`popReservation`. They are intended to replace the current `flatten`.
We'll switch over to use them once the 'post-reservation-refinement'
format is used for `Resources`.
Review: https://reviews.apache.org/r/60020
{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)
