3 ms·

Forgive me, but I'm not very familiar with the rapidly growing container-based ecosystems market, but how do all these pieces fit together? Namely: * Mesos / Y

Forgive me, but I'm not very familiar with the rapidly growing container-based ecosystems market, but how do all these pieces fit together? Namely: * Mesos / Yarn * Marathon * Kubernetes * OpenShift * Chronos There are others I'm sure that I just don't recall. Also, how does the container approach fit in the traditional VM models of OpenStack / AWS / Digital Ocean. Are these systems aiming to ultimately replace them? Do they solve the problems of networking and disk? Maybe it's time I spent an afternoon looking into all this.

themgt 12y ago
When CoreOS abandoned btrfs, it made me seriously start to consider the Joyent SDC stack, above all else just because ZFS can answer the storage question in a way that seemingly nothing on Linux will be able to provide in the near future
- raincom 12y ago
  well, micro services Paas does not care much about the storage: ephemeral storage is good. And you can re deploy the app with a click.
  - smarterclayton 12y ago
    As part of OpenShift and Kubernetes we're building stack integration for Gluster, Ceph, NFS, iSCSI, and others into the core runtime environment (so you can on-demand provision storage at a cluster level). Micro services may not care much about storage, but everything else does. https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/design/persistent-storage.md https://github.com/GoogleCloudPlatform/kubernetes/blob/maste... captures the first draft of it, but there's a lot more work going on to let you bind storage on demand to Docker containers at a cluster level.
- justincormack 12y ago
  ClusterHQ is working on openzfs for containers too, on Linux.
  - ferrantim 12y ago
    Yep, and we think ZFS on Linux is ready real production use https://clusterhq.com/blog/state-zfs-on-linux/ https://clusterhq.com/blog/state-zfs-on-linux/
    - deleted 12y ago
      [deleted]
- tracker1 12y ago
  I really, really like the Joyent SDC stack... It seems like a really nice solution. Though I wish they had the equivalent of S3 or Azure blob storage. Having to run your own VMs for archive storage seems like a pain, especially relative to the cost/amount of storage you get per VM.
  - themgt 12y ago
    Right. Ceph is what I've been using for that, and I'm assuming it'll be doable either in Docker or Linux KVM on SDC
  - Titanous 12y ago
    Manta is part of SDC and implements a S3-like API (plus distributed map-reduce data processing).
andrewjf 12y ago
> Mesos / Yarn Mesos is a general purpose framework for task scheduling into a set of machines. Mesos uses a concept of 'offers' where custom frameworks can choose to use or not use them. Yarn is similar, but it's a bit incestual with the rest of the Hadoop ecosystem and is designed to run distributed MRv2 jobs. Mesos isn't related to Hadoop other than it's use of Zookeeper for leader election & state. Mesos itself doesn't do much without a framework. > Marathon Marathon is a framework for Mesos that runs long-lived tasks and supports interesting things like artifact staging, dependencies. > Kubernetes Not really sure how Kubernetes differentiates itself from Mesos (besides having Google as a sponsor). I haven't used it myself. > OpenShift A PaaS from Red Hat that uses it's own scheduling and distribution mechanisms to run applications built (very Similar to Heroku/Elastic Beanstalk) > Chronos Similar to Marathon, except that it runs an essentially distributed cron (and has dependencies, etc). You can use Chronos as a full-fledged distributed job running system. Chronos isn't intended to run long-running tasks.

themgt 12y ago

When CoreOS abandoned btrfs, it made me seriously start to consider the Joyent SDC stack, above all else just because ZFS can answer the storage question in a way that seemingly nothing on Linux will be able to provide in the near future

raincom 12y ago
well, micro services Paas does not care much about the storage: ephemeral storage is good. And you can re deploy the app with a click.
- smarterclayton 12y ago
  As part of OpenShift and Kubernetes we're building stack integration for Gluster, Ceph, NFS, iSCSI, and others into the core runtime environment (so you can on-demand provision storage at a cluster level). Micro services may not care much about storage, but everything else does. https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/design/persistent-storage.md https://github.com/GoogleCloudPlatform/kubernetes/blob/maste... captures the first draft of it, but there's a lot more work going on to let you bind storage on demand to Docker containers at a cluster level.
justincormack 12y ago
ClusterHQ is working on openzfs for containers too, on Linux.
- ferrantim 12y ago
  Yep, and we think ZFS on Linux is ready real production use https://clusterhq.com/blog/state-zfs-on-linux/ https://clusterhq.com/blog/state-zfs-on-linux/
  - deleted 12y ago
    [deleted]
tracker1 12y ago
I really, really like the Joyent SDC stack... It seems like a really nice solution. Though I wish they had the equivalent of S3 or Azure blob storage. Having to run your own VMs for archive storage seems like a pain, especially relative to the cost/amount of storage you get per VM.
- themgt 12y ago
  Right. Ceph is what I've been using for that, and I'm assuming it'll be doable either in Docker or Linux KVM on SDC
- Titanous 12y ago
  Manta is part of SDC and implements a S3-like API (plus distributed map-reduce data processing).

andrewjf 12y ago

> Mesos / Yarn Mesos is a general purpose framework for task scheduling into a set of machines. Mesos uses a concept of 'offers' where custom frameworks can choose to use or not use them. Yarn is similar, but it's a bit incestual with the rest of the Hadoop ecosystem and is designed to run distributed MRv2 jobs. Mesos isn't related to Hadoop other than it's use of Zookeeper for leader election & state. Mesos itself doesn't do much without a framework. > Marathon Marathon is a framework for Mesos that runs long-lived tasks and supports interesting things like artifact staging, dependencies. > Kubernetes Not really sure how Kubernetes differentiates itself from Mesos (besides having Google as a sponsor). I haven't used it myself. > OpenShift A PaaS from Red Hat that uses it's own scheduling and distribution mechanisms to run applications built (very Similar to Heroku/Elastic Beanstalk) > Chronos Similar to Marathon, except that it runs an essentially distributed cron (and has dependencies, etc). You can use Chronos as a full-fledged distributed job running system. Chronos isn't intended to run long-running tasks.