RE: Support for tasks groups aka pods in Mesos

Thanks for the clarification – I’ll try to dig into this and use execute.cpp as a starting point for my problem… Kind Regards, Hubert From: Guangya Liu [mailto:gyliu...@gmail.com] Sent: Mittwoch, 21. September 2016 09:19 To: u...@mesos.apache.org Cc: dev; Vinod Kone Subject: Re: Support for

Re: mesos git commit: Fixed a typo in `docker_containerizer_tests.cpp`.

Thanks for fixing typos on the go Qian, details matter. I've decided I share with you a lifehack I use : ) Every time I encounter a typo, I assume it has been copy-pasted, so I grep the whole folder for a misspelled word and fix all occurrences in one shot to minimize the churn. For example,

Re: Support for tasks groups aka pods in Mesos

The answer is No, the taskGroup can be treated as Pod in Kubernetes, it will be a set of containers co-located and co-managed on an agent that share some resources (e.g., network namespace, volumes). For your case, you may want to split your 50 tasks to small task groups. Also the `execute` cli

Coverity Scan: Analysis completed for Mesos

Your request for analysis of Mesos has been completed successfully. The results are available at

RE: Support for tasks groups aka pods in Mesos

Hi, Very cool feature. I’ve seen some recent changes (MESOS-6096) in the mesos-execute cli supporting grouped tasks which spawns the task-group on an arbitrary or specified agent node. Tested this yesterday and it works great. But if the task