Re: Setting constraints

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 | m 510.282.129

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 Ko

Re: Setting constraints

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).

Re: Setting constraints

Hi Guangya, That doens't deploy the apps automatically to every slave. only one slave will get one of each. Scott Kinney | DevOps stem | m 510.282.1299 100 Rollins Road, Millbrae, California 94030 This e-mail and/or any attachments c

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 wrote: > I would like to have one in

Re: Marathon error

Just because the Marathon scheduler is running, doesn't mean that it has successfully registered with Mesos. Check the scheduler log and Mesos master log for messages about attempted/failed registrations. On Thu, May 19, 2016 at 4:28 AM, wrote: > Hi, > > > > Marathon service is running. > > But

Re: view attributes

perfect thank you Chris Scott Kinney | DevOps stem | 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

Re: view attributes

Scott, It's available from the master at the /slaves endpoint. For example, http master:5050/slaves | jq '.slaves[] | .id,.attributes' "108df187-4ee6-41fb-9c06-a02cbdbdfd7c-S5" {} "108df187-4ee6-41fb-9c06-a02cbdbdfd7c-S4" {} "108df187-4ee6-41fb-9c06-a02cbdbdfd7c-S3" { "public_ip": "true" } On S

Setting constraints

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' th

view attributes

I'm setting slave attributes in file under /etc/mesos-slave/attributes directory but i dont see a convenient way to view the salve's attributes in mesos or marathon ui. Thanks, Scott Scott Kinney | DevOps stem | m 510.282.1299 100 R