3 ms·

Disclaimer: I work for Mesosphere (Champions of Apache Mesos and DC/OS) We have total respect for K8s, but I don't think you can claim winning just based on th

Disclaimer: I work for Mesosphere (Champions of Apache Mesos and DC/OS) We have total respect for K8s, but I don't think you can claim winning just based on the community and stars. OpenStack has a huge larger community of developers and advocates, but it is still haven't reached it's potential despite many years and incredible effort, seminars and summits Also most of these next gen infr projects now (DC/OS which is powered by Mesos, K8s, docker swarm ) are converging feature wise, but they also have their strengths and weaknesses, some of these are temporary, some of these are structurally by design Mesos (and DC/OS) were not just designed for scale, but also for extensibility and different workloads, which is why you can run Cassandra, Kafka, Spark, ..etc In production. None of these workloads run as traditional containers, with DC/OS they have their own operational logic such as honoring placement, simple installation, and upgrade, which is a core design function of the two-level scheduler People usually complain that standing up Mesos is hard, which is why we we built DC/OS and open sourced it to give you the power of mesos and its awesome capabilities in managing containers and data workloads without going through all the effort to stitch everything yourself. Check it out at DCOS.io, I am sure you guys will be blown away.

manojlds 10y ago
I have been trying to understand advantages of DC/OS over Mesos. Why should I even consider it? All I can understand is that it has a better(?) UI. I understand that even this and the DCOS CLI and packages work with Mesos too? So what's in there in DC/OS?
- amr_abdelrazik 10y ago
  Tl;DR: DC/OS provides all the components you need on top of Mesos to run in production, all pre-packaged and tested together with easy to install way Mesos provide the core resource management and scheduling, think of it as the Kernel of an (DC) operating system. On top of Mesos you usually need: 1- Container/Workload Scheduling capability which is Marathon, now built in and integrated in DC/OS so you are just up and running in minutes 2- Management (Beautiful DC/OS UI and CLI) to manage all cluster and workload operations. It also includes Installer (of all components including Zookeeper, networking, ..etc) 3- App Store (Universe) that allows you to easily find and deploy latest packages such as Kafka, Cassandra and Spark with a single command, in regular Mesos you needed to find the Framework that worked with a specific version of Mesos, troubleshooting, ...etc. Now it's an app store like experience 4- Core infrastructure components such as very cool service discovery and loadbalancing (Minuteman), Storage drivers, CNI support If you want to run docker containers, DC/OS also gives you the ability to use the docker daemon or the new Universal containerize (technology preview) which we just released. Because mesos is very modular and very powerful, it was built to have modular implementation of all system components, but our team and our founders ran some of the largest implementations of Mesos (Twitter, Airbnb, ..etc) and they complied all thes best practices and the bits and pieces in DC/OS. Hope that explains,
  - bogomipz 10y ago
    I attempted to spin up a DCOS cluster on AWS the day that you Mesosphere opensourced it. I followed the tutorial step by step and the installation failed, I was never able to log in to the admin console. It was completely opaque and I wasn't able to troubleshoot it in any meaningful way. After A couple of hours I gave up and went back to my Mesos setup. It was a very frustrating experience. I'm not sure how it is now but my experience was disappointing.
rdtsc 10y ago
Speaking of DC/OS, not related to the article at hand, but I noticed this repo in there: https://github.com/dcos/lashup https://github.com/dcos/lashup Just wanted to say that is some seriously good stuff -- a CRDT based, distributed masterless database, and what seems like a failure detector as well.
eikenberry 10y ago
The problem I always here with Mesos is that it doesn't scale down well. I.E., that it is not developer friendly or, to put it another way, you can't run it on your laptop.
- SEJeff 10y ago
  Actually that isn't true. Minimesos runs quite well on your laptop if you wish to test that way: https://minimesos.org/ https://minimesos.org/
- karlkfi 10y ago
  DC/OS (A Mesos distribution) can be used on your laptop with dcos-vagrant or dcos-docker: - https://github.com/dcos/dcos-vagrant https://github.com/dcos/dcos-vagrant - https://github.com/dcos/dcos-docker https://github.com/dcos/dcos-docker However, your point is somewhat valid in that Mesos requires you to allocate resources to everything you run, while resource allocation/enforcement is optional in Kubernetes. So you can easily run too many things and freeze your computer with Kubernetes, while Mesos is more conservative.

manojlds 10y ago

I have been trying to understand advantages of DC/OS over Mesos. Why should I even consider it? All I can understand is that it has a better(?) UI. I understand that even this and the DCOS CLI and packages work with Mesos too? So what's in there in DC/OS?

amr_abdelrazik 10y ago
Tl;DR: DC/OS provides all the components you need on top of Mesos to run in production, all pre-packaged and tested together with easy to install way Mesos provide the core resource management and scheduling, think of it as the Kernel of an (DC) operating system. On top of Mesos you usually need: 1- Container/Workload Scheduling capability which is Marathon, now built in and integrated in DC/OS so you are just up and running in minutes 2- Management (Beautiful DC/OS UI and CLI) to manage all cluster and workload operations. It also includes Installer (of all components including Zookeeper, networking, ..etc) 3- App Store (Universe) that allows you to easily find and deploy latest packages such as Kafka, Cassandra and Spark with a single command, in regular Mesos you needed to find the Framework that worked with a specific version of Mesos, troubleshooting, ...etc. Now it's an app store like experience 4- Core infrastructure components such as very cool service discovery and loadbalancing (Minuteman), Storage drivers, CNI support If you want to run docker containers, DC/OS also gives you the ability to use the docker daemon or the new Universal containerize (technology preview) which we just released. Because mesos is very modular and very powerful, it was built to have modular implementation of all system components, but our team and our founders ran some of the largest implementations of Mesos (Twitter, Airbnb, ..etc) and they complied all thes best practices and the bits and pieces in DC/OS. Hope that explains,
- bogomipz 10y ago
  I attempted to spin up a DCOS cluster on AWS the day that you Mesosphere opensourced it. I followed the tutorial step by step and the installation failed, I was never able to log in to the admin console. It was completely opaque and I wasn't able to troubleshoot it in any meaningful way. After A couple of hours I gave up and went back to my Mesos setup. It was a very frustrating experience. I'm not sure how it is now but my experience was disappointing.

rdtsc 10y ago

Speaking of DC/OS, not related to the article at hand, but I noticed this repo in there: https://github.com/dcos/lashup https://github.com/dcos/lashup Just wanted to say that is some seriously good stuff -- a CRDT based, distributed masterless database, and what seems like a failure detector as well.

eikenberry 10y ago

The problem I always here with Mesos is that it doesn't scale down well. I.E., that it is not developer friendly or, to put it another way, you can't run it on your laptop.

SEJeff 10y ago
Actually that isn't true. Minimesos runs quite well on your laptop if you wish to test that way: https://minimesos.org/ https://minimesos.org/
karlkfi 10y ago
DC/OS (A Mesos distribution) can be used on your laptop with dcos-vagrant or dcos-docker: - https://github.com/dcos/dcos-vagrant https://github.com/dcos/dcos-vagrant - https://github.com/dcos/dcos-docker https://github.com/dcos/dcos-docker However, your point is somewhat valid in that Mesos requires you to allocate resources to everything you run, while resource allocation/enforcement is optional in Kubernetes. So you can easily run too many things and freeze your computer with Kubernetes, while Mesos is more conservative.