Return-Path: 
 <user-return-2138-apmail-mesos-user-archive=mesos.apache.org@mesos.apache.org>
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 8ED69C956
	for <apmail-mesos-user-archive@www.apache.org>;
 Tue,  2 Dec 2014 06:06:48 +0000 (UTC)
Received: (qmail 59384 invoked by uid 500); 2 Dec 2014 06:06:48 -0000
Delivered-To: apmail-mesos-user-archive@mesos.apache.org
Received: (qmail 59334 invoked by uid 500); 2 Dec 2014 06:06:48 -0000
Mailing-List: contact user-help@mesos.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@mesos.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@mesos.apache.org>
List-Post: <mailto:user@mesos.apache.org>
List-Id: <user.mesos.apache.org>
Reply-To: user@mesos.apache.org
Delivered-To: mailing list user@mesos.apache.org
Received: (qmail 59313 invoked by uid 99); 2 Dec 2014 06:06:47 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Dec 2014 06:06:47 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of tnachen@gmail.com designates
 209.85.218.48 as permitted sender)
Received: from [209.85.218.48] (HELO mail-oi0-f48.google.com) (209.85.218.48)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Dec 2014 06:06:44 +0000
Received: by mail-oi0-f48.google.com with SMTP id u20so8499266oif.35
        for <multiple recipients>; Mon, 01 Dec 2014 22:04:08 -0800 (PST)
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
         :cc:content-type;
        bh=cFdoHihVJEJYPziWHyjawlXE8IK6irekS6MYGozrXvE=;
        b=vH3PjlC3ZiGQ0foeyjvAi4IEiVSBmNC2b7Tmjfq+cmkTD80BIUGnoKyy5ojyztHMUu
         HxU2ecSt8vzR0pYHmPpcm5mg4wJpcCCPc+7NRn54fZmHr/FKuq1TRRCpTxgQORXskjaT
         64iSSyzU5s7nJhIwo02SafiW8cGxH+1WJ/DCF9gCKBgRx7vEX58767P9uKK9q5pzzJrQ
         ifAiq9T7oSvQ4H9QqzOa/kLlfRSBG08SszqzeecdycrPaGU2n2koIeM/pQfiLaVOigH/
         VJ9OETGtUT7qo8AbhLQhqqo3BJpl56JF8CvNC78GmX3Y1bRio5XU+j1umrKx93Xdd0Be
         VsMg==
MIME-Version: 1.0
X-Received: by 10.202.184.11 with SMTP id i11mr7198110oif.34.1417500248380;
 Mon, 01 Dec 2014 22:04:08 -0800 (PST)
Received: by 10.60.178.8 with HTTP; Mon, 1 Dec 2014 22:04:08 -0800 (PST)
In-Reply-To: 
 <CAMGRd-nsm9gNr6biBBA8OUBhxiq2rdHpwvUc=NSPjTGu9js0LA@mail.gmail.com>
References: 
 <CAC2U_PcZ4-fjmzJQ65qddaQU_y-r-K6CDRDyp1a351OGsTKYSg@mail.gmail.com>
	<CA+A2mTstsR0HDG0xHFR-Dvg6qv0-FZBq5VM6iYSTiD4QcV-JVw@mail.gmail.com>
	<CAMGRd-nsm9gNr6biBBA8OUBhxiq2rdHpwvUc=NSPjTGu9js0LA@mail.gmail.com>
Date: Mon, 1 Dec 2014 22:04:08 -0800
Message-ID: 
 <CAFx0iW8vjKE82b6gBdXuczNUKQcohkwjFiYDok6cHP=vTxcPWQ@mail.gmail.com>
Subject: Re: Rocket
From: Timothy Chen <tnachen@gmail.com>
To: "dev@mesos.apache.org" <dev@mesos.apache.org>
Cc: "user@mesos.apache.org" <user@mesos.apache.org>
Content-Type: text/plain; charset=UTF-8
X-Virus-Checked: Checked by ClamAV on apache.org

Thanks Tobias for clarifying this, we can consider implement and help
shape the spec that is easy for Mesos to integrate.

Tim

On Mon, Dec 1, 2014 at 9:39 PM, Tobias Knaup <tobi@knaup.me> wrote:
> An important point to clarify is that two things were announced: a spec
> (App Container) and an implementation (Rocket).
> Here is the spec:
> https://github.com/coreos/rocket/blob/master/app-container/SPEC.md
> This separation of spec and implementation is important. It makes it much
> easier to integrate in Mesos. systemd is also just the implementation of
> the runtime part of the spec that CoreOS chose for Rocket. Mesos can use
> something else or come with its own.
>
>
> On Mon, Dec 1, 2014 at 1:29 PM, Dominic Hamon <dhamon@twopensource.com>
> wrote:
>
>> Instead of considering the Rocket runtime as implemented, we should
>> instead consider how we can implement their specification. A community is
>> always healthier when there are multiple implementations of a
>> specification, and through implementing it we may find ways to improve it.
>>
>> Also, this allows us to be a strong voice in the community and provide
>> value through a C++ implementation.
>>
>> I've created a JIRA ticket
>> https://issues.apache.org/jira/browse/MESOS-2162 to track any thoughts on
>> this.
>>
>> On Mon, Dec 1, 2014 at 11:10 AM, Tim Chen <tim@mesosphere.io> wrote:
>>
>>> Hi all,
>>>
>>> Per the announcement from CoreOS about Rocket (
>>> https://coreos.com/blog/rocket/) , it seems to be an exciting
>>> containerizer runtime that has composable isolation/components, better
>>> security and image specification/distribution.
>>>
>>> All of these design goals also fits very well into Mesos, where in Mesos
>>> we also have a pluggable isolators model and have been experiencing some
>>> pain points with our existing containerizers around image distribution and
>>> security as well.
>>>
>>> I'd like to propose to integrate Rocket into Mesos with a new Rocket
>>> containerizer, where I can see we can potentially integrate our existing
>>> isolators into Rocket runtime.
>>>
>>> Like to learn what you all think,
>>>
>>> Thanks!
>>>
>>
>>
>>
>> --
>> Dominic Hamon | @mrdo | Twitter
>> *There are no bad ideas; only good ideas that go horribly wrong.*
>>