It may be me but I rather like http://kubernetes.io/ as this takes the approach that you are deploying an application not a set of disparate services.
Kubernetes, Mesos, Swarm, Fleet, Marathon belong in one category (orchestration tools).
Ansible, Chef, Puppet, Salt belong in another category (configuration management).And maybe it's because we don't have good terminology around this, but your 'orchestration tools' include both backend and frontend tools for cluster management- Marathon sits at the bottom of Mesos, etc- it just seems like a weird group.
Configuration management is a very different thing to what most of ansible/chef/puppet/salt are commonly used for - it's possible to do it but it's a bit of an uphill battle. The core problem of config management is not pushing out things, but rather how do you represent configs with their myriad of interacting multi-level exceptions while also allowing tens/hundreds/thousands of operational changes to be ongoing at the same time.
Ansible for example is good for about 3-4 levels of exceptions, which isn't that much considering region and environment (dev vs prod) are two of those.