You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jay Guo (JIRA)" <ji...@apache.org> on 2017/04/18 07:58:41 UTC
[jira] [Updated] (MESOS-7293) Refactor quota and weight to be
stored and managed by roles
[ https://issues.apache.org/jira/browse/MESOS-7293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jay Guo updated MESOS-7293:
---------------------------
Description: Currently {{weight}} and {{quota}} are stored as separate hashmap as {{roles}} in master, even though they are actually attributes of roles. Having them stored and managed by {{Role}} make it easier to fetch aggregated role-related information (rendering endpoint response), and the logic would be more clear. It could potentially make authZ simpler as well. (was: Currently {{weight}} and {{quota}} are stored as separate hashmap as {{roles}} in master, even though they are actually attributes of roles. Having them stored and managed by {{Role}} make it easier to fetch aggregated role-related information, and the logic would be more clear. It could potentially make authZ simpler as well.)
> Refactor quota and weight to be stored and managed by roles
> -----------------------------------------------------------
>
> Key: MESOS-7293
> URL: https://issues.apache.org/jira/browse/MESOS-7293
> Project: Mesos
> Issue Type: Bug
> Components: master
> Reporter: Jay Guo
>
> Currently {{weight}} and {{quota}} are stored as separate hashmap as {{roles}} in master, even though they are actually attributes of roles. Having them stored and managed by {{Role}} make it easier to fetch aggregated role-related information (rendering endpoint response), and the logic would be more clear. It could potentially make authZ simpler as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)