You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Yong Qiao Wang (JIRA)" <ji...@apache.org> on 2015/12/10 03:30:10 UTC

[jira] [Commented] (MESOS-4097) Change /roles endpoint to include quotas, weights, reserved resources?

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

Yong Qiao Wang commented on MESOS-4097:
---------------------------------------

Some concerns as below:
1. we removed RoleInfo in MESOS-4085, but we are going to show RoleInfo (all role-related configuration) by /roles?
2. Currently design should be worse for operator experience, for example, after operator configured the quota for a role with /quota endpoint, and he has to check the configuration with another endpoint ( /roles ) which will return all active roles information and does not query a specified one.


> 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)