[ https://issues.apache.org/jira/browse/MESOS-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563634#comment-15563634 ]
Anand Mazumdar commented on MESOS-2449: --------------------------------------- MESOS-6298 might need a little more work since the tech-debt cleanup is not that straight-forward. I would move it to the improvements epic. > 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)