We've been experimenting with using Marathon to do this. We've found a couple issues in making in smooth, but those bugs are all in the process of being fixed. Within the next few weeks, I think that Marathon will be a solid choice for this use case.
On Tue, Jan 6, 2015 at 4:05 AM, Itamar Ostricher <[email protected]> wrote: > Hi, > > I was wondering if the best approach to do what I want is to use mesos > itself, or other Linux system tools. > > There are a bunch of services that our framework assumes are running on > all participating slaves (e.g. logging service, data-bridge service, etc.). > One approach to do that is in the infrastructure level, making sure that > slave nodes are configured correctly (e.g. with pre-configured images, or > other provisioning systems). > Another approach would be to use mesos itself (maybe with something like > Marathon) to schedule these services on all slave nodes. > > The advantage of the mesos-based approach is that it becomes trivial to > account for the resource consumption of said services (e.g. make sure > there's always at least 1 CPU dedicated to this). > I'm not sure how to achieve something similar with the system-approach. > > Anyone has any insights on this? >
