You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Neil Conway (JIRA)" <ji...@apache.org> on 2015/11/23 22:43:11 UTC

[jira] [Updated] (MESOS-3988) Implicit roles

     [ https://issues.apache.org/jira/browse/MESOS-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neil Conway updated MESOS-3988:
-------------------------------
          Sprint: Mesosphere Sprint 23
    Story Points: 10

> Implicit roles
> --------------
>
>                 Key: MESOS-3988
>                 URL: https://issues.apache.org/jira/browse/MESOS-3988
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Neil Conway
>              Labels: mesosphere, roles
>
> At present, Mesos uses a static list of roles that are configured when the master starts up. This places some severe limitations on how roles can be used (e.g., changing the set of roles requires restarting all the masters).
> As an alternative (or a precursor) to implementing full-blown dynamic roles, we could instead relax the concept of roles, so that:
> * frameworks can register with any role (subject to ACLs/authz)
> * reservations can be made for any role
> Open questions, at least to me:
> * This would mean weights cannot be configured dynamically. Is that okay?
> * Is this feature useful enough without dynamic ACL changes?
> * If we implement this (+ dynamic ACLs), do we also need dynamic roles?



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