Uploaded image for project: 'Pegasus'
  1. Pegasus
  2. PM-345 Stampede Schema Related Changes for Pegasus 3.1
  3. PM-329

job id's in the DAX to be passed to kickstart invocation

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Fixed
    • Major
    • master, 3.1
    • master, 3.1
    • Pegasus Planner
    • None

    Description

      currently the derivation is passed as value of the -N option to kickstart.

      For 3.1, the derivation should be set to the logical id in the DAX for that job.

      For pegasus generated jobs null should be passed

      For clustered jobs, the .in files should have a comment for each invocation that includes both transformation, derivation and the associated task id. It should use the format below:

      # task_id transformation derivation

      # 1 montage::mProject ID0000001
      # 2 montage::mProject ID0000002
      ...

      For non-clustered jobs, we need to include the dax id in the submit file as a classad, it should be of the form:

      +pegasus_wf_dax_job_id = "xxxx"

      where "xxxx" can be "null" for Pegasus generated jobs.

      The above comments can go anywhere in the file, can be interleaved with the invocation lines, or put together at the end.

      Attachments

        Issue Links

          Activity

            People

              vahi Karan Vahi
              vahi Karan Vahi
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: