Re:Why the data center needs an operating system
by nqnielsen on Wednesday December 03, 2014 @03:54PM
(#8696273)
Mesos itself is only considered as the kernel of a operating system for the datacenter (should also be the message of the article) - not the entirety of what _will_ be. It is Mesos in conjunction with distributed storage, app schedulers, interactive and batch systems for data processing that will make the OS. Just like Mac OS X isn't the Mach kernel alone, but a wide palette of applications that makes the entire OS experience.
Re:Why the data center needs an operating system
by gtaylor on Wednesday December 03, 2014 @03:48PM
(#8696247)
> It's the only thing out there that will allow for super low latency response to commands across the cluster. It also can do configuration management etc if you want, or a lot of people use it to just trigger existing chef/puppet jobs.
FWIW, Ansible also does low-latency communications through pipelining/accelerated mode. Ditto for the config management and triggering.
Re:Why the data center needs an operating system
by res0nat0r on Wednesday December 03, 2014 @03:55PM
(#8696285)
I don't believe even with Ansible's accelerated mode it can come anywhere close to Salt for large deployments. It is still agentless and has to run from a single source and using ssh which is going to be slower than 0MQ. Also using something like salt-syndic to create topologies can reliably scale to thousands of machines and still cope with the load.
Re:Why the data center needs an operating system
by florianleibert on Thursday December 04, 2014 @12:29AM
(#8697954)
Mesos itself doesn't do scheduling - it merely does allocation and allows applications built on top of it to schedule to workload.
Re:Why the data center needs an operating system
by throwaway82347 on Friday December 05, 2014 @04:21AM
(#8703564)
s/Mesos/Marathon and the comment still stands.
Re:Why the data center needs an operating system
by florianleibert on Friday December 05, 2014 @10:35AM
(#8704993)
Well that changes everything b/c Marathon is just a piece of the puzzle. This turns the statement into "init.d isn't an operating system".
Mesos is basically an application scheduler. It doesn't manage the base operating systems or machine provisioning. Mesos is concerned with ensuring that one or multiple applications are launched and running on a cluster of machines.
The Saltstack framework is the only thing I know of that would provide all the primitives and control necessary for an operator to truly control a full 5-300,000 node datacenter from one station. It's the only thing out there that will allow for super low latency response to commands across the cluster. It also can do configuration management etc if you want, or a lot of people use it to just trigger existing chef/puppet jobs.
I've been using Saltstack in conjunction with Mesos to build out this full datacenter-as-OS stack. Works... :-)