, Arunabha Ghosh arunabha...@gmail.com 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
which can evolve along
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
inline below
- Original Message -
From: Tim Chen t...@mesosphere.io
To: user@mesos.apache.org
Cc: dev d...@mesos.apache.org
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 this, and from
, 2014 11:20:47 AM
Subject: Re: Rocket
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'm all over this like white on rice.
I think the best way
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.
Dave
On Wed, Dec 3, 2014 at 10:02 AM, Timothy Chen t...@mesosphere.io wrote:
Hi Tim,
Definitely I agree, i think what 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
Huge +1
On 1 December 2014 at 11:10, Tim Chen t...@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
-To: user@mesos.apache.org user@mesos.apache.org
Date: Monday, December 1, 2014 at 2:10 PM
To: dev d...@mesos.apache.org, user@mesos.apache.org
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
On Dec 1, 2014, at 11:22 AM, Niklas Nielsen nik...@mesosphere.io wrote:
Huge +1
On 1 December 2014 at 11:10, Tim Chen t...@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
...@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
Absolutely...
Cheers,
Tim
- Original Message -
From: Tim Chen t...@mesosphere.io
To: dev d...@mesos.apache.org, 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://coreos.com/blog
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 t...@mesosphere.io wrote:
Hi all,
Per the announcement from CoreOS about Rocket (
https://coreos.com/blog
+1 Sounds exciting!
--
Tom Arnfeld
Developer // DueDil
On Mon, Dec 1, 2014 at 8:03 PM, Jie Yu yujie@gmail.com 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 at 11
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 t...@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
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 t...@duedil.com wrote:
+1 Sounds exciting!
--
Tom Arnfeld
Developer // DueDil
On Mon, Dec 1, 2014 at 8:03 PM, Jie Yu yujie@gmail.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
Looks interesting definitely +1
-parolkar
On Tue, Dec 2, 2014 at 1:39 PM, Tobias Knaup t...@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
) 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
18 matches
Mail list logo