You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Jie Yu <yu...@gmail.com> on 2015/10/08 02:12:31 UTC
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
Re: Removing external containerizer from code base
Posted by Alex Glikson <GL...@il.ibm.com>.
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 <yu...@gmail.com>
To: mesos <de...@mesos.apache.org>, "user@mesos.apache.org"
<us...@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
Re: Removing external containerizer from code base
Posted by Brian Candler <b....@pobox.com>.
On 08/10/2015 19:04, Kapil Arya wrote:
> I don't know all the details, but I guess, depending upon the exact
> interface, it might be possible to have a C++ wrapper around a non-C++
> containerizer module. In a very naive approach, one simply fork/execs
> the "external" non-C++ containerizer script/program.
... and sends instructions to it. Which is, as far as I can see, what
the external containerizer does.
Re: Removing external containerizer from code base
Posted by Kapil Arya <ka...@mesosphere.io>.
On Thu, Oct 8, 2015 at 1:57 PM, Jie Yu <yu...@gmail.com> wrote:
> 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).
>
I don't know all the details, but I guess, depending upon the exact
interface, it might be possible to have a C++ wrapper around a non-C++
containerizer module. In a very naive approach, one simply fork/execs the
"external" non-C++ containerizer script/program.
>
> 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 <GL...@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 <yu...@gmail.com>
> > To: mesos <de...@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
> >
> >
> >
>
Re: Removing external containerizer from code base
Posted by Alex Glikson <GL...@il.ibm.com>.
Kapil Arya <ka...@mesosphere.io> wrote on 08/10/2015 09:21:14 PM:
> On Thu, Oct 8, 2015 at 2:19 PM, Jie Yu <yu...@gmail.com> wrote:
>
> > but I don't see 'containerizer' as one of the supported module types
listed
> > > in the documentation.. Can you, please, clarify?
> >
> >
> > Not right now, but should be very trivial to do. Kapil or I can
definitely
> > help with this.
>
> +1
Excellent! Would appreciate some guidelines then, in whatever format makes
sense (and/or an example). Maybe replacing the code/guidelines to use ECP
:-)
Thanks,
Alex
Re: Removing external containerizer from code base
Posted by Kapil Arya <ka...@mesosphere.io>.
On Thu, Oct 8, 2015 at 2:19 PM, Jie Yu <yu...@gmail.com> wrote:
> Alex,
>
> but I don't see 'containerizer' as one of the supported module types listed
> > in the documentation.. Can you, please, clarify?
>
>
> Not right now, but should be very trivial to do. Kapil or I can definitely
> help with this.
>
+1
>
> - Jie
>
> On Thu, Oct 8, 2015 at 11:15 AM, Alex Glikson <GL...@il.ibm.com> wrote:
>
> > Thanks Jie, this sounds promising, but I don't see 'containerizer' as one
> > of the supported module types listed in the documentation..
> > Can you, please, clarify?
> >
> > Thanks,
> > Alex
> >
> >
> >
> >
> > From: Jie Yu <yu...@gmail.com>
> > To: user@mesos.apache.org
> > Cc: dev <de...@mesos.apache.org>
> > Date: 08/10/2015 08:57 PM
> > Subject: Re: Removing external containerizer from code base
> >
> >
> >
> > 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 <GL...@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 <yu...@gmail.com>
> > > To: mesos <de...@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
> > >
> > >
> > >
> >
> >
> >
> >
>
Re: Removing external containerizer from code base
Posted by Jie Yu <yu...@gmail.com>.
Alex,
but I don't see 'containerizer' as one of the supported module types listed
> in the documentation.. Can you, please, clarify?
Not right now, but should be very trivial to do. Kapil or I can definitely
help with this.
- Jie
On Thu, Oct 8, 2015 at 11:15 AM, Alex Glikson <GL...@il.ibm.com> wrote:
> Thanks Jie, this sounds promising, but I don't see 'containerizer' as one
> of the supported module types listed in the documentation..
> Can you, please, clarify?
>
> Thanks,
> Alex
>
>
>
>
> From: Jie Yu <yu...@gmail.com>
> To: user@mesos.apache.org
> Cc: dev <de...@mesos.apache.org>
> Date: 08/10/2015 08:57 PM
> Subject: Re: Removing external containerizer from code base
>
>
>
> 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 <GL...@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 <yu...@gmail.com>
> > To: mesos <de...@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
> >
> >
> >
>
>
>
>
Re: Removing external containerizer from code base
Posted by Alex Glikson <GL...@il.ibm.com>.
Thanks Jie, this sounds promising, but I don't see 'containerizer' as one
of the supported module types listed in the documentation..
Can you, please, clarify?
Thanks,
Alex
From: Jie Yu <yu...@gmail.com>
To: user@mesos.apache.org
Cc: dev <de...@mesos.apache.org>
Date: 08/10/2015 08:57 PM
Subject: Re: Removing external containerizer from code base
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 <GL...@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 <yu...@gmail.com>
> To: mesos <de...@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
>
>
>
Re: Removing external containerizer from code base
Posted by Kapil Arya <ka...@mesosphere.io>.
On Thu, Oct 8, 2015 at 1:57 PM, Jie Yu <yu...@gmail.com> wrote:
> 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).
>
I don't know all the details, but I guess, depending upon the exact
interface, it might be possible to have a C++ wrapper around a non-C++
containerizer module. In a very naive approach, one simply fork/execs the
"external" non-C++ containerizer script/program.
>
> 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 <GL...@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 <yu...@gmail.com>
> > To: mesos <de...@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
> >
> >
> >
>
Re: Removing external containerizer from code base
Posted by Jie Yu <yu...@gmail.com>.
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 <GL...@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 <yu...@gmail.com>
> To: mesos <de...@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
>
>
>
Re: Removing external containerizer from code base
Posted by Jie Yu <yu...@gmail.com>.
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 <GL...@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 <yu...@gmail.com>
> To: mesos <de...@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
>
>
>
Re: Removing external containerizer from code base
Posted by Alex Glikson <GL...@il.ibm.com>.
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 <yu...@gmail.com>
To: mesos <de...@mesos.apache.org>, "user@mesos.apache.org"
<us...@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
Re: Removing external containerizer from code base
Posted by Jie Yu <yu...@gmail.com>.
FYI, I created this ticket to track
https://issues.apache.org/jira/browse/MESOS-3709
Kapil, do you want to pick this up? I can pick this up as well once I
finish a few stuff on my hand.
On Mon, Oct 12, 2015 at 12:50 AM, Timothy Chen <tn...@gmail.com> wrote:
> Yes it can be a module.
>
> Tim
>
> On Mon, Oct 12, 2015 at 12:04 AM, tommy xiao <xi...@gmail.com> wrote:
> > HI Jie Yu,
> >
> > https://issues.apache.org/jira/browse/MESOS-3435 in this proposal, i
> sure
> > the hyper is new containerizer, Does this can implement as a module?
> >
> > 2015-10-08 8:12 GMT+08:00 Jie Yu <yu...@gmail.com>:
> >
> >> 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
> >>
> >
> >
> >
> > --
> > Deshi Xiao
> > Twitter: xds2000
> > E-mail: xiaods(AT)gmail.com
>
Re: Removing external containerizer from code base
Posted by Timothy Chen <tn...@gmail.com>.
Yes it can be a module.
Tim
On Mon, Oct 12, 2015 at 12:04 AM, tommy xiao <xi...@gmail.com> wrote:
> HI Jie Yu,
>
> https://issues.apache.org/jira/browse/MESOS-3435 in this proposal, i sure
> the hyper is new containerizer, Does this can implement as a module?
>
> 2015-10-08 8:12 GMT+08:00 Jie Yu <yu...@gmail.com>:
>
>> 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
>>
>
>
>
> --
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
Re: Removing external containerizer from code base
Posted by tommy xiao <xi...@gmail.com>.
HI Jie Yu,
https://issues.apache.org/jira/browse/MESOS-3435 in this proposal, i sure
the hyper is new containerizer, Does this can implement as a module?
2015-10-08 8:12 GMT+08:00 Jie Yu <yu...@gmail.com>:
> 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
>
--
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com