You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Alexander Rukletsov (JIRA)" <ji...@apache.org> on 2016/10/10 12:28:20 UTC

[jira] [Updated] (MESOS-2449) Support group of tasks (Pod) constructs and API in Mesos

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

Alexander Rukletsov updated MESOS-2449:
---------------------------------------
    Fix Version/s:     (was: 1.1.0)

> Support group of tasks (Pod) constructs and API in Mesos
> --------------------------------------------------------
>
>                 Key: MESOS-2449
>                 URL: https://issues.apache.org/jira/browse/MESOS-2449
>             Project: Mesos
>          Issue Type: Epic
>            Reporter: Timothy Chen
>              Labels: mesosphere
>
> There is a common need among different frameworks, that wants to start a group of tasks that are either depend or co-located with each other.
> Although a framework can schedule individual tasks within the same offer and slave id, it doesn't have a way to describe dependencies, failure policies (if one of the task failed), network setup, and group container information, etc.
> Want to create a epic to start the discussion around the requirements folks need, and see where we can lead this.



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