Re: Deploying containers to every mesos slave node
You don't even need to create a custom framework: you can run a separate instance of Marathon for a dedicated role. On Thu, Mar 12, 2015 at 10:58 AM, Brian Devins wrote: > This was actually going to be my suggestion. You could create a custom > framework/scheduler to handle these types of tasks and configure mesos to > give priority to this framework using roles, and weights. > > On Thu, Mar 12, 2015 at 1:38 PM, Konrad Scherer < > konrad.sche...@windriver.com> wrote: > >> On 03/12/2015 04:54 AM, Aaron Carey wrote: >> >>> Hi All, >>> >>> In setting up our cluster, we require things like consul to be running >>> on all of >>> our nodes. I was just wondering if there was any sort of best practice >>> (or a >>> scheduler perhaps) that people could share for this sort of thing? >>> >> >> I am in a similar situation. I want to start a single "source cache" >> (over 200GB) data container on each of my builder nodes. I had the idea of >> creating a custom resource on each slave and creating a scheduler to handle >> this resource only. Has anyone tried this? The only problem I can see is >> that there is no way to prevent another scheduler from taking the offered >> custom resource, but since it is custom it seems unlikely. >> >> I would love to use Marathon for this, but looks like Marathon does not >> support custom resources and the issue[1] is in the backlog. Perhaps when >> Mesos and Marathon get dynamic resources[2] support? >> >> [1]: https://github.com/mesosphere/marathon/issues/375 >> [2]: https://issues.apache.org/jira/browse/MESOS-2018 >> >> -- >> Konrad Scherer, MTS, Linux Products Group, Wind River >> > >
Re: Deploying containers to every mesos slave node
This was actually going to be my suggestion. You could create a custom framework/scheduler to handle these types of tasks and configure mesos to give priority to this framework using roles, and weights. On Thu, Mar 12, 2015 at 1:38 PM, Konrad Scherer < konrad.sche...@windriver.com> wrote: > On 03/12/2015 04:54 AM, Aaron Carey wrote: > >> Hi All, >> >> In setting up our cluster, we require things like consul to be running on >> all of >> our nodes. I was just wondering if there was any sort of best practice >> (or a >> scheduler perhaps) that people could share for this sort of thing? >> > > I am in a similar situation. I want to start a single "source cache" (over > 200GB) data container on each of my builder nodes. I had the idea of > creating a custom resource on each slave and creating a scheduler to handle > this resource only. Has anyone tried this? The only problem I can see is > that there is no way to prevent another scheduler from taking the offered > custom resource, but since it is custom it seems unlikely. > > I would love to use Marathon for this, but looks like Marathon does not > support custom resources and the issue[1] is in the backlog. Perhaps when > Mesos and Marathon get dynamic resources[2] support? > > [1]: https://github.com/mesosphere/marathon/issues/375 > [2]: https://issues.apache.org/jira/browse/MESOS-2018 > > -- > Konrad Scherer, MTS, Linux Products Group, Wind River >
Re: Deploying containers to every mesos slave node
On 03/12/2015 04:54 AM, Aaron Carey wrote: Hi All, In setting up our cluster, we require things like consul to be running on all of our nodes. I was just wondering if there was any sort of best practice (or a scheduler perhaps) that people could share for this sort of thing? I am in a similar situation. I want to start a single "source cache" (over 200GB) data container on each of my builder nodes. I had the idea of creating a custom resource on each slave and creating a scheduler to handle this resource only. Has anyone tried this? The only problem I can see is that there is no way to prevent another scheduler from taking the offered custom resource, but since it is custom it seems unlikely. I would love to use Marathon for this, but looks like Marathon does not support custom resources and the issue[1] is in the backlog. Perhaps when Mesos and Marathon get dynamic resources[2] support? [1]: https://github.com/mesosphere/marathon/issues/375 [2]: https://issues.apache.org/jira/browse/MESOS-2018 -- Konrad Scherer, MTS, Linux Products Group, Wind River
Re: Deploying containers to every mesos slave node
No, this won't make it into 0.22. On Thu, Mar 12, 2015 at 10:28 AM, Gurvinder Singh < gurvinder.si...@uninett.no> wrote: > On 03/12/2015 02:00 PM, Tim St Clair wrote: > > You may want to also view > > - https://issues.apache.org/jira/browse/MESOS-1806 > > > > as folks have discussed straight up consul integration on that JIRA. > Any plans to resolve this JIRA for upcoming 0.22 release. > > - Gurvinder > > > > > > > > *From: *"Aaron Carey" > > *To: *user@mesos.apache.org > > *Sent: *Thursday, March 12, 2015 3:54:52 AM > > *Subject: *Deploying containers to every mesos slave node > > > > Hi All, > > > > In setting up our cluster, we require things like consul to be > > running on all of our nodes. I was just wondering if there was any > > sort of best practice (or a scheduler perhaps) that people could > > share for this sort of thing? > > > > Currently the approach is to use salt to provision each node and add > > consul/mesos slave process and so on to it, but it'd be nice to > > remove the dependency on salt. > > > > Thanks, > > Aaron > > > > > > > > > > -- > > Cheers, > > Timothy St. Clair > > Red Hat Inc. > >
Re: Deploying containers to every mesos slave node
On 03/12/2015 02:00 PM, Tim St Clair wrote: > You may want to also view > - https://issues.apache.org/jira/browse/MESOS-1806 > > as folks have discussed straight up consul integration on that JIRA. Any plans to resolve this JIRA for upcoming 0.22 release. - Gurvinder > > > > *From: *"Aaron Carey" > *To: *user@mesos.apache.org > *Sent: *Thursday, March 12, 2015 3:54:52 AM > *Subject: *Deploying containers to every mesos slave node > > Hi All, > > In setting up our cluster, we require things like consul to be > running on all of our nodes. I was just wondering if there was any > sort of best practice (or a scheduler perhaps) that people could > share for this sort of thing? > > Currently the approach is to use salt to provision each node and add > consul/mesos slave process and so on to it, but it'd be nice to > remove the dependency on salt. > > Thanks, > Aaron > > > > > -- > Cheers, > Timothy St. Clair > Red Hat Inc.
Re: Deploying containers to every mesos slave node
Hi all, the question for a way to start a task on all nodes has come up a couple of times on the Marathon ML and GH repo as well. The reason for not having this in Marathon is simple. We can’t guarantee that we’ll ever get offers for all the slaves and also we son’t know how many slaves are in the cluster. I think something like this would be a great addition to the Mesos API. Cheers, Dario > On 12 Mar 2015, at 06:36, Aaron Carey wrote: > > What base image are you using for your slave nodes? Salt doesn't seem to play > very nicely with CoreOS (unless anyone here has any tips?). > > In an ideal world we could spin up a node with just the mesos slave running > on it and then deploy consul as a docker container to it using a mesos > framework, removing the need for any kind of provisioning tool like salt > (assuming mesos slave is installed using cloud-init or something similar). > > > From: Shuai Lin [linshuai2...@gmail.com] > Sent: 12 March 2015 13:25 > To: user@mesos.apache.org > Subject: Re: Deploying containers to every mesos slave node > > We do the same thing: running consul on each mesos slave, and use saltstack > to provision it. Why do you want to get rid of salt? You always need some > tool to provision your server, right? > > Regards, > Shuai > > On Thu, Mar 12, 2015 at 4:54 PM, Aaron Carey <mailto:aca...@ilm.com>> wrote: > Hi All, > > In setting up our cluster, we require things like consul to be running on all > of our nodes. I was just wondering if there was any sort of best practice (or > a scheduler perhaps) that people could share for this sort of thing? > > Currently the approach is to use salt to provision each node and add > consul/mesos slave process and so on to it, but it'd be nice to remove the > dependency on salt. > > Thanks, > Aaron
RE: Deploying containers to every mesos slave node
What base image are you using for your slave nodes? Salt doesn't seem to play very nicely with CoreOS (unless anyone here has any tips?). In an ideal world we could spin up a node with just the mesos slave running on it and then deploy consul as a docker container to it using a mesos framework, removing the need for any kind of provisioning tool like salt (assuming mesos slave is installed using cloud-init or something similar). From: Shuai Lin [linshuai2...@gmail.com] Sent: 12 March 2015 13:25 To: user@mesos.apache.org Subject: Re: Deploying containers to every mesos slave node We do the same thing: running consul on each mesos slave, and use saltstack to provision it. Why do you want to get rid of salt? You always need some tool to provision your server, right? Regards, Shuai On Thu, Mar 12, 2015 at 4:54 PM, Aaron Carey mailto:aca...@ilm.com>> wrote: Hi All, In setting up our cluster, we require things like consul to be running on all of our nodes. I was just wondering if there was any sort of best practice (or a scheduler perhaps) that people could share for this sort of thing? Currently the approach is to use salt to provision each node and add consul/mesos slave process and so on to it, but it'd be nice to remove the dependency on salt. Thanks, Aaron
Re: Deploying containers to every mesos slave node
We do the same thing: running consul on each mesos slave, and use saltstack to provision it. Why do you want to get rid of salt? You always need some tool to provision your server, right? Regards, Shuai On Thu, Mar 12, 2015 at 4:54 PM, Aaron Carey wrote: > Hi All, > > In setting up our cluster, we require things like consul to be running on > all of our nodes. I was just wondering if there was any sort of best > practice (or a scheduler perhaps) that people could share for this sort of > thing? > > Currently the approach is to use salt to provision each node and add > consul/mesos slave process and so on to it, but it'd be nice to remove the > dependency on salt. > > Thanks, > Aaron >
Re: Deploying containers to every mesos slave node
You may want to also view - https://issues.apache.org/jira/browse/MESOS-1806 as folks have discussed straight up consul integration on that JIRA. - Original Message - > From: "Aaron Carey" > To: user@mesos.apache.org > Sent: Thursday, March 12, 2015 3:54:52 AM > Subject: Deploying containers to every mesos slave node > Hi All, > In setting up our cluster, we require things like consul to be running on all > of our nodes. I was just wondering if there was any sort of best practice > (or a scheduler perhaps) that people could share for this sort of thing? > Currently the approach is to use salt to provision each node and add > consul/mesos slave process and so on to it, but it'd be nice to remove the > dependency on salt. > Thanks, > Aaron -- Cheers, Timothy St. Clair Red Hat Inc.
Re: Deploying containers to every mesos slave node
i've only done it by accident, and noted that it worked. i have no idea if there are unpleasant side effects in mesos or marathon because of the unsatisfiable constraints ! On 12 Mar 2015, at 09:33, Aaron Carey wrote: Thanks Craig, I'll have a look into this approach. It does feel a little flaky though, I suspect it may be easy for things to get out of sync, I'll see how we get on. Thanks! Aaron -- *From:* craig w [codecr...@gmail.com] *Sent:* 12 March 2015 09:19 *To:* user@mesos.apache.org *Subject:* Re: Deploying containers to every mesos slave node Perhaps you could query the Mesos API to see how many slaves there are, then use that in the request to Marathon. On Thu, Mar 12, 2015 at 5:09 AM, Michael Neale wrote: > It would be idea if there was as a way to specify to marathon the number > of instances to be a variable representing the mesos slaves (I don't think > possible right now). > On Thu, 12 Mar 2015 at 8:07 pm craig w wrote: > >> If you know when the scaling occurs (perhaps there's an API you can query >> or maybe it can notify you), then you can update the configuration for the >> application (deployed using marathon) to change the number of instances >> (via the Marathon REST API). >> >> On Thu, Mar 12, 2015 at 5:03 AM, Aaron Carey wrote: >> >>> Hi Craig, >>> >>> I'd looked into that, but I was thinking this may cause issues when our >>> cluster auto scales up or down, as instances would no longer equal slaves? >>> >>> Thanks, >>> Aaron >>> >>> ---------- >>> *From:* craig w [codecr...@gmail.com] >>> *Sent:* 12 March 2015 08:57 >>> *To:* user@mesos.apache.org >>> *Subject:* Re: Deploying containers to every mesos slave node >>> >>>Aaron, >>> >>> You could use Marathon (a Mesos framework) to deploy a container to >>> each host by using constraints [1] and setting the number of instances of >>> the container to equal the number of slaves. >>> >>> [1] constraints - >>> https://mesosphere.github.io/marathon/docs/constraints.html >>> >>> On Thu, Mar 12, 2015 at 4:54 AM, Aaron Carey wrote: >>> >>>> Hi All, >>>> >>>> In setting up our cluster, we require things like consul to be running >>>> on all of our nodes. I was just wondering if there was any sort of best >>>> practice (or a scheduler perhaps) that people could share for this sort of >>>> thing? >>>> >>>> Currently the approach is to use salt to provision each node and add >>>> consul/mesos slave process and so on to it, but it'd be nice to remove the >>>> dependency on salt. >>>> >>>> Thanks, >>>> Aaron >>>> >>> >>> >>> >>> -- >>> >>> https://github.com/mindscratch >>> https://www.google.com/+CraigWickesser >>> https://twitter.com/mind_scratch >>> https://twitter.com/craig_links >>> >>> >> >> >> -- >> >> https://github.com/mindscratch >> https://www.google.com/+CraigWickesser >> https://twitter.com/mind_scratch >> https://twitter.com/craig_links >> >> -- https://github.com/mindscratch https://www.google.com/+CraigWickesser https://twitter.com/mind_scratch https://twitter.com/craig_links
RE: Deploying containers to every mesos slave node
Thanks Craig, I'll have a look into this approach. It does feel a little flaky though, I suspect it may be easy for things to get out of sync, I'll see how we get on. Thanks! Aaron From: craig w [codecr...@gmail.com] Sent: 12 March 2015 09:19 To: user@mesos.apache.org Subject: Re: Deploying containers to every mesos slave node Perhaps you could query the Mesos API to see how many slaves there are, then use that in the request to Marathon. On Thu, Mar 12, 2015 at 5:09 AM, Michael Neale mailto:michael.ne...@gmail.com>> wrote: It would be idea if there was as a way to specify to marathon the number of instances to be a variable representing the mesos slaves (I don't think possible right now). On Thu, 12 Mar 2015 at 8:07 pm craig w mailto:codecr...@gmail.com>> wrote: If you know when the scaling occurs (perhaps there's an API you can query or maybe it can notify you), then you can update the configuration for the application (deployed using marathon) to change the number of instances (via the Marathon REST API). On Thu, Mar 12, 2015 at 5:03 AM, Aaron Carey mailto:aca...@ilm.com>> wrote: Hi Craig, I'd looked into that, but I was thinking this may cause issues when our cluster auto scales up or down, as instances would no longer equal slaves? Thanks, Aaron From: craig w [codecr...@gmail.com<mailto:codecr...@gmail.com>] Sent: 12 March 2015 08:57 To: user@mesos.apache.org<mailto:user@mesos.apache.org> Subject: Re: Deploying containers to every mesos slave node Aaron, You could use Marathon (a Mesos framework) to deploy a container to each host by using constraints [1] and setting the number of instances of the container to equal the number of slaves. [1] constraints - https://mesosphere.github.io/marathon/docs/constraints.html On Thu, Mar 12, 2015 at 4:54 AM, Aaron Carey mailto:aca...@ilm.com>> wrote: Hi All, In setting up our cluster, we require things like consul to be running on all of our nodes. I was just wondering if there was any sort of best practice (or a scheduler perhaps) that people could share for this sort of thing? Currently the approach is to use salt to provision each node and add consul/mesos slave process and so on to it, but it'd be nice to remove the dependency on salt. Thanks, Aaron -- https://github.com/mindscratch https://www.google.com/+CraigWickesser https://twitter.com/mind_scratch https://twitter.com/craig_links -- https://github.com/mindscratch https://www.google.com/+CraigWickesser https://twitter.com/mind_scratch https://twitter.com/craig_links -- https://github.com/mindscratch https://www.google.com/+CraigWickesser https://twitter.com/mind_scratch https://twitter.com/craig_links
Re: Deploying containers to every mesos slave node
you could perhaps use the hostname:UNIQUE constraint and set the number of tasks to the expected maximum number of slaves On 12 Mar 2015, at 09:20, craig w wrote: Perhaps you could query the Mesos API to see how many slaves there are, then use that in the request to Marathon. On Thu, Mar 12, 2015 at 5:09 AM, Michael Neale wrote: > It would be idea if there was as a way to specify to marathon the number > of instances to be a variable representing the mesos slaves (I don't think > possible right now). > On Thu, 12 Mar 2015 at 8:07 pm craig w wrote: > >> If you know when the scaling occurs (perhaps there's an API you can query >> or maybe it can notify you), then you can update the configuration for the >> application (deployed using marathon) to change the number of instances >> (via the Marathon REST API). >> >> On Thu, Mar 12, 2015 at 5:03 AM, Aaron Carey wrote: >> >>> Hi Craig, >>> >>> I'd looked into that, but I was thinking this may cause issues when our >>> cluster auto scales up or down, as instances would no longer equal slaves? >>> >>> Thanks, >>> Aaron >>> >>> -------------- >>> *From:* craig w [codecr...@gmail.com] >>> *Sent:* 12 March 2015 08:57 >>> *To:* user@mesos.apache.org >>> *Subject:* Re: Deploying containers to every mesos slave node >>> >>>Aaron, >>> >>> You could use Marathon (a Mesos framework) to deploy a container to >>> each host by using constraints [1] and setting the number of instances of >>> the container to equal the number of slaves. >>> >>> [1] constraints - >>> https://mesosphere.github.io/marathon/docs/constraints.html >>> >>> On Thu, Mar 12, 2015 at 4:54 AM, Aaron Carey wrote: >>> >>>> Hi All, >>>> >>>> In setting up our cluster, we require things like consul to be running >>>> on all of our nodes. I was just wondering if there was any sort of best >>>> practice (or a scheduler perhaps) that people could share for this sort of >>>> thing? >>>> >>>> Currently the approach is to use salt to provision each node and add >>>> consul/mesos slave process and so on to it, but it'd be nice to remove the >>>> dependency on salt. >>>> >>>> Thanks, >>>> Aaron >>>> >>> >>> >>> >>> -- >>> >>> https://github.com/mindscratch >>> https://www.google.com/+CraigWickesser >>> https://twitter.com/mind_scratch >>> https://twitter.com/craig_links >>> >>> >> >> >> -- >> >> https://github.com/mindscratch >> https://www.google.com/+CraigWickesser >> https://twitter.com/mind_scratch >> https://twitter.com/craig_links >> >> -- https://github.com/mindscratch https://www.google.com/+CraigWickesser https://twitter.com/mind_scratch https://twitter.com/craig_links
Re: Deploying containers to every mesos slave node
Perhaps you could query the Mesos API to see how many slaves there are, then use that in the request to Marathon. On Thu, Mar 12, 2015 at 5:09 AM, Michael Neale wrote: > It would be idea if there was as a way to specify to marathon the number > of instances to be a variable representing the mesos slaves (I don't think > possible right now). > On Thu, 12 Mar 2015 at 8:07 pm craig w wrote: > >> If you know when the scaling occurs (perhaps there's an API you can query >> or maybe it can notify you), then you can update the configuration for the >> application (deployed using marathon) to change the number of instances >> (via the Marathon REST API). >> >> On Thu, Mar 12, 2015 at 5:03 AM, Aaron Carey wrote: >> >>> Hi Craig, >>> >>> I'd looked into that, but I was thinking this may cause issues when our >>> cluster auto scales up or down, as instances would no longer equal slaves? >>> >>> Thanks, >>> Aaron >>> >>> -------------- >>> *From:* craig w [codecr...@gmail.com] >>> *Sent:* 12 March 2015 08:57 >>> *To:* user@mesos.apache.org >>> *Subject:* Re: Deploying containers to every mesos slave node >>> >>>Aaron, >>> >>> You could use Marathon (a Mesos framework) to deploy a container to >>> each host by using constraints [1] and setting the number of instances of >>> the container to equal the number of slaves. >>> >>> [1] constraints - >>> https://mesosphere.github.io/marathon/docs/constraints.html >>> >>> On Thu, Mar 12, 2015 at 4:54 AM, Aaron Carey wrote: >>> >>>> Hi All, >>>> >>>> In setting up our cluster, we require things like consul to be running >>>> on all of our nodes. I was just wondering if there was any sort of best >>>> practice (or a scheduler perhaps) that people could share for this sort of >>>> thing? >>>> >>>> Currently the approach is to use salt to provision each node and add >>>> consul/mesos slave process and so on to it, but it'd be nice to remove the >>>> dependency on salt. >>>> >>>> Thanks, >>>> Aaron >>>> >>> >>> >>> >>> -- >>> >>> https://github.com/mindscratch >>> https://www.google.com/+CraigWickesser >>> https://twitter.com/mind_scratch >>> https://twitter.com/craig_links >>> >>> >> >> >> -- >> >> https://github.com/mindscratch >> https://www.google.com/+CraigWickesser >> https://twitter.com/mind_scratch >> https://twitter.com/craig_links >> >> -- https://github.com/mindscratch https://www.google.com/+CraigWickesser https://twitter.com/mind_scratch https://twitter.com/craig_links
Re: Deploying containers to every mesos slave node
It would be idea if there was as a way to specify to marathon the number of instances to be a variable representing the mesos slaves (I don't think possible right now). On Thu, 12 Mar 2015 at 8:07 pm craig w wrote: > If you know when the scaling occurs (perhaps there's an API you can query > or maybe it can notify you), then you can update the configuration for the > application (deployed using marathon) to change the number of instances > (via the Marathon REST API). > > On Thu, Mar 12, 2015 at 5:03 AM, Aaron Carey wrote: > >> Hi Craig, >> >> I'd looked into that, but I was thinking this may cause issues when our >> cluster auto scales up or down, as instances would no longer equal slaves? >> >> Thanks, >> Aaron >> >> -- >> *From:* craig w [codecr...@gmail.com] >> *Sent:* 12 March 2015 08:57 >> *To:* user@mesos.apache.org >> *Subject:* Re: Deploying containers to every mesos slave node >> >>Aaron, >> >> You could use Marathon (a Mesos framework) to deploy a container to each >> host by using constraints [1] and setting the number of instances of the >> container to equal the number of slaves. >> >> [1] constraints - >> https://mesosphere.github.io/marathon/docs/constraints.html >> >> On Thu, Mar 12, 2015 at 4:54 AM, Aaron Carey wrote: >> >>> Hi All, >>> >>> In setting up our cluster, we require things like consul to be running >>> on all of our nodes. I was just wondering if there was any sort of best >>> practice (or a scheduler perhaps) that people could share for this sort of >>> thing? >>> >>> Currently the approach is to use salt to provision each node and add >>> consul/mesos slave process and so on to it, but it'd be nice to remove the >>> dependency on salt. >>> >>> Thanks, >>> Aaron >>> >> >> >> >> -- >> >> https://github.com/mindscratch >> https://www.google.com/+CraigWickesser >> https://twitter.com/mind_scratch >> https://twitter.com/craig_links >> >> > > > -- > > https://github.com/mindscratch > https://www.google.com/+CraigWickesser > https://twitter.com/mind_scratch > https://twitter.com/craig_links > >
Re: Deploying containers to every mesos slave node
If you know when the scaling occurs (perhaps there's an API you can query or maybe it can notify you), then you can update the configuration for the application (deployed using marathon) to change the number of instances (via the Marathon REST API). On Thu, Mar 12, 2015 at 5:03 AM, Aaron Carey wrote: > Hi Craig, > > I'd looked into that, but I was thinking this may cause issues when our > cluster auto scales up or down, as instances would no longer equal slaves? > > Thanks, > Aaron > > -- > *From:* craig w [codecr...@gmail.com] > *Sent:* 12 March 2015 08:57 > *To:* user@mesos.apache.org > *Subject:* Re: Deploying containers to every mesos slave node > >Aaron, > > You could use Marathon (a Mesos framework) to deploy a container to each > host by using constraints [1] and setting the number of instances of the > container to equal the number of slaves. > > [1] constraints - > https://mesosphere.github.io/marathon/docs/constraints.html > > On Thu, Mar 12, 2015 at 4:54 AM, Aaron Carey wrote: > >> Hi All, >> >> In setting up our cluster, we require things like consul to be running on >> all of our nodes. I was just wondering if there was any sort of best >> practice (or a scheduler perhaps) that people could share for this sort of >> thing? >> >> Currently the approach is to use salt to provision each node and add >> consul/mesos slave process and so on to it, but it'd be nice to remove the >> dependency on salt. >> >> Thanks, >> Aaron >> > > > > -- > > https://github.com/mindscratch > https://www.google.com/+CraigWickesser > https://twitter.com/mind_scratch > https://twitter.com/craig_links > > -- https://github.com/mindscratch https://www.google.com/+CraigWickesser https://twitter.com/mind_scratch https://twitter.com/craig_links
RE: Deploying containers to every mesos slave node
Hi Craig, I'd looked into that, but I was thinking this may cause issues when our cluster auto scales up or down, as instances would no longer equal slaves? Thanks, Aaron From: craig w [codecr...@gmail.com] Sent: 12 March 2015 08:57 To: user@mesos.apache.org Subject: Re: Deploying containers to every mesos slave node Aaron, You could use Marathon (a Mesos framework) to deploy a container to each host by using constraints [1] and setting the number of instances of the container to equal the number of slaves. [1] constraints - https://mesosphere.github.io/marathon/docs/constraints.html On Thu, Mar 12, 2015 at 4:54 AM, Aaron Carey mailto:aca...@ilm.com>> wrote: Hi All, In setting up our cluster, we require things like consul to be running on all of our nodes. I was just wondering if there was any sort of best practice (or a scheduler perhaps) that people could share for this sort of thing? Currently the approach is to use salt to provision each node and add consul/mesos slave process and so on to it, but it'd be nice to remove the dependency on salt. Thanks, Aaron -- https://github.com/mindscratch https://www.google.com/+CraigWickesser https://twitter.com/mind_scratch https://twitter.com/craig_links
Re: Deploying containers to every mesos slave node
Aaron, You could use Marathon (a Mesos framework) to deploy a container to each host by using constraints [1] and setting the number of instances of the container to equal the number of slaves. [1] constraints - https://mesosphere.github.io/marathon/docs/constraints.html On Thu, Mar 12, 2015 at 4:54 AM, Aaron Carey wrote: > Hi All, > > In setting up our cluster, we require things like consul to be running on > all of our nodes. I was just wondering if there was any sort of best > practice (or a scheduler perhaps) that people could share for this sort of > thing? > > Currently the approach is to use salt to provision each node and add > consul/mesos slave process and so on to it, but it'd be nice to remove the > dependency on salt. > > Thanks, > Aaron > -- https://github.com/mindscratch https://www.google.com/+CraigWickesser https://twitter.com/mind_scratch https://twitter.com/craig_links
Deploying containers to every mesos slave node
Hi All, In setting up our cluster, we require things like consul to be running on all of our nodes. I was just wondering if there was any sort of best practice (or a scheduler perhaps) that people could share for this sort of thing? Currently the approach is to use salt to provision each node and add consul/mesos slave process and so on to it, but it'd be nice to remove the dependency on salt. Thanks, Aaron
