[jira] [Commented] (MESOS-5155) Consolidate authorization actions for quota.

["Alexander Rukletsov (JIRA)" <ji...@apache.org>]

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

Alexander Rukletsov commented on MESOS-5155:
--------------------------------------------

[~zhitao], Let me try to answer these questions:
1. IIUC, you are saying that operators won't be able to use update quota and old set/remove authz actions together. I think this is fine, because we introduce update quota *after* introducing a new authz action. We can even motivate operators to migrate faster ; ).
2. IIUC this one, we can add an overload for {{Master::QuotaHandler::authorizeRemoveQuota()}} which takes a principal and a role, check *both* for now, and remove the current overload after deprecation cycle. Does this make sense?

> Consolidate authorization actions for quota.
> --------------------------------------------
>
>                 Key: MESOS-5155
>                 URL: https://issues.apache.org/jira/browse/MESOS-5155
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Alexander Rukletsov
>            Assignee: Zhitao Li
>              Labels: mesosphere
>
> We should have just a single authz action: {{UPDATE_QUOTA_WITH_ROLE}}. It was a mistake in retrospect to introduce multiple actions.
> Actions that are not symmetrical are register/teardown and dynamic reservations. The way they are implemented in this way is because entities that do one action differ from entities that do the other. For example, register framework is issued by a framework, teardown by an operator. What is a good way to identify a framework? A role it runs in, which may be different each launch and makes no sense in multi-role frameworks setup or better a sort of a group id, which is its principal. For dynamic reservations and persistent volumes, they can be both issued by frameworks and operators, hence similar reasoning applies. 
> Now, quota is associated with a role and set only by operators. Do we need to care about principals that set it? Not that much. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)