[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesos-issues
Subject:    [jira] [Updated] (MESOS-3177) Dynamic roles/weights configuration at runtime
From:       "Benjamin Hindman (JIRA)" <jira () apache ! org>
Date:       2015-10-28 22:41:28
Message-ID: JIRA.12850379.1438288864000.89857.1446072088022 () Atlassian ! JIRA
[Download RAW message or body]


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

Benjamin Hindman updated MESOS-3177:
------------------------------------
    Epic Name: Dynamic roles/weights

> Dynamic roles/weights configuration at runtime
> ----------------------------------------------
> 
> Key: MESOS-3177
> URL: https://issues.apache.org/jira/browse/MESOS-3177
> Project: Mesos
> Issue Type: Epic
> Components: master, slave
> Reporter: Cody Maloney
> Assignee: Yong Qiao Wang
> 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)


[prev in list] [next in list] [prev in thread] [next in thread]