Mesos应用Marathon实战之Constraints篇分析.docxVIP

Mesos应用：Marathon实战之Constraints篇1.概念Marathon可以通过Constraints来控制其app在何处运行我们可以通过Marathon的REST API或者Marathon gem(marathon client)来设置app的constraints配置。Constraints由三个部分组成：字段名(field name)，操作(operator), 可选参数(optional parameter)其中字段名(field name)可以为mesos的一个slave的hostname或者Mesos slave的attribute。2.实战接下来我们结合实战，来介绍下Marathon Constrains的用法Slave IPAttribute7无0rack_id:rack-11rack_id:rack-12rack_id:rack-2字段名Hostname字段hostname 匹配slave的hostnames。hostname支持所有的operatorAttribute字段attribute 匹配Mesos slave的attributes字段。我们可以通过在mesos节点上运行mesos-slave --help来学习如何设置mesos slave的attributes。操作UNIQUE operatorUNIQUE tells Marathon to enforce uniqueness of the attribute across all of an apps tasks.$ curl-v -X POST 0:8080/v2/apps \-H Content-Type:application/json-d {id:dataman,container: {type:DOCKER,docker: {image:3:5000/fchen/mynginx,network:BRIDGE,portMappings: [{containerPort:80,hostPort:0,protocol:tcp} ] }},constraints:[[hostname,UNIQUE]],cmd:/usr/sbin/nginx -c /etc/nginx/nginx.conf,cpus:0.1,mem:128.0,instances: 5}field name = hostname, operator = UNIQUE, 在每个slave上只起一个instance。由于我们申请了5个nginx instance，而我们Mesos集群节点只有4个slave，所以我们在Marathon的管理界面上看到app dataman为Deploying状态。CLUSTER operatorCLUSTER allows you to run all of your apps tasks on slaves that share a certain attribute. This is useful for example if you have apps with special hardware needs, or if you want to run them on the same rack for low latency.$ curl-v -X POST 0:8080/v2/apps \-H Content-Type:application/json-d {id:dataman,container: {type:DOCKER,docker: {image:3:5000/fchen/mynginx,network:BRIDGE,portMappings: [{containerPort:80,hostPort:0,protocol:tcp} ] }},constraints: [[rack_id,CLUSTER,rack-1]],cmd:/usr/sbin/nginx -c /etc/nginx/nginx.conf,cpus:0.1,mem:128.0,instances: 5}CLUSTER允许我们将app发布到Mesos特定的slave节点上。如果你的app对物理机的硬件有要求，那么这个特性就很有用了。我们可以看到marathon将我们的app都发布到了rack-1节点上去了。$curl-v -X POST 0:8080/v2/apps \-H Content-Type:application/json-d {id:dataman,container: {type:DOCKER,docker: {image:3:5000/fchen/mynginx,n