orchestra issueshttps://gitlab.inria.fr/apere/orchestra/-/issues2019-09-25T15:18:38+02:00https://gitlab.inria.fr/apere/orchestra/-/issues/23Ability to mask cpus and gpus2019-09-25T15:18:38+02:00PERE AlexandreAbility to mask cpus and gpusV0.3.0PERE AlexandrePERE Alexandrehttps://gitlab.inria.fr/apere/orchestra/-/issues/14Non-maximal number of tasks2019-08-20T14:41:07+02:00PERE AlexandreNon-maximal number of tasksWhen using runaway, the number of tasks that starts at the same time is low compared to the maximum number of tasks.
This should be checked forWhen using runaway, the number of tasks that starts at the same time is low compared to the maximum number of tasks.
This should be checked forV0.2.0https://gitlab.inria.fr/apere/orchestra/-/issues/9Runaway batch executor pool size2019-08-22T08:45:59+02:00PERE AlexandreRunaway batch executor pool sizeIn runaway, the pool-size of the executor is currently set to one as can be seen there:
https://gitlab.inria.fr/apere/orchestra/blob/master/runaway-cli/src/main.rs#L380
We should lift this limitation to allow runaway to use as much thr...In runaway, the pool-size of the executor is currently set to one as can be seen there:
https://gitlab.inria.fr/apere/orchestra/blob/master/runaway-cli/src/main.rs#L380
We should lift this limitation to allow runaway to use as much threads as possible.V0.2.0https://gitlab.inria.fr/apere/orchestra/-/issues/34Add stdout, stderr and ecode to scheduler message2019-12-19T08:59:04+01:00PERE AlexandreAdd stdout, stderr and ecode to scheduler messageThe scheduler message should contain the stdout, stderr and exit code of the execution. This would allow the sched subcommand, not only to enable optimization and stuff, but also to reschedule failed executions or so.The scheduler message should contain the stdout, stderr and exit code of the execution. This would allow the sched subcommand, not only to enable optimization and stuff, but also to reschedule failed executions or so.https://gitlab.inria.fr/apere/orchestra/-/issues/33Parametric profiles2019-12-19T08:58:53+01:00PERE AlexandreParametric profilesParametric profiles, are profiles whose allocation can be parameterized by environment variables captured at run time. To allow that, we have to initiate the host with the variables captured at the beginning of the program.Parametric profiles, are profiles whose allocation can be parameterized by environment variables captured at run time. To allow that, we have to initiate the host with the variables captured at the beginning of the program.https://gitlab.inria.fr/apere/orchestra/-/issues/20Dynamic number of tasks per nodes2019-09-25T15:18:49+02:00PERE AlexandreDynamic number of tasks per nodesSome users may want to have say one task per gpu on a node, but the number of gpus may change from node to node. For this reason we should turn the static number of tasks per nodes into a command that allows to set the number of tasks de...Some users may want to have say one task per gpu on a node, but the number of gpus may change from node to node. For this reason we should turn the static number of tasks per nodes into a command that allows to set the number of tasks depending on the node capacity.PERE AlexandrePERE Alexandrehttps://gitlab.inria.fr/apere/orchestra/-/issues/19Add more environment variables to profiles2019-09-25T15:17:46+02:00PERE AlexandreAdd more environment variables to profilesProfiles should be enhanced by more environment variables such as:
+ The id of the execution
+ A random seedProfiles should be enhanced by more environment variables such as:
+ The id of the execution
+ A random seedPERE AlexandrePERE Alexandrehttps://gitlab.inria.fr/apere/orchestra/-/issues/18Use `liborchestra::application` in runaway2019-10-22T14:28:33+02:00PERE AlexandreUse `liborchestra::application` in runawayCurrently, runaway uses its own implementation of the application logic. We should use the `liborchestra::application` instead.
Plus, subcommands functions are super long in runaway. Using the application module will help to change that. Currently, runaway uses its own implementation of the application logic. We should use the `liborchestra::application` instead.
Plus, subcommands functions are super long in runaway. Using the application module will help to change that. https://gitlab.inria.fr/apere/orchestra/-/issues/16Change timers implementation2019-11-08T17:12:16+01:00PERE AlexandreChange timers implementationCurrently asynchronous timers create a thread every time a delay is needed :). That is awful.
We could implement something like tokio_timer, with a resource clock running in a separate thread, that wakes up tasks when the delay is over.Currently asynchronous timers create a thread every time a delay is needed :). That is awful.
We could implement something like tokio_timer, with a resource clock running in a separate thread, that wakes up tasks when the delay is over.https://gitlab.inria.fr/apere/orchestra/-/issues/13Automate fetchignore2019-08-23T11:19:15+02:00PERE AlexandreAutomate fetchignoreIn runaway, the fetchignore could essentially be removed by monitoring the created files.In runaway, the fetchignore could essentially be removed by monitoring the created files.https://gitlab.inria.fr/apere/orchestra/-/issues/12Adds completion for profile names2019-08-22T10:33:16+02:00PERE AlexandreAdds completion for profile namesWhen using runaway, there is no completion available for the profiles names. It would be nice to have it.When using runaway, there is no completion available for the profiles names. It would be nice to have it.https://gitlab.inria.fr/apere/orchestra/-/issues/11Allow config parser to parse different indentation schemes2019-08-22T14:52:06+02:00PERE AlexandreAllow config parser to parse different indentation schemesLots of editors automatically turn tabs into spaces. We should be able to parse the config file nonetheless.Lots of editors automatically turn tabs into spaces. We should be able to parse the config file nonetheless.