Re: Rocket

2014-12-05 Thread John Pampuch
; On Fri, Dec 5, 2014 at 6:49 PM, Arunabha Ghosh wrote: >> Should CoreOS decide to adopt a governance model which is not open or what >> the Mesos community wants, does it make sense to adopt the Rocket spec and >> evolve it along with Mesos ? Having a documented container spec

Re: Rocket

2014-12-05 Thread Dominic Hamon
On Fri, Dec 5, 2014 at 6:49 PM, Arunabha Ghosh wrote: > Should CoreOS decide to adopt a governance model which is not open or what > the Mesos community wants, does it make sense to adopt the Rocket spec and > evolve it along with Mesos ? Having a documented container spec for Mesos >

Re: Rocket

2014-12-05 Thread Arunabha Ghosh
Should CoreOS decide to adopt a governance model which is not open or what the Mesos community wants, does it make sense to adopt the Rocket spec and evolve it along with Mesos ? Having a documented container spec for Mesos which can evolve along with Mesos would in some ways be better than

Re: Rocket

2014-12-03 Thread Dave Lester
ay >> "Apache >> is one of the options mentioned"? >> >> I don't see it it in the discussion thread for >> https://github.com/coreos/rocket/issues/139, but I would love to find it >> and +1 the idea. Moving to Apache would be great to see. >>

Re: Rocket

2014-12-03 Thread Tim Chen
0 AM, Dave Lester wrote: > Hey Tim C, > > Out of curiosity, which GitHub issue are you referring to when you say "Apache > is one of the options mentioned"? > > I don't see it it in the discussion thread for > https://github.com/coreos/rocket/issues/139, but I woul

Re: Rocket

2014-12-03 Thread Dave Lester
Hey Tim C, Out of curiosity, which GitHub issue are you referring to when you say "Apache is one of the options mentioned"? I don't see it it in the discussion thread for https://github.com/coreos/rocket/issues/139, but I would love to find it and +1 the idea. Moving to Apache wo

Re: Rocket

2014-12-03 Thread Timothy Chen
;s true it won't be as difficult as other options to maintain as an containerizer option for us. Tim > On Dec 3, 2014, at 9:42 AM, Tim St Clair wrote: > > inline below > > From: "Tim Chen" > To: user@mesos.apache.org > Cc: "dev" > Sent: We

Re: Rocket

2014-12-03 Thread Tim St Clair
inline below - Original Message - > From: "Tim Chen" > To: user@mesos.apache.org > Cc: "dev" > Sent: Wednesday, December 3, 2014 11:20:47 AM > Subject: Re: Rocket > Hi Tim, > I see you've already commented on the rocket repo about

Re: Rocket

2014-12-03 Thread Tim Chen
Hi Tim, I see you've already commented on the rocket repo about this, and from their messaging it aims to be independent which should be the whole point of the open container spec. I think the best way is just to be involved in the spec early on and continue to do so while we move forward

Re: Rocket

2014-12-03 Thread Tim St Clair
Not to put too fine a point on it, but how are folks planning on establishing governance around the App Container spec? https://github.com/coreos/rocket/issues/193 If the mesos community decides to leverage our own, how do we ensure that we have say in the spec going forwards? Cheers, Tim

Re: Rocket

2014-12-01 Thread Timothy Chen
tation (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

Re: Rocket

2014-12-01 Thread Abhishek Parolkar
Looks interesting definitely +1 -parolkar On Tue, Dec 2, 2014 at 1:39 PM, Tobias Knaup 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/blo

Re: Rocket

2014-12-01 Thread Tobias Knaup
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

Re: Rocket

2014-12-01 Thread Dominic Hamon
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

Re: Rocket

2014-12-01 Thread Jing Dong
Very promising idea. Rocket is absolutely looking at Docker's flaw and improve the production environment. On 1 Dec 2014, at 20:30, Tom Arnfeld wrote: +1 Sounds exciting! -- Tom Arnfeld Developer // DueDil On Mon, Dec 1, 2014 at 8:03 PM, Jie Yu wrote: > Sounds great Tim! > &g

Re: Rocket

2014-12-01 Thread Tim Chen
Hi Jie, I don't think they've published any API yet, the actual integration story is TBD but given the early stage we can help shape the API as well. Tim On Mon, Dec 1, 2014 at 12:01 PM, Jie Yu wrote: > Sounds great Tim! > > Do you know if they have published an API for

Re: Rocket

2014-12-01 Thread Tom Arnfeld
+1 Sounds exciting! -- Tom Arnfeld Developer // DueDil On Mon, Dec 1, 2014 at 8:03 PM, Jie Yu wrote: > Sounds great Tim! > Do you know if they have published an API for the rocket toolset? Are we > gonna rely on the command line interface? > - Jie > On Mon, Dec 1, 2014 a

Re: Rocket

2014-12-01 Thread Jie Yu
Sounds great Tim! Do you know if they have published an API for the rocket toolset? Are we gonna rely on the command line interface? - Jie On Mon, Dec 1, 2014 at 11:10 AM, Tim Chen wrote: > Hi all, > > Per the announcement from CoreOS about Rocket ( > https://coreos.com/blog/r

Re: Rocket

2014-12-01 Thread Tim St Clair
Absolutely... Cheers, Tim - Original Message - > From: "Tim Chen" > To: "dev" , user@mesos.apache.org > Sent: Monday, December 1, 2014 1:10:44 PM > Subject: Rocket > Hi all, > Per the announcement from CoreOS about Rocket ( > https://core

Re: Rocket

2014-12-01 Thread Joe Stein
> > > 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.

Re: Rocket

2014-12-01 Thread Steven Schlansker
On Dec 1, 2014, at 11:22 AM, Niklas Nielsen wrote: > Huge +1 > > On 1 December 2014 at 11:10, Tim Chen wrote: > Hi all, > > Per the announcement from CoreOS about Rocket > (https://coreos.com/blog/rocket/) , it seems to be an exciting containerizer > runtime that

Re: Rocket

2014-12-01 Thread Heller, Chris
;user@mesos.apache.org" Date: Monday, December 1, 2014 at 2:10 PM To: dev , "user@mesos.apache.org" Subject: Rocket 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/compone

Re: Rocket

2014-12-01 Thread Niklas Nielsen
Huge +1 On 1 December 2014 at 11:10, Tim Chen 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 i

Rocket

2014-12-01 Thread Tim Chen
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