REVIEW-8: SDIACT-117 Improve Resource Description Information Management - Joint SD&I Test and Operations Readiness Review

The Resource Description Repository (RDR) is the authoritative information repository for SP resources critical to the function of XSEDE central services. This activity redesigns the RDR around the Rails framework, used in other areas of XSEDE. RDR continues to use a web interface to administer static resource information so that documentation coordinators can continue to manage resources in a format that is easy and familiar.

• (Shava) Tried out interface and reported being able to add duplicate admins – Developers fixed by adding a "The RDR Admin already exists" error message.
• (Shava) Test missing for "Information Services data cache" – Developer clarified would be tested during SDIACT-178 testing
• (Shava) Need Inca tests? Developer added into deployment plan.

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

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

Software (use the latest revision below)

• N/A, already a deployed service at https://dirsdev.psc.edu/rdr_ui/

Documentation

• Introduction
  • User Guide (See Introduction)
• Design/Security overview
  • Security and General Design Description
• Installation guide
  • N/A
• Deployment Plan
  • SDIACT-117 Deployment Plan
• User guide
  • User Guide
• Defect, issue, and risk reporting
  • See SDIACT-117 test plan below
• Acceptance test plan
  • Test Plan
  • Shava (Safari, Tests 1, 5)
  • Susan (Google Chrome, Tests 2-4)
  • Tabitha (Firefox, Test 2-4)
  • Dana Brunson (Test 2-4)
• Testing resources
  • https://dirsdev.psc.edu/rdr_ui/

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.