REVIEW-53: XCI-143 Deliver incremental IPF fixes and enhancements - Test Readiness Review

The Information Publishing Framework (IPF) is used by XSEDE Ops to publish dynamic software and services availability information. XCI-143 delivers an enhanced IPF that 1) publishes to new information servers, 2) has an improved ipf_configure_xsede script, 3) looks for module-whatis default: <yes|no> and publish it as a GLUE2 extension, 4) enables SPs to publish software/service support contact information, 5) publishes itself into information services, and 6) publishes GPU information when provided by SLURM.

• (Shava) Include "InCommon IGTF CA" in include cacerts.pem file since many SPs use certs issued by them — fixed.
• (JP) Deployment plan should be specific about the workflows each SP is expected to run - added for all SPs – need to finalize before testing is completed
• (JP, Shava) Multiple documentations improvement suggestions – fixed
• (Shava) %VER%-%REL% did not get resolved in INSTALL guide – needs to be fixed before testing is completed.

• Introduction
  • See user guide below
• Design/Security overview
  • No major changes to architecture made. See previous XCI-21 design doc.
• Installation guide
  • XCI-143 Installation Guide
• Deployment Plan
  • XCI-143 Deployment Plan
• User guide
  • Guide
• Defect, issue, and risk reporting
  • See XCI-143 test plan below
• Acceptance test plan
  • Test Plan
• Testing resources
  • hpcdev-pub04.sdsc.edu

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.