Some context in icgc-argo/workflow-roadmap#148

Improve the current cancel method to throw a specific and consistent exit code so that the retry mechanism could behave upon the return code.

Currently at Task Logs, we have the following information:

Can we add workdir information for each task into Task Logs? This will help us to locate the files for debug purposes.

Goal is to optimize utilization of the compute system as much as possible. Make sure that the cores are not idle - find the optimal active time for the system.

• Scale testing plan and results documentation
• Plan of what to test and how to record
• test a single sample and record # of cores, measure idle rate/speed at each step
• develop a matrix of cores assigned/step and record to get the best configuration
• Record data metrics from sample as part of the workflow
• file size /lane
• Final alignment file size

Exit Criteria

• Optimization report for the alignment workflow
• Meet with Christina

Design a GraphQL API to communicate with WES API and ARGO API

Scope of this is to produce a specification on what the eventual Domain Layer will need to be?

Refer to platform-ui Dockerfile:
https://github.com/icgc-argo/platform-ui/blob/develop/Dockerfile

The main process must run as user $APP_UID, not as root