[jira] [Comment Edited] (MESOS-922) Containerizer to support launching tasks by TaskInfo

["Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910742#comment-13910742 ] 

Niklas Quarfot Nielsen edited comment on MESOS-922 at 3/28/14 8:50 PM:
-----------------------------------------------------------------------

https://reviews.apache.org/r/18403
https://reviews.apache.org/r/19795/


was (Author: nnielsen):
WIP in https://reviews.apache.org/r/18403

> Containerizer to support launching tasks by TaskInfo
> ----------------------------------------------------
>
>                 Key: MESOS-922
>                 URL: https://issues.apache.org/jira/browse/MESOS-922
>             Project: Mesos
>          Issue Type: Improvement
>          Components: isolation
>            Reporter: Ian Downes
>            Assignee: Niklas Quarfot Nielsen
>             Fix For: 0.19.0
>
>
> Currently the slave runs tasks by using an existing executor or by launching a new executor. When a task's TaskInfo doesn't specify the executor with an ExecutorInfo (has a CommandInfo instead) the slave will create an ExecutorInfo specifying the mesos-command executor.
> The decision on how to launch a task could instead be delegated to the containerizer and the TaskInfo would be passed unmodifed. This would have the following advantages:
> 1) The containerizer can decide on the executor to run the task, either the mesos-executor or a specialized executor appropriate for the containerization implementation. Furthermore, the containerizer can allocate appropriate additional resources for the executor.
> 2) The containerizer can see the task's resources and can allocate these when the executor is launched. This is useful for such containerizer implementations as KVM where it is harder to dynamically adjust a containerized executor's resources. This is most applicable when the executor will only run a single task.



--
This message was sent by Atlassian JIRA
(v6.2#6252)