Need inputs on running MPI jobs on Mesos

Hello Mesos Devs, I am contributing to Apache Airavata and currently working on extending the support for the science gateways to run MPI jobs on cloud based Mesos clusters. I am looking at mpiexec-mesos and Mesos

Re: A Plan for Mesos Community Syncs

+1 - Thanks MPark! > On Oct 13, 2016, at 10:34 PM, Michael Park wrote: > > I would like to try to get the community syncs back on track. They have not > been organized well recently, and I would like to take ownership of being > the driver/host of the meetings. I think my

Re: A Plan for Mesos Community Syncs

+1 — *Joris Van Remoortere* Mesosphere On Thu, Oct 13, 2016 at 1:38 PM, Vinod Kone wrote: > Huge +1. Thanks for taking ownership of this. > > On Thu, Oct 13, 2016 at 1:34 PM, Michael Park wrote: > > > I would like to try to get the community syncs back

Re: Parallel test runner added

Thanks for pushing this through Benjamin! I understand if you're unable to attend the community sync on the 20th, but would you be able to present this as a demo somehow? maybe via a screencast? MPark On Thu, Oct 13, 2016 at 6:33 PM, Benjamin Mahler wrote: > Great to see

Re: Parallel test runner added

Great to see this Benjamin! Looking forward to seeing the parallel test runner turn green, I'll help file tickets under the epic (I see there are a lot of test failures for me). Once we clear the issues and turn it green, shall we make this the default? I would be in favor of that. Ben On Thu,

Re: Parallel test runner added

This is great, Benjamin! I've used it the whole day today and it is awesome. (It will become insanely great once MESOS-6387 is resolved.) Thanks for everyone who made this happen, also on behalf of my employer : ) Alex. On Thu, Oct 13, 2016 at 11:28 PM, Benjamin Bannier <

Parallel test runner added

Hi, Since most tests in the Mesos, libprocess, and stout test suites can be executed in parallel (the exception being some `ROOT` tests with global side effects in Mesos), we recently added a parallel test runner `support/mesos-gtest-runner.py`. This should allow to potentially significantly

Re: A Plan for Mesos Community Syncs

Huge +1. Thanks for taking ownership of this. On Thu, Oct 13, 2016 at 1:34 PM, Michael Park wrote: > I would like to try to get the community syncs back on track. They have not > been organized well recently, and I would like to take ownership of being > the driver/host of the

A Plan for Mesos Community Syncs

I would like to try to get the community syncs back on track. They have not been organized well recently, and I would like to take ownership of being the driver/host of the meetings. I think my half-involved driving of the meetings have been detrimental in terms of logistics, consistency,

Re: On Mesos versioning and deprecation policy

>How about splitting the unnamed version into explicit v0, v2, and internal? Currently our internal protobuf and v0 protobuf use the same unnamed version protobuf and under the same namespace (`package mesos`). If we are going to split v0 and internal, that requires copy all protobuf files under

Re: Allowing both CommandInfo and ExecutorInfo on TaskInfo

For command task, if its `ExecutorInfo` would set with `CommandExecutor` as well? Some tickets may relate to this. [1]: https://issues.apache.org/jira/browse/MESOS-2330 [2]: https://issues.apache.org/jira/browse/MESOS-527 [3]: https://issues.apache.org/jira/browse/MESOS-5198 On Fri, Oct 14,

Allowing both CommandInfo and ExecutorInfo on TaskInfo

Hi, We are contemplating whether to allow both CommandInfo and ExecutorInfo on TaskInfo (MESOS-6294 ). Currently we only allow one or the other. The motivation is to allow custom executors a more structured way to pass information (e.g, command)