Return-Path: X-Original-To: apmail-mesos-user-archive@www.apache.org Delivered-To: apmail-mesos-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7D7D911D62 for ; Wed, 23 Apr 2014 23:58:53 +0000 (UTC) Received: (qmail 75909 invoked by uid 500); 23 Apr 2014 23:58:46 -0000 Delivered-To: apmail-mesos-user-archive@mesos.apache.org Received: (qmail 75842 invoked by uid 500); 23 Apr 2014 23:58:46 -0000 Mailing-List: contact user-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@mesos.apache.org Delivered-To: mailing list user@mesos.apache.org Received: (qmail 75831 invoked by uid 99); 23 Apr 2014 23:58:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2014 23:58:46 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of diptanuc@gmail.com designates 209.85.160.179 as permitted sender) Received: from [209.85.160.179] (HELO mail-yk0-f179.google.com) (209.85.160.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2014 23:58:42 +0000 Received: by mail-yk0-f179.google.com with SMTP id 9so1477033ykp.10 for ; Wed, 23 Apr 2014 16:58:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=5d4RNtshcbts5SQgY8f+6OHj8WGtj/hHcgixOnqmuaM=; b=1APUPGJh0xxt/dH/dUBssMr9r4UoP1OphgIWGbG2QajgMjwd9zaLxFVO1FxPJ23Bq4 RC/zyloqHKcLKkVe06XDjh+dmlIOMsvVLwtXZ7wWyw9r1uMcDDGEaMC233TcPD6BC0w0 kwEaH0gqzpzuqLQHspLQBO9tlAmYvIzZRIgG4jo1b9gonPKegR/nuPnHX1lJ0VrdX9zC YuPteZ/DXV0lHnS+5hHM/iZNFQ8IuNYpj51VYyib0TUV3tgx9n4TsSOpZAPPrBroB1Ea +tctXKWIHWtmchYlt58LX/yxMLTOYkTZc6KhRiXdwJ4ZXxufySHw+EOWkH7RNS9B+8A+ Y7nA== MIME-Version: 1.0 X-Received: by 10.236.87.139 with SMTP id y11mr74277370yhe.27.1398297499237; Wed, 23 Apr 2014 16:58:19 -0700 (PDT) Received: by 10.170.72.131 with HTTP; Wed, 23 Apr 2014 16:58:19 -0700 (PDT) In-Reply-To: References: Date: Wed, 23 Apr 2014 16:58:19 -0700 Message-ID: Subject: Re: External Containererization API From: Diptanu Choudhury To: user@mesos.apache.org Content-Type: multipart/alternative; boundary=20cf301b63e9bb808d04f7be8180 X-Virus-Checked: Checked by ClamAV on apache.org --20cf301b63e9bb808d04f7be8180 Content-Type: text/plain; charset=UTF-8 Hi, I am working on a containerizer similar to Deimos, and uses that Docker as well. I rolled out a custom executor for supporting docker and also to do things like register services inside containers with our service discovery platform and get logs out of containers into stderr and stdout of the mesos task. The new APIs around containerization would make it easier to pass information to the executors and I want to adopt the new APIs when they are released. On Wed, Apr 23, 2014 at 4:37 PM, Adam Bordelon wrote: > Also see https://gist.github.com/solidsnack/10944095 for SolidSnack's > getting-started-with-deimos if you want to try out Deimos (uses > Mesosphere's custom branch including r/17567) > > > On Wed, Apr 23, 2014 at 4:08 PM, Niklas Nielsen wrote: > >> Hey Diptanu, >> >> MESOS-816 (and dependent patches) are still in the works but getting >> close to land. These reviews (https://reviews.apache.org/r/17567/ and >> https://reviews.apache.org/r/20080/) are (more or less) the last two >> outstanding pieces. The first external containerizer which use the new API >> can be found here: https://github.com/mesosphere/deimos >> >> Are you writing a new isolator in the context of the old isolation >> architecture, or targeted the new containerizer API? >> >> Cheers, >> Niklas >> >> >> >> On 23 April 2014 15:59, Diptanu Choudhury wrote: >> >>> Hi, >>> >>> With Mesos 18 release, has support for passing ContainerInfo[per >>> MESOS-816] to slaves etc been released in the Java API? >>> >>> I am working on a docker isolator right now, and the only way I can >>> pass information to the executor right now is via the executor data. I am >>> wondering if Mesos 18 had anything to offer around that? I see a >>> ContainerID protobuf message but not sure what that is for. >>> >>> -- >>> Thanks, >>> Diptanu Choudhury >>> Web - www.linkedin.com/in/diptanu >>> Twitter - @diptanu >>> >> >> > -- Thanks, Diptanu Choudhury Web - www.linkedin.com/in/diptanu Twitter - @diptanu --20cf301b63e9bb808d04f7be8180 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I am working on a containerizer sim= ilar to Deimos, and uses that Docker as well. I rolled out a custom executo= r for supporting docker and also to do things like register services inside= containers with our service discovery platform and get logs out of contain= ers into stderr and stdout of the mesos task. The new APIs around container= ization would make it easier to pass information to the executors and I wan= t to adopt the new APIs when they are released.


On Wed,= Apr 23, 2014 at 4:37 PM, Adam Bordelon <adam@mesosphere.io> wrote:
Also see https://gist.github= .com/solidsnack/10944095 for SolidSnack's getting-started-with-deim= os if you want to try out Deimos (uses Mesosphere's custom branch inclu= ding r/17567)

On Wed, Apr 23, 2014 at 4:08 PM, Niklas Ni= elsen <niklas@mesosphere.io> wrote:
Hey Diptanu,

=
MESOS-816 = (and dependent patches) are still in the works but getting close to land. T= hese reviews (https://reviews.apache.org/r/17567/ and https://reviews.apache.org/r= /20080/) are (more or less) the last two outstanding pieces. The first = external containerizer which use the new API can be found here: https://github.com/= mesosphere/deimos

Are you writing a new isolator in the context of = the old isolation architecture, or targeted the new containerizer API?

Cheers,
Niklas



On 23 April 2= 014 15:59, Diptanu Choudhury <diptanuc@gmail.com> wrote:
Hi,

With Mesos 18 release, has support = for passing ContainerInfo[per MESOS-816] to slaves etc been released in the= Java API?

I am working on a docker=C2=A0isolator right now, and the= only way I can pass information to the executor right now is via the execu= tor data. I am wondering if Mesos 18 had anything to offer around that? I s= ee a ContainerID protobuf message but not sure what that is for.

--
Thanks,
Diptanu ChoudhuryWeb -=C2=A0www.linkedin.com/in/diptanu
Twitter -=C2=A0@diptanu





--
=
Thanks,
Diptanu Choudhury
Web -=C2=A0www.linkedin.com/in/dipt= anu
Twitter -=C2=A0@di= ptanu
--20cf301b63e9bb808d04f7be8180--