; 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
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
>
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
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.
>>
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
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
;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
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
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
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
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
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
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
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
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
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
+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
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
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
>
> > 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.
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
;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
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
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
24 matches
Mail list logo