Custom docker executor

2015-08-08 Thread Kapil Malik
... posting in a fresh thread Hi, We have a usecase to run multi-user workloads on mesos. Users provide docker images encapsulating application logic, which we (we = say some "Central API") schedule on Chronos / Marathon. However, we need to run some standard pre / post steps for every docker s

Re: Custom docker executor

2015-08-08 Thread Tim Chen
Hi Kapil, What kind of pre/post actions do you like to perform? The community has been contributing hooks that can be performed pre and post container launch, so like to see what your use cases are and perhaps the new hooks can satisfy your need, or maybe even some other way that can already do w

Re: Custom docker executor

2015-08-08 Thread Mike Michel
Hi, we (http://sloppy.io) use https://github.com/ClusterHQ/powerstrip for pre/post hooks and it is running smooth for a long time now. We start many containers a day and powerstrip as a docker proxy is involved in every start. Best, Mike Am 08.08.2015 um 10:01 schrieb Kapil Malik: … pos

RE: Custom docker executor

2015-08-08 Thread Kapil Malik
Hi Tim, Thank you for the quick reply. As I mentioned, we need to run short lived (using Chronos currently) and long lived (using Marathon currently) jobs. While I cannot provide elaborate details, objectively, our requirements include the following – 1. Failure callback for jobs schedul

Re: Custom docker executor

2015-08-08 Thread Tim Chen
Hi Kapil, Thanks these information are very useful. About failure callbacks in Chronos, I agree it's indeed something that Chronos should just provide as it's a common feature for job dependency managers. We can have more discussions on your github issue. Marathon doesn't have a failure callback

RE: Custom docker executor

2015-08-08 Thread Kapil Malik
Hi Tim, Thanks again. Inline. From: Tim Chen [mailto:t...@mesosphere.io] Sent: 08 August 2015 23:23 To: user@mesos.apache.org Subject: Re: Custom docker executor Hi Kapil, Thanks these information are very useful. About failure callbacks in Chronos, I agree it's indeed something that Chronos