[
https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804888#comment-14804888
]
Yong Qiao Wang edited comment on MESOS-3177 at 9/18/15 6:07 AM:
----------------------------------------------------------------
Thanks [~cmaloney] for your quickly reply.
[~thomasr], Could you share some ideas to me? if possible, I'd like to work
together with your on the design of this ticket. Thanks!
was (Author: jamesyongqiaowang):
Thanks [~cmaloney] for your quickly reply.
[~thomasr], are your working on this ticket now? If you do not have time on
this now, I want to re-assign this ticket to me, and try to propose a detailed
design for this. Thanks!
> 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)
