Alex, Implementing your own containerizer totally makes sense. The containerizer interface can be modulized and your own containerizer can be implemented as a module. Please take a look at the module documentation <https://github.com/apache/mesos/blob/master/docs/modules.md>. From what I can tell, implementing your own containerizer as a module will definitely be simpler than an external solution.
I assume we would have to implement it in cpp, Most likely because that's the most straightforward way. Other languages are also possible (e.g., using JNI for Java). it might require recompiling (parts of) Mesos, some other things? No. With modules, you don't have to. Let me know if you have any further questions! - Jie On Thu, Oct 8, 2015 at 10:44 AM, Alex Glikson <glik...@il.ibm.com> wrote: > Actually we have been thinking to implement our own containerizer, and the > option to use ECP seemed attractive. > Can you, please, elaborate on the implications of having our own > containerizer without ECP? I assume we would have to implement it in cpp, > it might require recompiling (parts of) Mesos, some other things? > > Thanks, > Alex > > > > > From: Jie Yu <yujie....@gmail.com> > To: mesos <d...@mesos.apache.org>, "user@mesos.apache.org" < > user@mesos.apache.org> > Date: 08/10/2015 03:12 AM > Subject: Removing external containerizer from code base > ------------------------------ > > > > Hey guys, > > Per discussion in MESOS-3370 > <https://issues.apache.org/jira/browse/MESOS-3370>, I'll start removing > the > external containerizer and cleaning up the relevant code. > > Please let me know if you have any concern. Thanks! > > - Jie > > >
