Jorge issues

Results 6 issues of


                                            Jorge

Allow user interactive steps between plugins.

Each plugin specifies in its output directory a FE viewer for certain important files from the list of known FE viewers. The list of known viewers could be documented and...

priority: low

CUBE should only allow the creation of a plugin pipeline if all the plugins in the pipeline have a common compute resource. The pipeline will be able to run in any of the compute resources in the set of common compute resources. When the ChRIS admin registers a pipeline from the ChRIS store he/she must specify a compute resource which will be inherited by all the pipeline's plugins.

Move validation methods calls from views code to within serializer's is_valid method (eg. validate_previous call)

Add to Swarm scheduler “expected resources” the same way it's done for Openshift: `number_of_workers`, `cpu_limit`, `memory_limit`, `gpu_limit`

enhancement

good first issue

`activeDeadlineSeconds` should be set to 24h for the job object in the openshiftmgr's schedule method. `ttlSecondsAfterFinished` should as well be set to at least 2h.

Jorge

Allow *user interactive steps* between plugins.

Move validation methods calls from views code to within serializer's is_valid method (eg. validate_previous call)

Add to Swarm scheduler “expected resources” the same way it's done for Openshift: `number_of_workers`, `cpu_limit`, `memory_limit`, `gpu_limit`

`activeDeadlineSeconds` should be set to 24h for the job object in the openshiftmgr's schedule method. `ttlSecondsAfterFinished` should as well be set to at least 2h.

`backoffLimit` should be set to 0 or at most 1 for the job object in the openshiftmgr's schedule method

Allow user interactive steps between plugins.