[
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)
