[
https://issues.apache.org/jira/browse/MESOS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049956#comment-15049956
]
Yong Qiao Wang commented on MESOS-4097:
---------------------------------------
OK, per my understanding of role management I think Mesos is prefer to set
role-related configuration with some separated endpoint, such as use /quota to
set quota, use /reserve to dynamically set reservation, and maybe use /weights
to set weight, etc., and use the unified endpoint /roles to show all
role-related information. That way, do we need to defer the function to query
quota with /quota after using /roles to show quota information of a role?
> Change /roles endpoint to include quotas, weights, reserved resources?
> ----------------------------------------------------------------------
>
> Key: MESOS-4097
> URL: https://issues.apache.org/jira/browse/MESOS-4097
> Project: Mesos
> Issue Type: Improvement
> Reporter: Neil Conway
> Labels: mesosphere, quota, reservations, roles
>
> MESOS-4085 changes the behavior of the {{/roles}} endpoint: rather than
> listing all the explicitly defined roles, we will now only list those roles
> that have one or more registered frameworks.
> As suggested by [~alexr] in code review, this could be improved -- an
> operator might reasonably expect to see all the roles that have
> * non-default weight
> * non-default quota
> * non-default ACLs?
> * any static or dynamically reserved resources
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
