update the semantics for the output-dir option

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • master, 4.3
    • Affects Version/s: master
    • Component/s: Pegasus Planner
    • None

      User Request from SCEC:

      SCEC is using the --output-dir option to specify different output directories for each sub workflow in a hierarchal workflow to an output site

      In 4.2, if a relative path is passed as the --output-dir option it gets resolved to the local site as an absolute path. This resolving is incorrect, if a user has specified a non local site as the output site. The only way to specify this in 4.2 is to give the correct absolute path in the --output-dir option on the remote site.

      SCEC has a request, where they want the path to appended from the storage directory specified already in the output site.
      For 4.3, we will implement this . However, the appending will not happen for local sites as for that the directory from where the planner is invoked / the command line will be used to determine the directory

            Assignee:
            Karan Vahi
            Reporter:
            Karan Vahi
            Archiver:
            Rajiv Mayani

              Created:
              Updated:
              Resolved:
              Archived: