SGW-02: Transfer files to and from a community resource, SGW-04: Enable gateway users to transfer files to or from a community resource
Effort and Costs:
The documentation is already started and just needs a couple of details wrapped up. Nailing down the details may take ~2 days of total effort, spread across several weeks due to the need to involve multiple people from a few teams. When the details are finalized, it will take a couple of hours to put the documentation into a form that can be made available online and referenced.
The test plan will probably take a couple of hours to write up, assuming there's a template available.
The effort required for testing will depend on the test plan, of course. If the plan is to ask a gateway that's already using this method to confirm that it's how they are doing it, the effort will be pretty small, maybe a day total. If the plan is to create a new sample gateway and follow the instructions, it's likely to take a week or more simply due to the complexity of starting a new gateway from scratch.
Documentation for science gateway developers that explains how to set up two kinds of transfers:
For SGW-02, enable the gateway to transfer files to/from the gateway user's local system.
For SGW-04, enable gateway users to transfer files to/from the XSEDE resources the gateway uses. (E.g., SDSC Comet.)
We need to document and prepare training materials on the use of XSEDE/Globus system features to accomplish the following things in the context of developing a science gateway. This is required for the 6-8-2016 Capability Delivery Plan for SGW-4.
Identify XSEDE storage systems that support Globus sharing.
Use the Globus transfer API to create a shared endpoint on an XSEDE storage system.
Instruct end users to download and install Globus Connect Personal on Windows, Mac, and/or Linux systems.