-
Notifications
You must be signed in to change notification settings - Fork 55
Architecture Diagram
Matt McLoughlin edited this page May 2, 2023
·
8 revisions
- Client calls Cromwell (hosted on AKS) directly using REST API, or
- Client uploads the workflow and trigger file to the Azure Storage container, kicking off the Trigger Service (hosted on AKS) which calls Cromwell on Azure (hosted on AKS)
- Cromwell interprets the workflow and uses the TES backend (hosted on AKS) to sends execute tasks on Azure Batch
- CoA and TES use PostgreSQL on Azure as its database to store TesTasks as JSON
- TriggerService and TES both sends logs/is monitored by Application Insights
- Azure Batch has one node per task (allowing each task to run sandboxed in parallel)
- Azure Batch nodes will pull images from ACR (or external container registries) as defined in your WDL/CDL
- Azure Batch has its own Azure Storage for its lifetime
- Your completed (or failed) workflow results will be deposited in the appropriate Azure Storage container
To search, expand the Pages section above.