Thanks :) But I am runing a test setup of 3 nodes on CentOS7, should have written this with first post.
Linux m01 3.10.0-693.2.2.el7.x86_64 mesos-1.4.0-2.0.1.x86_64 marathon-1.4.8-1.0.660.el7.x86_64 containernetworking-cni-0.5.1-1.el7.x86_64 mesosphere-zookeeper-3.4.6-0.1.20141204175332.centos7.x86_64 chronos-2.5.0-0.1.20170816233446.el7.x86_64 -----Original Message----- From: Bruce Campbell [mailto:[email protected]] Sent: vrijdag 20 oktober 2017 18:41 To: [email protected] Subject: RE: Mesos acceptedResourceRoles slave_public In acs engine if you define a ports list, the agent will be deployed as slave_public. Example of a public linux agent: "agentPoolProfiles": [ { "name": "wpub6", "count": 3, "vmSize": "Standard_DS2_v2", "dnsPrefix": "wpub6", "ports": [ 80, 443, 8080, 3389 ], "customNodeLabels" : { "foo" : "bar", "att1" : "value1" } }, }, -----Original Message----- From: Marc Roos [mailto:[email protected]] Sent: Friday, October 20, 2017 9:29 AM To: user <[email protected]> Subject: Mesos acceptedResourceRoles slave_public I added "acceptedResourceRoles": ["slave_public"] to a json application config in marathon. And it complains that the agents/slaves are not configured for this. I see some manuals on how to reconfigure via dc/os. I just wondered could this be an easy setting like something like this echo "appc,docker" > /etc/mesos-slave/image_providers
