REVIEW-16: SDIACT-27 Enable data sharing using Globus Sharing - Joint SD&I Test and Operations Readiness Review

This activity provides SP administrator documentation on how to configure a GridFTP endpoint for Globus Sharing. Globus sharing will enable XSEDE users who have an account on an XSEDE endpoint (xsede#foo) to share files easily with other XSEDE users who do not have accounts on that endpoint. No additional software packages are needed to enable Globus sharing on a SP GridFTP endpoint.

All documents looked good. No specific requests for changes was provided by the testers.

Documentation

• Introduction
  • See "About Globus sharing" in https://software.xsede.org/svn/sdi/activities/sdiact-027/trunk/Plans/endpoint-provider-doc.pdf
• Design/Security overview
  • Security and General Design Description
• SP administrator guide
  • SDIACT-27 administrator guide
• Deployment Plan
  • SDIACT-27 Deployment Plan
• User guide
  • User Guide
• Defect, issue, and risk reporting
  • See SDIACT-27 test plan below
• Acceptance test plan
  • Test Plan
• Testing resources
  • hpcdev-pub04.sdsc.edu (Peter)
  • TBD (Ed)

Package information: All software packages (e.g., server and client packages) for this CI are listed.

Documentation and Installation instructions: The deployment plan for this CI on XSEDE is clearly described as well as the installation instructions and any XSEDE specific configuration instructions.

Test environment and facilities: The test environment needed to adequately to validate this component is described. Should indicate also whether testing can be performed within a VM and if not, the reasons for it.

Assumptions: Lists any assumptions needed before testing can begin (e.g., accounts needed).

Test procedures, cases, and scenarios: Lists the tests that should be run or an associated test suite and expected performance metrics if applicable.

Defect, issue, and risk reporting: Deployment plans should include defect and issue reporting information. The testing plan could reference that same information from the deployment plan, or provide alternate information if defects and issues need to be reported differently during testing. Risks, as well as defects and iss