OK, got it, thanks. That makes it useless for data backup though, if chronos starts new container on the node where it does not have an access to db data
On Tue, Jan 10, 2017 at 11:14 AM, Stephen Gran <stephen.g...@piksel.com> wrote: > Hi, > > This is what I'm trying to say, perhaps not very clearly: > the task 'ls /' will be run in a 4th container. It is a new process. > > Cheers, > > On 10/01/17 15:54, l vic wrote: > > Great, but I have several servers: 3 different containers running on 3 > > different nodes. If i try to schedule the job : > > curl -L -H 'Content-Type: application/json' -X POST > > http://|chronos-node:|2002/scheduler/iso8601 > > <http://10.1.122.1:2002/scheduler/iso8601> -d ' > > { > > "schedule": "R10/2015-06-05T13:36:00Z/PT1M", > > "name": "test-container-job", > > "container": { > > "type": "DOCKER", > > "image": "<your test conatiner tag>", > > "network": "BRIDGE" > > }, > > "cpus": "0.1", > > "mem": "512", > > "uris" : ["file:///.dockercfg"], > > "command": "ls /" > > }' > > Will it schedule the job on all 3 nodes, or only the first one? Can I > > actually choose which one in my json? > > Thks > > > > On Tue, Jan 10, 2017 at 10:47 AM, Stephen Gran <stephen.g...@piksel.com > > <mailto:stephen.g...@piksel.com>> wrote: > > > > Hi, > > > > Chronos launches a new task to perform the job. Think of it more > like > > cron launching a new process when this is run on a single server. > > > > Cheers, > > > > On 10/01/17 15:31, l vic wrote: > > > If I have cluster of 3 running containers - how Chronos will > select one > > > to schedule the job? > > > > > > On Fri, Jan 6, 2017 at 1:33 PM, Radek Gruchalski < > ra...@gruchalski.com <mailto:ra...@gruchalski.com> > > > <mailto:ra...@gruchalski.com <mailto:ra...@gruchalski.com>>> > wrote: > > > > > > Chronos launches a task on Mesos whenever a scheduled event is > bound > > > to happen. > > > You can run a container task with Chronos, n problem: > > > > > > https://mesos.github.io/chronos/docs/api.html#job- > configuration > > <https://mesos.github.io/chronos/docs/api.html#job-configuration> > > > <https://mesos.github.io/chronos/docs/api.html#job- > configuration > > <https://mesos.github.io/chronos/docs/api.html#job-configuration>> > > > > > > Check the container field. > > > > > > – > > > Best regards, > > > Radek Gruchalski > > > ra...@gruchalski.com <mailto:ra...@gruchalski.com> > > <mailto:ra...@gruchalski.com <mailto:ra...@gruchalski.com>> > > > > > > > > > On January 6, 2017 at 7:17:36 PM, l vic (lvic4...@gmail.com > <mailto:lvic4...@gmail.com> > > > <mailto:lvic4...@gmail.com <mailto:lvic4...@gmail.com>>) > wrote: > > > > > >> Chronos is a separate service... I have database cluster > running > > >> as Mesos framework. I have to periodically schedule data > backups > > >> using shell scripts within running docker container. Is that > > >> possible with Chronos? > > >> > > >> On Fri, Jan 6, 2017 at 11:47 AM, Radek Gruchalski > > >> <ra...@gruchalski.com <mailto:ra...@gruchalski.com> > > <mailto:ra...@gruchalski.com <mailto:ra...@gruchalski.com>>> wrote: > > >> > > >> There are two options: > > >> > > >> - https://github.com/dcos/metronome < > https://github.com/dcos/metronome> > > >> <https://github.com/dcos/metronome < > https://github.com/dcos/metronome>> > > >> - https://github.com/mesos/chronos < > https://github.com/mesos/chronos> > > >> <https://github.com/mesos/chronos < > https://github.com/mesos/chronos>> > > >> > > >> while Metronome, apparently, being a successor of Chronos. > > >> > > >> – > > >> Best regards, > > >> Radek Gruchalski > > >> ra...@gruchalski.com <mailto:ra...@gruchalski.com> > > <mailto:ra...@gruchalski.com <mailto:ra...@gruchalski.com>> > > >> > > >> > > >> On January 6, 2017 at 5:40:45 PM, l vic ( > lvic4...@gmail.com <mailto:lvic4...@gmail.com> > > >> <mailto:lvic4...@gmail.com <mailto:lvic4...@gmail.com>>) > > wrote: > > >> > > >>> Hi, > > >>> Is there a way to schedule mesos framework task for > > execution > > >>> at certain day/time? > > >>> Thank youm > > >>> -V > > >> > > >> > > > > > > > -- > > Stephen Gran > > Senior Technical Architect > > > > picture the possibilities | piksel.com <http://piksel.com> > > > > > > -- > Stephen Gran > Senior Technical Architect > > picture the possibilities | piksel.com >
