[
https://issues.apache.org/jira/browse/MESOS-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022024#comment-15022024
]
Guangya Liu commented on MESOS-3988:
------------------------------------
One concern for this is that the role will be out of control in mesos cluster
because the end user may input some wrong words for roles.
If we can go with this direction, for the weight issues, perhaps we can enable
framework set roles plus weight, i,e, "role:weight", and we can define some
policy to decide how to get the weight if same roles configured different
weights, such as {{sum(weight)/n}} or using the biggest or smallest weight etc.
> 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)
