On Wed, Jul 1, 2015 at 11:38 PM, tommy xiao <[email protected]> wrote:
> Hi Marco, > > I want to fault tolerance slave nodes over multi datacenter. but i found > the possible setup methods is not production way. > what kind of fault-tolerance are you looking for here? Against one (or either) of the DC going away or network partitioning? or one (or more) of the racks in one DC to go away? Depending on what you want to protect yourself against there may be different ways to achieve that. I'm sorry I haven't been around Mesos long enough to really be knowledgeable about the specifics here; but have built HA systems before around VPCs and On-Prem solutions, and I know bi-di routing can be achieved using gateways and/or VPN (dedicated) links (we also solved that very issue at Google too, but I can't talk about that :). I'm sure the Twitter folks have solved that same problem too, but I'm guessing they may not be able to share much either? > 2015-07-02 1:38 GMT+08:00 Marco Massenzio <[email protected]>: > >> Hi Tommy, >> >> not sure what your use-case is, but you are correct, the master/slave >> nodes need to have bi-directional connectivity. >> However, there is no fundamental reason why those have to be "public IPs" >> - so long as they are routable (either via DNS discovery and / or VPN or >> other network-layer mechanisms) that will work. >> (I mean, without even thinking too hard about this - so I may be entirely >> wrong here - you could place a couple of Nginx/HAproxy nodes with two NICs, >> one visible to the Slaves, the other in the VPC subnet, and forward all >> traffic? I'm sure I'm missing something here :) >> >> When you launch the master nodes, you specify the NICs they need to >> listen to via the --ip option, while the slave nodes have the --master flag >> that should have either a hostname:port of ip:port argument: so long as >> they are routable, this *should* work (although, admittedly, I've never >> tried this personally). >> >> One concern I would have in such an arrangement though, would be about >> network partitioning: if the DC/DC connectivity were to drop, you'd >> suddenly lose all master/slave connectivity; it's also not clear to me that >> having sectioned the Masters from the Slaves would give you better >> availability and/or reliability and/or security? >> It would be great to understand the use-case, so we could see what could >> be added (if anything) to Mesos going forward. >> >> >> *Marco Massenzio* >> *Distributed Systems Engineer* >> >> On Wed, Jul 1, 2015 at 9:15 AM, tommy xiao <[email protected]> wrote: >> >>> Hello, >>> >>> I would like to deploy master nodes in a private zone, and setup mesos >>> slaves in another datacenter. But the multi-datacenter mode can't work. it >>> need slave node can reach master node in public network ip. But in >>> production zone, the gateway ip is not belong to master nodes. Does anyone >>> have same experience on multi-datacenter deployment case? >>> >>> I prefer kubernets cluster proposal. >>> >>> https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/proposals/federation-high-level-arch.png >>> >>> >>> -- >>> Deshi Xiao >>> Twitter: xds2000 >>> E-mail: xiaods(AT)gmail.com >>> >> >> > > > -- > Deshi Xiao > Twitter: xds2000 > E-mail: xiaods(AT)gmail.com >
