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

Add support for hold/release of a workflow

XMLWordPrintable

    • Type: Icon: New Feature New Feature
    • Resolution: Fixed
    • Priority: Icon: Major Major
    • master, 4.5.0
    • Affects Version/s: master
    • Component/s: None
    • None

      One way to do this would be to create pegasus-hold and pegasus-release scripts to allow users to hold and release workflows. They would be wrappers around condor_hold and condor_release that know how to identify the DAGMan job(s) associated with a Pegasus workflow. They may need extra logic to handle hierarchical workflows.

      This was a feature mentioned by SCEC in relation to Ensemble Manager. They have cases where they would like to be able to hold their workflows to prevent them from failing repeatedly until they can resolve an issue with their infrastructure.

            Assignee:
            rynge Mats Rynge
            Reporter:
            gideon Gideon Juve (Inactive)
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: