[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954553#comment-14954553 ] Yong Qiao Wang commented on MESOS-3177: --- Maybe we can consider taking quota as a parameter of role, then it does not needs to add some separated HTTP endpoints for quota management, and should use the role management HTTP endpoints for quota configuration. [~alex-mesos], some thoughts for this? > 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: 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934901#comment-14934901 ] Adam B commented on MESOS-3177: --- The tricky part with your use case description, [~air], is that a framework registers with a single role, so you're either asking if a) a framework can register with a new, unrecognized role b) a framework can change its role after registration c) a framework can create an additional role and use it. And none of those are going to be recommended/possible after just this ticket. a) Since the total number of roles affects each role's fair share of the cluster, it should be up to the cluster admin to add new roles, not the frameworks. We could add a flag/ACL to allow frameworks to register with unrecognized roles, but it would be disabled by default. (I can also imagine typos wreaking havoc.) b) Even with the progress we've already made on updating the simpler fields in FrameworkInfo upon reregistration, updating a framework's role is the most complex. See https://cwiki.apache.org/confluence/display/MESOS/Design+doc:+Updating+Framework+Info c) Even assuming that we've enabled an ACL to allow (specific) frameworks to create new roles, we still have a long way to go before we can support multi-role frameworks. See MESOS-1763 > 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: 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900287#comment-14900287 ] Yong Qiao Wang commented on MESOS-3177: --- Thanks [~thomasr], I think this requirement should be covered by Quota proposal. This ticket should only focus on the roles/weights add/remove/update. > 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: 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14880720#comment-14880720 ] Alexander Rukletsov commented on MESOS-3177: I think this ticket is more about adding and removing roles dynamically, while quota is about resource guarantees associated with roles. > 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 > 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14880719#comment-14880719 ] Alexander Rukletsov commented on MESOS-3177: I think this ticket is more about adding and removing roles dynamically, while quota is about resource guarantees associated with roles. > 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 > 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14877358#comment-14877358 ] Marco Massenzio commented on MESOS-3177: By the sound of it (and we can dig in further detail) this sounds like the ["Quota" proposal|https://docs.google.com/document/d/16iRNmziasEjVOblYp5bbkeBZ7pnjNlaIzPQqMTHQ-9I/edit?usp=sharing], which is currently being led by [~alexr] and others. Then again, I may be missing important bits, but skimming quickly through the "User Stories" it seems to cover the one requested here? > 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 > 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14877342#comment-14877342 ] Thomas Rampelberg commented on MESOS-3177: -- I don't have any good suggestions for design, but I'd like to +1 [~air]'s user story. That's exactly what I'd like to see as well. The full user story: - As a framework user I would like to dynamically create roles to associate resources with so that I can guarantee resources being available on the cluster for my specific application. > 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 > 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804888#comment-14804888 ] Yong Qiao Wang commented on MESOS-3177: --- 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804289#comment-14804289 ] Cody Maloney commented on MESOS-3177: - Currently the mesos master doesn't keep track of roles it knows of explicitly, just roles which it says it should know about passed in via the flag. Storing them in the replicated log would be my preferred place to put / persist them. If they are persisted in the repliacted log and that is the authoritative source for them, I'd rather not have them be flags to the mesos master anymore, as after first mesos master start those flags would be meaningless and lead to a potentially bad user experience (I set the flags on mesos master but they aren't applying!?!?!). There is a `mesos-log` command that already exists, and it's been design discussed some that initialization of the replicated log shouldn't be implicit in master startup (Can potentially lead to bad cluster/error cases for some node replacement scenarios). I would suggest only allowing adding roles in v1. Removing roles will require revoking offers, which sort of exists with inverse offers that recently became available, but is going to be a lot of engineering. For other things you're going to need a Mesos Shepherd going forward for more design review, building out a proper design proposal, and getting things landed in time. > 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791661#comment-14791661 ] Yong Qiao Wang commented on MESOS-3177: --- In addition, When we remove an existing role, we also need to call related slave to release the resources which reserved by that role before. [~cmaloney], any thoughts 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[
https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791639#comment-14791639
]
Yong Qiao Wang commented on MESOS-3177:
---
Thanks [~cmaloney] for your kindly reply. I have some questions and comments
for your above thinks:
1. As we know, currently roles and weights are not persist in the replicated
log, do you mean that we should persist them?
2. If yes for #1, then I think the initial replicated log for roles and weights
are created when Mesos master starts in the first time, and the content of the
log should be the roles and weights specified by --roles and --weights flag. is
it right?
3. For add a new role "add_role", in code level, there are two places only need
to change:
Add a new HTTP endpoint in master.cpp to add a new item in
{code}
hashmap roles;
{code}
and call allocator to update the RoleSorter;
4. For remove an existing role "remove_role", I think it should ensure the
following things before remove an existing role:
- Kill all tasks which using the resources reserved by this role;
- Shutdown all executors which using the resources reserved by this role;
- Unreserve the dynamically reserved resources for this role;
- Destory the persisted volumn which using the resources reserved by this
role;
- Remove all frameworks which associated with this role?
- Remove the related ACL of this role;
5. Do you mean the authorization rather than authentication in above comments?
[~cmaloney], Welcome your any comments for above thinks of me.
> 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740398#comment-14740398 ] Cody Maloney commented on MESOS-3177: - There hasn't been any design documentation building / development so far. In my mind I've been thinking it of a "Before you start the mesos masters, you create the initial replicated log state which contains the first set of roles and weights to operate with". Then from that point on mesos has a "add_role" and "remove_role" endpoints to manage them. Even better would be that if you don't have authentication turned on, as mesos sees new roles it just adds them (And as all things with that role disappear it removes them). If authentication is turned on, the authentication mechanism effectively "permanently" owns all the roles it defines (if it's just a static configuration file). If it's a dynamic source / database then the interface to talk about ownership would probably need to get more complicated. > 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738183#comment-14738183 ] Yong Qiao Wang commented on MESOS-3177: --- Hi [~thomasr] and [~cmaloney], are there some latest updates and design docs for this ticket? > 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[ https://issues.apache.org/jira/browse/MESOS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738059#comment-14738059 ] Guangya Liu commented on MESOS-3177: [~air] I think that this epic can cover your case. Once the role is created dynamically, you can use this role directly and there is no difference with other roles. 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)
[jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
[
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)
