Cloud Planning with Condor-I/O cannot use deep filenames

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • 3.1.2
    • Affects Version/s: master
    • Component/s: Pegasus Planner
    • None

      When using Condor-I/O in the cloud planning environment, we cannot use deep filenames i.e. with directories.

      However, it is possible and envisioned that I install the CA certificates and Globus gridftp client tools on the remote cloud resource. Given a valid user certificate proxy that is staged, we should be able to have regular Pegasus stage-io jobs using Mats's new transfer client.

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

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 2 days
                2d
                Logged:
                Time Spent - Not Specified
                Not Specified