[jira] [Updated] (MESOS-6631) Disallow frameworks from modifying FrameworkInfo.roles.

2017-01-25 Thread Michael Park (JIRA)

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

Michael Park updated MESOS-6631:

Shepherd: Michael Park  (was: Benjamin Mahler)

> Disallow frameworks from modifying FrameworkInfo.roles.
> ---
>
> Key: MESOS-6631
> URL: https://issues.apache.org/jira/browse/MESOS-6631
> Project: Mesos
>  Issue Type: Task
>  Components: master
>Reporter: Benjamin Mahler
>Assignee: Benjamin Bannier
>
> In "phase 1" of the multi-role framework support, we want to preserve the 
> existing behavior of single-role framework support in that we disallow 
> frameworks from modifying their role.
> With multi-role framework support, we will initially disallow frameworks from 
> modifying the roles field. Note that in the case that the master has failed 
> over but the framework hasn't re-registered yet, we will use the framework 
> info from the agents to disallow changes to the roles field. We will treat 
> {{FrameworkInfo.roles}} as a set rather than a list, so ordering does not 
> matter for equality.
> One difference between {{role}} and {{roles}} is that for {{role}} 
> modification, we ignore it. But, with {{roles}} modification, since this is a 
> new feature, we can disallow it by rejecting the framework subscription.
> Later, in phase 2, we will allow frameworks to modify their roles, see 
> MESOS-6627.



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


[jira] [Updated] (MESOS-6631) Disallow frameworks from modifying FrameworkInfo.roles.

2017-01-06 Thread Benjamin Bannier (JIRA)

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

Benjamin Bannier updated MESOS-6631:

Sprint: Mesosphere Sprint 49

> Disallow frameworks from modifying FrameworkInfo.roles.
> ---
>
> Key: MESOS-6631
> URL: https://issues.apache.org/jira/browse/MESOS-6631
> Project: Mesos
>  Issue Type: Task
>  Components: master
>Reporter: Benjamin Mahler
>Assignee: Benjamin Bannier
>
> In "phase 1" of the multi-role framework support, we want to preserve the 
> existing behavior of single-role framework support in that we disallow 
> frameworks from modifying their role.
> With multi-role framework support, we will initially disallow frameworks from 
> modifying the roles field. Note that in the case that the master has failed 
> over but the framework hasn't re-registered yet, we will use the framework 
> info from the agents to disallow changes to the roles field. We will treat 
> {{FrameworkInfo.roles}} as a set rather than a list, so ordering does not 
> matter for equality.
> One difference between {{role}} and {{roles}} is that for {{role}} 
> modification, we ignore it. But, with {{roles}} modification, since this is a 
> new feature, we can disallow it by rejecting the framework subscription.
> Later, in phase 2, we will allow frameworks to modify their roles, see 
> MESOS-6627.



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


[jira] [Updated] (MESOS-6631) Disallow frameworks from modifying FrameworkInfo.roles.

2016-11-22 Thread Benjamin Mahler (JIRA)

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

Benjamin Mahler updated MESOS-6631:
---
Description: 
In "phase 1" of the multi-role framework support, we want to preserve the 
existing behavior of single-role framework support in that we disallow 
frameworks from modifying their role.

With multi-role framework support, we will initially disallow frameworks from 
modifying the roles field. We will treat {{FrameworkInfo.roles}} as a set 
rather than a list, so ordering does not matter for equality.

One difference between {{role}} and {{roles}} is that for {{role}} 
modification, we ignore it. But, with {{roles}} modification, since this is a 
new feature, we can disallow it by rejecting the framework subscription.

Later, in phase 2, we will allow frameworks to modify their roles, see 
MESOS-6627.

  was:
In "phase 1" of the multi-role framework support, we want to preserve the 
existing behavior of single-role framework support in that we disallow 
frameworks from modifying their role.

With multi-role framework support, we will initially disallow frameworks from 
modifying the roles field. We will treat {{FrameworkInfo.roles}} as a set 
rather than a list, so ordering does not matter for equality.

Later, in phase 2, we will allow frameworks to modify their roles, see 
MESOS-6627.


> Disallow frameworks from modifying FrameworkInfo.roles.
> ---
>
> Key: MESOS-6631
> URL: https://issues.apache.org/jira/browse/MESOS-6631
> Project: Mesos
>  Issue Type: Task
>  Components: master
>Reporter: Benjamin Mahler
>
> In "phase 1" of the multi-role framework support, we want to preserve the 
> existing behavior of single-role framework support in that we disallow 
> frameworks from modifying their role.
> With multi-role framework support, we will initially disallow frameworks from 
> modifying the roles field. We will treat {{FrameworkInfo.roles}} as a set 
> rather than a list, so ordering does not matter for equality.
> One difference between {{role}} and {{roles}} is that for {{role}} 
> modification, we ignore it. But, with {{roles}} modification, since this is a 
> new feature, we can disallow it by rejecting the framework subscription.
> Later, in phase 2, we will allow frameworks to modify their roles, see 
> MESOS-6627.



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