> Depending on the specific needs, different models are possible. Would be great to chat.
I'd love to join in this conversation, in our recent deployment we've been bridging Amazon EC2 with our private cloud to make use of the elasticity AWS provides, and have been thinking of ways to better improve that model. The first is what we're doing right now, and the attributes-model is intriguing. (Sorry, we should take these discussions off this thread!) On 17 August 2014 06:20, Sharma Podila <spod...@netflix.com> wrote: > > On Sat, Aug 16, 2014 at 6:41 PM, Michael Babineau < > michael.babin...@gmail.com> wrote: > >> >> I'm especially interested in multi-datacenter Mesos (either as one >> cluster or coordinating across clusters) -- if anyone has thoughts around >> this, I'd love to chat! >> >> > Depending on the specific needs, different models are possible. Would be > great to chat. > > 1. One Mesos master with slaves added from different datacenters > > Slaves from each data center may be given different attributes to bias > scheduling tasks based on latency, data locality and other characteristics. > Depends on what framework is being used. > > 2. Peer to peer model, a full Mesos cluster in each data center > > A layer written on top or in between them to broker available resources > as a 'lease out' > > 3. Hierarchical model, one datacenter is 'primary' and off-shores tasks to > other datacenters based on load (possibly similar to spilling over to > off-site cloud when on-premise datacenter is full) > 4. A ring of Mesos clusters > > Send task to the datacenter based on consistent hashing of task name/ID, a > la Cassandra clusters' key hashing. Although, one of the previous 3 models > may already achieve the objectives that this model attempts to. > > > Some of these are easier than others. There's going to be other models, I > am sure. > >
