JIRA Issue

[#XCI-3] Document how Science Gateways can enable direct end-user-to-XSEDE-SP-resource file transfers

[XCI-3] Document how Science Gateways can enable direct end-user-to-XSEDE-SP-resource file transfers Created: 06/07/2016  Updated: 08/20/2020

Status: Test Readiness Review
Project: XSEDE Cyberinfrastructure Integration
Component/s: Globus Sharing, Globus Transfer
Fix Version/s: PY8 (Sep '18 - Aug '19), PY9 (Sep '19 - Aug '20)

Type: XCI New Capability Priority: Critical
Reporter: Lee Liming Assignee: Unassigned
Resolution: Unresolved Votes: 0

Issue Links:
Blocks
is blocked by XCI-416 CDP update for SGW-4: New approach fo... In Progress
Target Operator:
XSEDE Science Gateways
XSEDE Priority: 3.6 UREP'16
XSEDE Areas:
RACD Data, RACD Integration Services
Use Case Priority: Low
Public activity link: https://software.xsede.org/display/xci-3
Devel Repository:
Show
https://software.xsede.org/svn/xci/activities/xci-003/trunk/
Use Cases:
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.
Deliverables:
  1. Documentation for science gateway developers that explains how to set up two kinds of transfers:
    1. For SGW-02, enable the gateway to transfer files to/from the gateway user's local system.
    2. For SGW-04, enable gateway users to transfer files to/from the XSEDE resources the gateway uses. (E.g., SDSC Comet.)
  2. Test plan
  3. Test report
Planned Launch Date:
Actual Launch Date:
Planned Design Review Date:
Planned Test Readiness Review Date:
Actual Test Readiness Review Date:
Planned Complete Date:
Activity Lead: Lee Liming
User documentation: https://docs.google.com/document/d/1BPcGq3p7eKHvdqmRADwGh9JX7WUou7LRo0YOx78LqOI/edit#heading=h.wsahg5e01t

 Description   

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.
  • Put items 1-5 together with XSEDE identity management for Science Gateways (https://software.xsede.org/display/SDIACT-245) to allow end users to transfer files directly to/from their own systems and XSEDE systems.


 Comments   

There are comments for XCI-3 that can be viewed with XSEDE authentication.