Just a thought looking forward... Might be useful to define an init kind of feature in Mesos slaves. Configuration can be defined in Mesos master that lists services that must be run on all slaves. When slaves register, they get the list of services to run all the time. Updates to the configuration can be dynamically reflected on all slaves and therefore this ensures that all slaves run the required services. Sophistication can be put in place to have different set of services for different "types" of slaves (by resource types/quantity, etc.). Such a feature bodes well with Mesos being the DataCenter OS/Kernel.
On Thu, Jan 22, 2015 at 9:43 AM, CCAAT <[email protected]> wrote: > On 01/21/2015 11:10 PM, Shuai Lin wrote: > > OK, I'll take a look at the debian package. > > thanks, > James > > > > > You can always write the init wrapper scripts for marathon. There is an >> official debian package, which you can find in mesos's apt repo. >> >> On Thu, Jan 22, 2015 at 4:20 AM, CCAAT <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hello all, >> >> I was reading about Marathon: "Marathon scheduler processes were >> started outside of Mesos using init, upstart, or a similar tool" [1] >> >> This means >> >> So my related questions are" >> >> Does Marathon work with mesos + Openrc as the init system? >> >> Are there any other frameworks that work with Mesos + Openrc? >> >> >> James >> >> >> >> [1] http://mesosphere.github.io/__marathon/ >> <http://mesosphere.github.io/marathon/> >> >> >> >
