• Table of contents
• Crunch1-in-Crunch2 (DRAFT)
  • Background
  • Requirements

Crunch1-in-Crunch2 (DRAFT)¶

Detail about how Crunch2 runs jobs that were written for Crunch1.

See

• Crunch2 Jobs API

Background¶

In order for Crunch2 to replace Crunch1, Crunch2 must be capable of running jobs that rely on Crunch1's API. Examples:

• run-command
• arv-run (via run-command)
• existing tutorial/example jobs
• user scripts based on existing tutorials

Requirements¶

Crunch1 jobs rely on the following pieces:

• arv-run-pipeline-instance fulfills a pipeline instance by submitting and monitoring jobs using the Crunch1 API. (This piece could be replaced by a Crunch2 equivalent if necessary; however, users may have written job-submission/monitoring scripts along the same lines and it's ideal if these also continue to work.)
• Keep mount available within the container
• Some environment variables (CRUNCH_SRC, ARVADOS_API_*, etc)
• jobs and job_tasks APIs