REVIEW-18: SDIACT-202 Incremental GSI-OpenSSH fixes and enhancements - Joint SD&I Test and Operations Readiness Review

• (Peter) Missing SLES command in install guide
  • Fixed
• (Peter) User guide has a few bad links and out of date information
  • Will most likely be removed – resolve before end of testing
• (Peter) Test plan references SVN install guide which doesn't display correctly in browsers
  • Test plan now points to development repository instructions that display correctly.
• (Shava) Test plan doesn't specify that CentOS 7 packages are available and should be tested
  • Test plan modified
• (Shava) Add more description to Test 6
  • Test plan modified
• (David) Test 5 instructions are confusing
  • Test plan modified

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

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

Software (use the latest revision below)

• http://software.xsede.org/development/gsi-openssh-server-xsede/ (version 7.1p2e-7)

Documentation

• Introduction
  • http://grid.ncsa.illinois.edu/ssh/
• Design/Security overview
  • Security and General Design Description
• Installation guide
  • SDIACT-202 Installation Guide
• Deployment Plan (Draft for Operations)
  • SDIACT-202 Deployment Plan
• User guide
  • Guide
• Defect, issue, and risk reporting
  • See SDIACT-202 test plan below
• Acceptance test plan
  • Test Plan
• Testing resources
  • SD&I - CentOS 6 - RPM install - hpcdev-pub04.sdsc.edu
  • PSC - CentOS 7 - RPM install - PSC machine
  • TACC - CentOS 6 - Targz install - stampede.tacc.xsede.org

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.