(I'm sure I'm missing something here, so please forgive if I'm stating the obvious)
This is actually very well supported right now: you can use "slave attributes" (if, eg, you want to name the various clusters differently and launch tasks according to those criteria) that would be passed on to the Frameworks along with the resource offers: the frameworks could then decide whether to accept the offer and launch tasks based on whatever logic you want to implement. You could use something like "--attributes="cluster:01z99; os:ubuntu-14-04; jdk:8" or whatever makes sense. *Marco Massenzio* *Distributed Systems Engineer* On Tue, Jul 7, 2015 at 8:55 AM, CCAAT <[email protected]> wrote: > Hello team_mesos, > > Is there any reason one set of (3) masters cannot talk to and manage > several (many) different slave clusters of (3)? These slave clusters > would be different arch, different mixes of resources and be running > different frameworks, but all share/use the same (3) masters. > > > Ideas on how to architect this experiment, would be keenly appreciated. > > > James > >
