One of the major, compelling cases for using mesos is the resource partitioning and isolation between process groups that slave containerizers manage. And that, of course, OS containers are lightweight and low-overhead.
Windows has a ways to go here. You can read about Drawbridge, or even the latest speculation re: Docker+Windows Server integration and what that might look like. On Fri, Feb 20, 2015 at 12:17 AM, Alexandre Mclean < [email protected]> wrote: > Hi everyone, > what are the current limitations to make the Slave work on a Windows > platform? > > Would it be possible to extract the slave component from the main Mesos > codebase and compile it on Windows? > > Also, could we have a pure implementation of the Slave that wouldn't > depend on libmesos, like we do for the newest bindings like mesos-go? Does > it even make sense to want this? > > -- > Alexandre > -- James DeFelice 585.241.9488 (voice) 650.649.6071 (fax)
