REVIEW-10: SDIACT-148 Incremental UNICORE-GFFS interoperability fixes and enhancements - Test Readiness Review

UNICORE and GFFS provide job execution and data management capabilities to users and interoperate using a small interoperability package. SDIACT-148 delivers an update to the UNICORE GFFS interoperability package.

• (Galen) Add links to installers
  • Corrected links to GFFS and UNICORE installers
• (Galen) Correct steps in Test 1, Step 4
  • Corrected to refer to Steps 11-17

Materials for SDIACT-148 are linked below and have been checked into SVN at:

https://software.xsede.org/svn/sdi/activities/sdiact-148/trunk/

Software (use the latest revision below)

• http://software.xsede.org/development/UNICORE/UNICORE-7.3.0/
• http://software.xsede.org/development/genesis2/sdiact-175/test_grid/

Documentation

• Introduction
  • [https://portal.xsede.org/software/gffs]
• Design/Security overview
  • Security and General Design Description
• Installation guide
  • SDIACT-148 Service Provider Guide (See Steps 11-13)
  • SDIACT-148 Updated Genesis II Omnibus Reference Manual
• Deployment Plan
  • SDIACT-148 Deployment Plan
• User guide
  • GFFS User Guide
• Defect, issue, and risk reporting
  • See SDIACT-148 test plan below
• Acceptance test plan
  • Test Plan
• Testing resources
  • hpcdev-pub04.sdsc.edu (SP Container)

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.