REVIEW-26: SDIACT-200 Improve data transfer performance with a central logging and transfer analysis service - Joint SD&I Test and Operations Readiness Review

This review analyzes the test readiness for a new data transfer logging and analysis infrastructure to support the diagnosis of performance issues, identification of areas for improvement and appropriate setting of user expectations based on actual transfers. The infrastructure will also support regular reporting of metrics as well as ad hoc queries to better understand usage of the data transfer infrastructure of XSEDE.

• (Shava) How can SPs verify their data is being parsed correctly?
  • Instructions will be modified to email Siva for confirmation
• (David) Change instructions to instruct users to create RSA keys
  • Developer changed install instructions
• (Choonhan) Explicitly specify globust username in script and in test plan
  • Developer modified script; will need to modify test plan before the end of testing
• (Tabitha) Resources out of date in deployment plan
  • Fixed by reviewer

• Introduction
  • https://www.xsede.org/web/staff/staff-wiki/-/wiki/Main/GridFTP%20Logging%20Upload%20Configuration (see first paragraph)
• Design/Security overview
  • Security and General Design Description
• Installation guide
  • SDIACT-200 Installation Guide
• Deployment Plan
  • SDIACT-200 Deployment Plan
• User guide
  • n/a (not intended for end users)
• Defect, issue, and risk reporting
  • See SDIACT-200 test plan below
• Acceptance test plan
  • Test Plan
• Testing resources
  • hpcdev-pub04.sdsc.edu (Choonhan)
  • TACC machine (David)
  • NICS machine (Tabitha)

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 issues, should be part of the testing report.