Good stuff. Thanks.
Currently I have both consul and registrator tasks with the "constraints": [["hostname", "UNIQUE"] if ensure the number of instances in the task is more than what's running they run on every salve and launch to new slaves. seems to work. kinda dirty. not sure what side affects this might have. SK ________________________________ Scott Kinney | DevOps stem <http://www.stem.com/> | m 510.282.1299 100 Rollins Road, Millbrae, California 94030 This e-mail and/or any attachments contain Stem, Inc. confidential and proprietary information and material for the sole use of the intended recipient(s). Any review, use or distribution that has not been expressly authorized by Stem, Inc. is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Thank you. ________________________________ From: Guangya Liu <[email protected]> Sent: Sunday, May 22, 2016 4:11 AM To: [email protected] Subject: Re: Setting constraints Hi Scott, If you want to monitor the status of "Pod" project, I think that you can subscribe the working group for container: [email protected]<mailto:[email protected]> , there may be some discussion for this. There is also a document for some notes here: https://docs.google.com/document/d/1BneVLIqvgKWbVWs5usfKtUeBeoBQLvVs4tPLSPG6NAs/edit?usp=sharing For your question, can you please do it as this to workaround? Put both service to a single docker image and use marathon deploy it with "constraints": [["hostname", "UNIQUE"], this may help. Thanks, Guangya On Sun, May 22, 2016 at 12:00 PM, Scott Kinney <[email protected]<mailto:[email protected]>> wrote: Yes, I would like to have a consul and a registrator automaticaly run on every slave or on every slave that as a certain attribute. I'll keep an eye out for the 'pod' feature. Thanks Guangya ________________________________ Scott Kinney | DevOps stem <http://www.stem.com/> | m 510.282.1299<tel:510.282.1299> 100 Rollins Road, Millbrae, California 94030 This e-mail and/or any attachments contain Stem, Inc. confidential and proprietary information and material for the sole use of the intended recipient(s). Any review, use or distribution that has not been expressly authorized by Stem, Inc. is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Thank you. ________________________________ From: Guangya Liu <[email protected]<mailto:[email protected]>> Sent: Saturday, May 21, 2016 7:12 PM To: [email protected]<mailto:[email protected]> Subject: Re: Setting constraints Scott, So you mean that you want to treat the consul and registrator as a deploy unit? One agent run one consul and registrator? Then this is similar with Kubernetes Pod and Mesos also planning a project for "Pod" support in near future. Thanks, Guangya On Sun, May 22, 2016 at 9:43 AM, Vinod Kone <[email protected]<mailto:[email protected]>> wrote: There is no flexible/dynamic way to ensure that a particular task runs on every agent in the cluster. If you are ok with static configuration, you can set aside resources for a role on every agent by using the resources flag (e.g, --resources="cpus(system):2;cpus(*): 10" on an agent with 12 cpus). You can then start marathon with "system" role and ensure that only system tasks are submitted with that role in their app config. On Sat, May 21, 2016 at 6:26 PM, Scott Kinney <[email protected]<mailto:[email protected]>> wrote: Hi Guangya, That doens't deploy the apps automatically to every slave. only one slave will get one of each. ________________________________ Scott Kinney | DevOps stem <http://www.stem.com/> | m 510.282.1299<tel:510.282.1299> 100 Rollins Road, Millbrae, California 94030 This e-mail and/or any attachments contain Stem, Inc. confidential and proprietary information and material for the sole use of the intended recipient(s). Any review, use or distribution that has not been expressly authorized by Stem, Inc. is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Thank you. ________________________________ From: Guangya Liu <[email protected]<mailto:[email protected]>> Sent: Saturday, May 21, 2016 6:21 PM To: [email protected]<mailto:[email protected]> Subject: Re: Setting constraints Hi Scott, I think only setting "constraints": [["hostname", "UNIQUE"] is good enough, please refer to https://github.com/mesosphere/marathon/blob/master/docs/docs/constraints.md#unique-operator Thanks, Guangya On Sun, May 22, 2016 at 12:59 AM, Scott Kinney <[email protected]<mailto:[email protected]>> wrote: I would like to have one instance of consul and registrator running on every slave. I thought that by setting a attribute on every node then setting contraints like.. "constraints": [ ["exec_env", "GROUP_BY"], ["hostname", "UNIQUE"] ] If every node has the same 'exec_env' then they would all get one instance of this task ( i am not setting a value for 'instances' btw). What is a good way to be sure every slave has one of a particular task? Thanks! ________________________________ Scott Kinney | DevOps stem <http://www.stem.com/> | m 510.282.1299<tel:510.282.1299> 100 Rollins Road, Millbrae, California 94030 This e-mail and/or any attachments contain Stem, Inc. confidential and proprietary information and material for the sole use of the intended recipient(s). Any review, use or distribution that has not been expressly authorized by Stem, Inc. is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Thank you.
