marathon

提起Docker容器化 不得不提服务编排，众所周知目前Docker常用的服务编排模式有三种， Mesos DockerSwarm Kubernetes，下面将详细介绍这三种服务编排模式的架构和环境搭建。 一. Mesos 1.Mesos架构图 下图是在Mesos官网上对mesos架构的介绍 即使不看下面的英文描述，从这张图上我们也看看出Mesos的整体架构，主体为主从结构master/slave或者master/agent模式，对master节点来说为了避免单点，引入了多个master，多个master向Zookeeper注册自己，用zk实现选举。master节点运行一些任务调度器（scheduler），agent节点运行任务执行器（executor），一个agent节点可以运行多个执行器，有执行器来执行具体任务（task）。 2.Mesos任务执行调度过程 任务调度如下图： 从图中可以看出，这个调度分为四个过程： 1.Mesos Agent将自己所在机器（物理机，虚拟机，容器）的资源信息（可用的处理器，内存，磁盘等资源）上报给Mesos Master的资源分配组件（Allocation Module）。 2.master节点向framework发送资源邀约（resource offer），通知framework在agent上可用的资源信息。 3.框架调度程序（FW

I'm looking for some pros and cons of whether to go with Marathon and Chronos, Docker Swarm or Kubernetes when running Docker containers on DC/OS. For example, when is it better to use Marathon/Chronos than Kubernetes and vice versa? Right now I'm mostly into experimenting but hopefully we'll start using one of these services in production after the summer. This may disqualify Docker Swarm since I'm not sure if it'll be production ready by then. What I like about Docker Swarm is that it's essentially just "Docker commands" and you don't have to learn something completely new. We're already

I have problem witch start redis server on one IP address in mesos, marathon. My steps create own Dockerfile who include own redis.conf I create my own docker image and pull it into docker repo (name arekmax/redis-instancje) in Marathon I start my docker images - redis start and work properly. Failover redis server in mesos also work properly - when I shut-down 192.168.18.21 server - Marathon start Redis in second or third instance. Now I want give my developer one adress IP where they can use redis server (I don't want give them now 192.168.18.21:31822 and after failover for example 192.168