mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Carey <aca...@ilm.com>
Subject RE: Deploying containers to every mesos slave node
Date Thu, 12 Mar 2015 13:36:06 GMT
What base image are you using for your slave nodes? Salt doesn't seem to play very nicely with
CoreOS (unless anyone here has any tips?).

In an ideal world we could spin up a node with just the mesos slave running on it and then
deploy consul as a docker container to it using a mesos framework, removing the need for any
kind of provisioning tool like salt (assuming mesos slave is installed using cloud-init or
something similar).


________________________________
From: Shuai Lin [linshuai2012@gmail.com]
Sent: 12 March 2015 13:25
To: user@mesos.apache.org
Subject: Re: Deploying containers to every mesos slave node

We do the same thing: running consul on each mesos slave, and use saltstack to provision it.
Why do you want to get rid of salt? You  always need some tool to provision your server, right?

Regards,
Shuai

On Thu, Mar 12, 2015 at 4:54 PM, Aaron Carey <acarey@ilm.com<mailto:acarey@ilm.com>>
wrote:
Hi All,

In setting up our cluster, we require things like consul to be running on all of our nodes.
I was just wondering if there was any sort of best practice (or a scheduler perhaps) that
people could share for this sort of thing?

Currently the approach is to use salt to provision each node and add consul/mesos slave process
and so on to it, but it'd be nice to remove the dependency on salt.

Thanks,
Aaron


Mime
View raw message