Hi Diptanu,
Thanks for your feedback. This sounds like the approach we'll be taking,
too.
On Sat, Nov 29, 2014 at 11:34 AM, Diptanu Choudhury dipta...@gmail.com
wrote:
Hi Janet,
We implemented the same in our Titan Mesos Executor. We have an executor
manage multiple containers. We didn't
Hello
the idea is to be able of tuning the mesos slave configuration (attributes,
resources offers, general options, ... upgrades?) without altering the
current tasks running on this mesos slave (a dockerized jenkins instance +
docker jenkins slaves for example).
I am setting up a test cluster
Ah thanks. Why does it take 2 minutes to change configuration, are you
doing it manually? Scary :)
On Mon, Dec 1, 2014 at 10:43 AM, Geoffroy Jabouley
geoffroy.jabou...@gmail.com wrote:
Hello
the idea is to be able of tuning the mesos slave configuration
(attributes, resources offers,
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
This does sound promising. Though if it restricts one to hosts using systemd
than I don¹t see much value in it over Docker. However no need to preclude
it on choice of init process alone, plus it exercises the ContainerInfo
structure some more. +1
From: Tim Chen t...@mesosphere.io
Reply-To:
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
cool, yeah +1
The more container options means the more you need a solution like Mesos to
run them all in =8^) ... or be able to run apps without them too...
fantastic!
On Mon, Dec 1, 2014 at 2:22 PM, Niklas Nielsen nik...@mesosphere.io wrote:
Huge +1
On 1 December 2014 at 11:10, Tim Chen
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 (
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 (
+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
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 yujie@gmail.com wrote:
Sounds great Tim!
Do you know if they have published an API for the
There are some downsides to this as well - For ex, if the executor crashes
Mesos would get a TASK_LOST while the container might still be running. So
we are doing something similar to Aurora's GC Executor to clean up
containers behind us.
On Mon, Dec 1, 2014 at 10:19 AM, Janet Borschowa
Sorry this is a bit of a tangent to the thread:
For ex, if the executor crashes Mesos would get a TASK_LOST while the
container might still be running.
Mesos should destroy the container when the executor exits, are you seeing
otherwise?
So we are doing something similar to Aurora's GC
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
Hey Ben,
We are not using the Docker containerizer from Mesos Core yet, we just have
a plain executor. And by container I meant the docker container here. The
docker containers in this case are started by the executor [which uses
Docker's remote API]. Mesos does kill the container that it creates
Got it, thanks for clarifying. :)
On Mon, Dec 1, 2014 at 1:40 PM, Diptanu Choudhury dipta...@gmail.com
wrote:
Hey Ben,
We are not using the Docker containerizer from Mesos Core yet, we just
have a plain executor. And by container I meant the docker container
here. The docker containers in
Hi,
Sorry if this has been discussed before. I'm new to the list.
We are currently running our Spark + Spark Streaming jobs on Mesos,
submitting our jobs through Marathon.
We see with some regularity that the Spark Streaming driver gets killed by
Mesos and then restarted on some other node by
There are different reasons, but most commonly is when the framework ask to
kill the task.
Can you provide some easy repro steps/artifacts? I've been working on Spark
on Mesos these days and can help try this out.
Tim
On Mon, Dec 1, 2014 at 2:43 PM, Gerard Maas gerard.m...@gmail.com wrote:
When executor dies, did you see any exceptions from Mesos or Spark?
On 1 December 2014 at 22:43, Gerard Maas gerard.m...@gmail.com wrote:
Hi,
Sorry if this has been discussed before. I'm new to the list.
We are currently running our Spark + Spark Streaming jobs on Mesos,
submitting our
Hi Tim,
It's quite hard to reproduce. It just happens... some time worst than
others, mostly when the system is under load. We notice b/c the framework
starts 'jumping' from one slave to other, but so far we have no clue why
this is happening.
What I'm currently looking for is some potential
Hi Gerard,
I see. What will be helpful to help diagnoise your problem is that if you
can enable verbose logging (GLOG_v=1) before running the slave, and share
the slave logs when it happens.
Tim
On Mon, Dec 1, 2014 at 3:23 PM, Gerard Maas gerard.m...@gmail.com wrote:
Hi Tim,
It's quite hard
Hi Dave,
This is a timely topic, since we have been prototyping and mocking up something
similar at Mesosphere. We created a new public GitHub repository for it about
three weeks ago called universe (http://github.com/mesosphere/universe).
Although we have added some informal specs, it's very
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:
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 t...@knaup.me wrote:
An important point to clarify is that two things were announced: a spec
(App Container) and an
26 matches
Mail list logo
