[
https://issues.apache.org/jira/browse/MESOS-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970167#comment-16970167
]
Benno Evers commented on MESOS-9991:
------------------------------------
{noformat}
commit 09c830d87b88d4c2f386cb9ded5931528d6cf144
Author: Benjamin Bannier <[email protected]>
Date: Fri Nov 8 14:19:16 2019 +0100
Added authorization handling for reservations with `source`.
This patch adds authorization handling for `RESERVE` operations
containing `source` fields. In order to stay backwards-compatible we add
a dedicated authorization branch for such operations which under the
hood translates each removed reservation to an `UNRESERVE` operation and
every added reservation as a `RESERVE` operation where we fall back to
existing authorization code for authorization.
Review: https://reviews.apache.org/r/71729/
{noformat}
> Update 'Master::authorizeReserveResources' for re-reservations
> --------------------------------------------------------------
>
> Key: MESOS-9991
> URL: https://issues.apache.org/jira/browse/MESOS-9991
> Project: Mesos
> Issue Type: Task
> Reporter: Benjamin Bannier
> Assignee: Benjamin Bannier
> Priority: Major
> Labels: foundations
>
> We need to authorize all modifications to bring {{source}} to common
> ancestor, and from common ancestor to {{resources}}.
> * each removed authorizations needs to be authorized as an {{unreserve}}
> operation
> * each added reservation needs to be authorized as a {{reserve}} operation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
