REVIEW-1: SDIACT-139 XWFS Deployment Release 2 - Joint SD&I Test and Operations Readiness Review

This review verifies the test readiness for "SDIACT -139 XWFS Deployment Release 2" and will be conducted jointly with SD&I and Operations. The XSEDE-Wide File System (XWFS) is a wide-area file system based on IBM's General Parallel File System (GPFS) technology. This activity is a maintenance release with a number of performance improvements. XSEDE Data Operations has already deployed the improvements and done extensive performance testing and so the purpose of this testing effort will be to run some independent testing of its XWFS's basic functionality for users.

• (Laura) A note should be added to the user guide indicating that data is replicated but not backed up
• (Laura) Test directories were missing – FIXED
• (Bryon) Test 3 in test plan needs to be updated to clarify Stampede as the target resource only.

• Software (use the latest revision below)
  • n/a (already deployed by Data Operations)
• Documentation
  • Introduction
    • XWFS User Guide
  • Design/Security overview
    • Security and General Design Description
  • Installation guide
    • n/a (no installation needed)
  • Deployment Plan
    • n/a (no deployment or changes needed in user doc, monitoring, etc.)
  • User guide
    • XWFS User Guide
  • Defect, issue, and risk reporting
    • See test plan below
  • Acceptance test plan
    • Test Plan
  • Testing resources
    • Stampede (Laura)
    • Gordon (Bryon)

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.