airavata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject airavata-sandbox git commit: Update README for helix-playground
Date Thu, 22 Jun 2017 19:29:11 GMT
Repository: airavata-sandbox
Updated Branches:
  refs/heads/master ad8cde1f4 -> 9f244e583

Update README for helix-playground


Branch: refs/heads/master
Commit: 9f244e5830a7e4b636e96bf56e8708c276fb0930
Parents: ad8cde1
Author: Gourav Shenoy <>
Authored: Thu Jun 22 15:29:08 2017 -0400
Committer: Gourav Shenoy <>
Committed: Thu Jun 22 15:29:08 2017 -0400

 helix-playground/ | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/helix-playground/ b/helix-playground/
index 3be47ce..7fad1c1 100644
--- a/helix-playground/
+++ b/helix-playground/
@@ -14,7 +14,7 @@ Apart from these, Helix also provides out-of-the-box APIs to perform Distributed
 * Workflow – A combination of jobs arranged in a DAG. In a ONE-TIME workflow, once all
jobs are completed, the workflow ends. In a RECURRING workflow, you can schedule workflows
to run periodically.
 * Job Queues – Another type of workflow, but never ends – keeps accepting new incoming
jobs. Ends only when user terminates it.
+![helix-task-framework](images/helix-task-framework.png "Helix Task Framework Workflow")
 * Helix also allows users to share data (key-value pairs) across Tasks/Jobs/Workflows. The
content stored at workflow layer can shared by different jobs belong to this workflow. Similarly
content persisted at job layer can shared by different tasks nested in this job.
 * Helix provides APIs to POLL either a JOB or WORKFLOW to reach a particular state.

View raw message