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 <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 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.*
