Uploaded image for project: 'Pegasus'
  1. Pegasus
  2. PM-304

recursive planning ahead

XMLWordPrintable

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major Major
    • 4.3
    • Affects Version/s: None
    • Component/s: Pegasus Planner
    • None

      In the FG wf-of-wf case, there is an outer workflow, presumably script-generated, that incorporates an application workflow as inner node. When planning the outer workflow, at least the first level of the inner workflow should be planned right there and then, too. I am proposing a -recursive flag that takes an optional integer argument, and defaults to a very large number (i.e. max positive integer). This number is the maxdepth of the recursion, and defaults to virtually infinite (the large number), but can be pruned by the user giving a number. In the FG case, I would give something like "-recursive 1", which means to plan the outer workflow and the first child workflow(s), but no grand-child workflow(s).

      Note, I believe the recursive option should not be passed to workflow-planning pre scripts in sub workflows.

            Assignee:
            vahi Karan Vahi
            Reporter:
            voeckler Jens Voeckler
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: