[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights

["Aaron Bell (JIRA)" <ji...@apache.org>]

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

Aaron Bell commented on MESOS-3177:
-----------------------------------

Does this JIRA cover this use case, or should I file a new one?

Support creating roles at runtime: As a developer I want a persistent volume of 10GB. In order for the underlying disk resource to belong exclusively to me, I need to define a role for it {{my-db-01}} and use that role in a new Dynamic Reservation on the host, with size 10GB and role {{my-db-01}}.

> Make Mesos own configuration of roles/weights
> ---------------------------------------------
>
>                 Key: MESOS-3177
>                 URL: https://issues.apache.org/jira/browse/MESOS-3177
>             Project: Mesos
>          Issue Type: Improvement
>          Components: master, slave
>            Reporter: Cody Maloney
>            Assignee: Thomas Rampelberg
>              Labels: mesosphere
>
> All roles and weights must currently be specified up-front when starting Mesos masters currently. In addition, they should be consistent on every master, otherwise unexpected behavior could occur (You can have them be inconsistent for some upgrade paths / changing the set).
> This makes it hard to introduce new groups of machines under new roles dynamically (Have to generate a new master configuration, deploy that, before we can connect slaves with a new role to the cluster).
> Ideally an administrator can manually add / remove / edit roles and have the settings replicated / passed to all masters in the cluster by Mesos. Effectively Mesos takes ownership of the setting, rather than requiring it to be done externally.
> In addition, if a new slave joins the cluster with an unexpected / new role that should just work, making it much easier to introduce machines with new roles. (Policy around whether or not a slave can cause creation of a new role, a given slave can register with a given role, etc. is out of scope, and would be controls in the general registration process).



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