Hi all, the question for a way to start a task on all nodes has come up a couple of times on the Marathon ML and GH repo as well. The reason for not having this in Marathon is simple. We can’t guarantee that we’ll ever get offers for all the slaves and also we son’t know how many slaves are in the cluster. I think something like this would be a great addition to the Mesos API.
Cheers, Dario > On 12 Mar 2015, at 06:36, Aaron Carey <[email protected]> wrote: > > 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 [[email protected]] > Sent: 12 March 2015 13:25 > To: [email protected] > 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 <[email protected] > <mailto:[email protected]>> 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
