[
https://issues.apache.org/jira/browse/MESOS-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966524#comment-14966524
]
Yong Qiao Wang commented on MESOS-2936:
---------------------------------------
Hey, [~alexr], we are planing to add a separated endpoint /roles to add/remove
role in Role Dynamic Configuration project (MESOS-3177). I found in the request
quota design, it also can be used to add a role. I think there are some repeats
between these two projects. For my understanding , quota should be view as an
attribute of role, so in quota management project, the quota updating
action(PUT) should be enough to manage(add/update/remove) the quota of an exist
role, and if the role does not exist, then you need to create this role with
endpoint /roles before configuring the quota for this role. So maybe we need to
remove the quota request action from quota management endpoint. [~alexr], any
thoughts for this?
In addition, welcome you to give me a review for the role dynamically configure
design, your comments is important for me. Thanks in advance.
> Create a design document for Quota support in Master
> ----------------------------------------------------
>
> Key: MESOS-2936
> URL: https://issues.apache.org/jira/browse/MESOS-2936
> Project: Mesos
> Issue Type: Documentation
> Components: documentation
> Reporter: Alexander Rukletsov
> Assignee: Alexander Rukletsov
> Labels: mesosphere
>
> Create a design document for the Quota feature support in Mesos Master
> (excluding allocator) to be shared with the Mesos community.
> Design Doc:
> https://docs.google.com/document/d/16iRNmziasEjVOblYp5bbkeBZ7pnjNlaIzPQqMTHQ-9I/edit?usp=sharing
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
