[
https://issues.apache.org/jira/browse/MESOS-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-6636:
-----------------------------------
Description:
With support for multi-role frameworks, we need to make sure that individual
tasks and executors cannot mix roles. Likewise, we do not want to allow a
scheduler to make a reservation or create a volume based on resources with
different allocated roles.
We will however allow tasks from one role to run on executors from another role.
Note that this is already prevented via disallowing schedulers to apply
operations to offers with different allocation infos, but this more explicit
validation can be added to prevent accidentally allowing mixing within
tasks/executors/reservations/volumes should we change the higher level offer
mixing validation.
was:
With support for multi-role frameworks, we need to make sure that individual
tasks and executors cannot mix roles. Likewise, we do not want to allow a
scheduler to make a reservation based on resources with different allocated
roles.
We will however allow tasks from one role to run on executors from another role.
Summary: Validate that tasks / executors / reservations / volumes do
not mix Resource.allocation_info.roles. (was: Validate that tasks / executors
/ reservations do not mix Resource.allocation_info.roles.)
> Validate that tasks / executors / reservations / volumes do not mix
> Resource.allocation_info.roles.
> ---------------------------------------------------------------------------------------------------
>
> Key: MESOS-6636
> URL: https://issues.apache.org/jira/browse/MESOS-6636
> Project: Mesos
> Issue Type: Task
> Components: master
> Reporter: Benjamin Mahler
> Assignee: Jay Guo
> Fix For: 1.3.0
>
>
> With support for multi-role frameworks, we need to make sure that individual
> tasks and executors cannot mix roles. Likewise, we do not want to allow a
> scheduler to make a reservation or create a volume based on resources with
> different allocated roles.
> We will however allow tasks from one role to run on executors from another
> role.
> Note that this is already prevented via disallowing schedulers to apply
> operations to offers with different allocation infos, but this more explicit
> validation can be added to prevent accidentally allowing mixing within
> tasks/executors/reservations/volumes should we change the higher level offer
> mixing validation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
