kickstart location should be TC-overwritable

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Fixed
    • Priority: Major
    • 3.0
    • Affects Version/s: master
    • Component/s: Pegasus Planner
    • None

      In FG/cloud mode, I like to still use kickstarted jobs. However, instead of chosing the kickstart location from SC only based on the site of the job (yes, I know, this is how it classically came to be the way it is), it should be chosen on the existence of env::PEGASUS_HOME and possibly flags in the "pegasus" namespace in the job's profile after SC and TC have been applied. That should permit me to overwrite the location in the TC.

      I don't know, if this would apply to other ancillary jobs, too. But the less special treatment they receive, the less confusing Pegasus will be.

            Assignee:
            Karan Vahi
            Reporter:
            Jens Voeckler
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: