planner should use its own path to locate pegasus binaries instead of PATH

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

XMLWordPrintable

    • Type: Improvement
    • Resolution: Cannot Reproduce
    • Priority: Minor
    • master, 4.4.0
    • Affects Version/s: master, 4.3.2
    • Component/s: Pegasus Planner
    • None

      The planner currently uses the PATH variable to locate Pegasus binaries such as pegasus-create-dir if PEGASUS_HOME is not defined for the local site. This can cause problems if the PATH variable conflicts with the planner that the user invoked, and causes confusion if pegasus is not on the users PATH. Instead, the planner should use its own path to locate other Pegasus binaries. That approach should work in all cases regardless of how the user has configured their environment and will cause less confusion for users.

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

              Created:
              Updated:
              Resolved:
              Archived: