As Connor already mentioned you can use URL for your artifact/app - there is whole REST API - artifact store - for working with artifacts - look at
https://mesosphere.github.io/marathon/docs/artifact-store.html 2015-07-29 18:47 GMT+02:00 Connor Doyle <[email protected]>: > In Marathon the executor ID is unique every time, so tasks and executors > will be in 1:1 correspondence. More generally, if you re-use the executor > info message when launching tasks, a single executor can handle multiple > tasks simultaneously. > > On Jul 29, 2015, at 09:43, Aaron Carey <[email protected]> wrote: > > ah cool! Will that run as one instance per task, or one scheduler per > slave? > > > ------------------------------ > *From:* Connor Doyle [[email protected]] > *Sent:* 29 July 2015 17:24 > *To:* [email protected] > *Subject:* Re: Custom executor > > You don't even have to pre-load the executor on the slave boxes -- just > add it as a URL and it will be downloaded to the sandbox like any other > resource! > > On Jul 29, 2015, at 02:47, Aaron Carey <[email protected]> wrote: > > Ah I see.. so is it simply a case of making the executor file > executable, putting it on the slave, and supplying the path to it in the > JSON? > > Thanks! > > Aaron > > ------------------------------ > *From:* Ondrej Smola [[email protected]] > *Sent:* 29 July 2015 10:13 > *To:* [email protected] > *Subject:* Re: Custom executor > > Hi Aaron, > > custom executor should be supported by Marathon - i dont use it but from > tests in > > > https://github.com/mesosphere/marathon/blob/master/src/test/scala/mesosphere/mesos/TaskBuilderTest.scala#L236 > > there is a option to specify path to custom executor. > > https://mesosphere.github.io/marathon/docs/rest-api.html#post-/v2/apps > > in task definition there is "executor" json prop > > Chronos also supports this property > > > Download/create some simple executor and try to test it. > > > > > 2015-07-29 11:00 GMT+02:00 Aaron Carey <[email protected]>: > >> Hi Tim, >> >> We have some specific requirements for moving data around when executing >> tasks on slaves, I want to be able to 'check out' a selection of files, and >> possibly mount filesystems onto the slave (and subsequently into the >> executing docker container). The data required by each task is specified in >> our database. >> >> Basically I wanted to customise an executor to prepare the data on the >> slave before executing the docker container, rather than having to get the >> container to download its own data or attempt to mount NFS volumes itself. >> >> I hope that all makes sense, I couldn't find a simple solution to this >> using the existing architecture.. I'd love to know your thoughts though! >> >> Thanks, >> Aaron >> >> ------------------------------ >> *From:* Tim Chen [[email protected]] >> *Sent:* 28 July 2015 19:01 >> *To:* [email protected] >> *Subject:* Re: Custom executor >> >> Can you explain what your motivations are and what your new custom >> executor will do? >> >> Tim >> >> On Tue, Jul 28, 2015 at 5:08 AM, Aaron Carey <[email protected]> wrote: >> >>> Hi, >>> >>> Is it possible to build a custom executor which is not associated with a >>> particular scheduler framework? I want to be able to write a custom >>> executor which is available to multiple schedulers (eg Marathon, Chronos >>> and our own custom scheduler). Is this possible? I couldn't quite figure >>> out the best way to go about this from the docs? Is it possible to mix and >>> match languages for schedulers and executors? (ie one is python one is C++) >>> >>> Thanks, >>> Aaron >>> >> >> >
