Overview
The Information Publishing Framework (IPF) is used by XSEDE SPs to publish dynamic software and services availability information. XCI-677 delivers an enhanced IPF that is based on Python3 and enables filtering of SLURM jobs.
Review Summary
No issues with testing materials.
Review Output Documents (Final)
- Introduction
- See user guide below
- Design/Security overview
- No major changes to architecture made. See previous XCI-21 design doc.
- Installation guide
- Deployment Plan
- User guide
- Defect, issue, and risk reporting
- See test plan below
- Acceptance test plan
- Testing resources
- PSC test resource (Derek will setup for Galen)
Review Input Documents
- Introduction
- See user guide below
- Design/Security overview
- No major changes to architecture made. See previous XCI-21 design doc.
- Installation guide
- Deployment Plan
- User guide
- Defect, issue, and risk reporting
- See test plan below
- Acceptance test plan
- Testing resources
- PSC test resource (Derek will setup for Galen)
Review Criteria
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.
Schedule
Current Date: 2023-09-24Current Status: Closed (Test Readiness Review)
Target Date | Actual Date | Activity Milestone |
---|---|---|
2020-03-04 | Review launch date | |
2020-03-13 | Written feedback due (Reviewers) | |
2020-03-17 | 2020-06-26 | Written response date (Review Material Developers) |
2020-03-31 | 2020-06-26 | Final approval due and completion date (Reviewers) |
Review Last Updated: 2020-06-26 6:47 pm
Reviewers
If you are a reviewer, please login to sign or withdraw from this review.
Required
- Galen Arnold
VIEWED: 2020-06-03 10:21
SIGNED: 2020-03-05 15:44 - Derek Simmel
Review Material Developers
Eric Blau
Review Facilitator
Shava Smallen