[
https://issues.apache.org/jira/browse/MESOS-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498840#comment-14498840
]
David Greenberg commented on MESOS-2449:
----------------------------------------
I've added an issue to this Epic that describe a late-binding focused design
for this construct, based on the use cases I've seen for it on my clusters.
> 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
>
> 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)
