Skip to content

i-VRESSE/workflow-comparison

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

34 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Comparison of existing workflow engines

See if any of them can be used as base for ivresse. Each directory holds report for a workflow engine.

User stories

Prebaked workflow

Redo workflow

Do part of prebaked workflow

Replace node with alternative

Own code in workflow

Requirements

  • Submit job to a queue
  • Job is constructed out of parts that can be replaced with alternate implementations
  • Part of job can be array of computations
  • Multi user
    • authenicate against openid connect
    • data from users should not be readable by other unless
  • Files need to be on shared filesystem or downloaded/uploaded
  • Compute on
    • local machine for testing or small deployments
    • SLURM cluster
    • cloud (VM/container/function)
  • Compute on disk intensive on SLURM cluster and rest on cloud
  • For maintenance disable SLURM cluster so all calculations are done in cloud or vice versa
  • Has graphical way to construct a workflow from nodes

API standards

It would be nice if the compute orchestrator is using a standardized API to prevent vendor lock-in.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published