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

Add better support for variables

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: master
    • Fix Version/s: master, 4.6.0
    • Component/s: pegasus-plan
    • Labels:
      None

      Description

      We often have this problem where we need to generate a site catalog because we have something in there that is dynamic, like a username or something. Similar issues exist for the TC, RC and DAX.

      It would be nice if we could insert environment variables into these files. For example, in the site catalog we could have:

      <profile namespace="globus" key="project">$PROJECT</profile>

      Or:

      <directory type="shared-storage" path="/project/projectdirs/m2187/sns/$RUN">

      Or in the RC:

      production_200.conf file://$PWD/production_200.conf pool="local"

      We could even have pegasus-defined variables, like:

      <job id="ID0000001" name="echo">
          <argument>$PEGASUS_JOBID $PEGASUS_WF_UUID</argument>
      </job>

      Or something crazier, like:

      <job id="ID0000001" name="ping">
          <argument>-c 5 $(uname -n)</argument>
      </job>

      Undefined variables cause the planner to fail.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                vahi Karan Vahi
                Reporter:
                gideon Gideon Juve (Inactive)
              • Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: