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 C8B9318D78 for ; Thu, 8 Oct 2015 17:45:41 +0000 (UTC) Received: (qmail 53244 invoked by uid 500); 8 Oct 2015 17:45:41 -0000 Delivered-To: apmail-mesos-user-archive@mesos.apache.org Received: (qmail 53177 invoked by uid 500); 8 Oct 2015 17:45:40 -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 53167 invoked by uid 99); 8 Oct 2015 17:45:40 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2015 17:45:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 794C1180E04 for ; Thu, 8 Oct 2015 17:45:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.989 X-Spam-Level: ** X-Spam-Status: No, score=2.989 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id cViGMlOn9zp1 for ; Thu, 8 Oct 2015 17:45:29 +0000 (UTC) Received: from e06smtp07.uk.ibm.com (e06smtp07.uk.ibm.com [195.75.94.103]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 91F9E2031C for ; Thu, 8 Oct 2015 17:45:28 +0000 (UTC) Received: from /spool/local by e06smtp07.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 8 Oct 2015 18:45:26 +0100 Received: from d06dlp02.portsmouth.uk.ibm.com (9.149.20.14) by e06smtp07.uk.ibm.com (192.168.101.137) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Thu, 8 Oct 2015 18:45:23 +0100 X-Helo: d06dlp02.portsmouth.uk.ibm.com X-MailFrom: glikson@il.ibm.com X-RcptTo: user@mesos.apache.org Received: from b06cxnps3075.portsmouth.uk.ibm.com (d06relay10.portsmouth.uk.ibm.com [9.149.109.195]) by d06dlp02.portsmouth.uk.ibm.com (Postfix) with ESMTP id 3BA6A2190019 for ; Thu, 8 Oct 2015 18:45:22 +0100 (BST) Received: from d06av08.portsmouth.uk.ibm.com (d06av08.portsmouth.uk.ibm.com [9.149.37.249]) by b06cxnps3075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id t98HjNUC36962494 for ; Thu, 8 Oct 2015 17:45:23 GMT Received: from d06av08.portsmouth.uk.ibm.com (localhost [127.0.0.1]) by d06av08.portsmouth.uk.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id t98HjNIH026419 for ; Thu, 8 Oct 2015 11:45:23 -0600 Received: from d50lp01.ny.us.ibm.com ([146.89.104.207]) by d06av08.portsmouth.uk.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id t98HjMdN024887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 8 Oct 2015 11:45:23 -0600 Message-Id: <201510081745.t98HjMdN024887@d06av08.portsmouth.uk.ibm.com> Received: from /spool/local by d50lp01.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 8 Oct 2015 13:44:32 -0400 Received: from smtp.notes.na.collabserv.com (192.155.248.82) by d50lp01.ny.us.ibm.com (158.87.18.20) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256/256) Thu, 8 Oct 2015 13:44:31 -0400 Received: from /spool/local by smtp.notes.na.collabserv.com with smtp.notes.na.collabserv.com ESMTP for from ; Thu, 8 Oct 2015 17:44:29 -0000 Received: from us1a3-smtp03.a3.dal06.isc4sb.com (10.106.154.94) by smtp.notes.na.collabserv.com (10.106.227.105) with smtp.notes.na.collabserv.com ESMTP; Thu, 8 Oct 2015 17:44:28 -0000 Received: from us1a3-mail105.a3.dal06.isc4sb.com ([10.146.21.201]) by us1a3-smtp03.a3.dal06.isc4sb.com with ESMTP id 2015100817444658-441621 ; Thu, 8 Oct 2015 17:44:46 +0000 In-Reply-To: To: dev@mesos.apache.org Cc: "user@mesos.apache.org" Subject: Re: Removing external containerizer from code base From: "Alex Glikson" Date: Thu, 8 Oct 2015 20:44:26 +0300 References: MIME-Version: 1.0 X-KeepSent: 47011983:3D1EB2A5-C2257ED8:00611FBC; type=4; name=$KeepSent X-Mailer: IBM Notes Release 9.0.1SHF211 December 19, 2013 X-LLNOutbound: False X-Disclaimed: 31111 X-TNEFEvaluated: 1 Content-Type: multipart/alternative; boundary="=_alternative 0061737EC2257ED8_=" x-cbid: 15100817-0029-0000-0000-000004604779 X-IBM-ISS-SpamDetectors: Score=0.49; BY=0; FL=0; FP=0; FZ=0; HX=0; KW=0; PH=0; SC=0.49; ST=0; TS=0; UL=0; ISC= X-IBM-ISS-DetailInfo: BY=3.00004481; HX=3.00000236; KW=3.00000007; PH=3.00000004; SC=3.00000117; SDB=6.00599872; UDB=6.00263140; UTC=2015-10-08 17:44:29 x-cbparentid: 15100817-9900-0000-0000-0000046995FC X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER --=_alternative 0061737EC2257ED8_= Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="US-ASCII" 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=20 containerizer without ECP? I assume we would have to implement it in cpp,=20 it might require recompiling (parts of) Mesos, some other things? Thanks, Alex From: Jie Yu To: mesos , "user@mesos.apache.org"=20 Date: 08/10/2015 03:12 AM Subject: Removing external containerizer from code base Hey guys, Per discussion in MESOS-3370 , I'll start removing=20 the external containerizer and cleaning up the relevant code. Please let me know if you have any concern. Thanks! - Jie --=_alternative 0061737EC2257ED8_= Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="US-ASCII" Actually we have been thinking to implem= ent our own containerizer, and the option to use ECP seemed attractive.<= br>Can you, please, elaborate on the imp= lications 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.jay@gmail.= com>
To: &n= bsp;      mesos <dev@mesos.apache.= org>, "user@mesos.apache.org" <user@mesos.apache.org>
<= font size=3D1 color=3D#5f5f5f face=3D"sans-serif">Date:        08/10/2015 03:12 AM<= br>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 relev= ant code.

Please let me know if you have any concern. Thanks!
- Jie


--=_alternative 0061737EC2257ED8_=--