Skip to content Skip to navigation

JIRA Issue

[#REVIEW-31] XCI-6 Verify integration process for a new SP resource - Test Readiness Review

[REVIEW-31] XCI-6 Verify integration process for a new SP resource - Test Readiness Review Created: 09/23/2016  Updated: 10/17/2016  Resolved: 10/17/2016

Status: Closed
Project: Technical Reviews
Component/s: None
Fix Version/s: None

Type: Test Readiness Review
Reporter: Shava Smallen Assignee: Shava Smallen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Review
is review of XCI-6 Verify integration process for a new ... Closed
Review Materials:
  • Acceptance test plan
  • Testing resources
    • Comet virtual clusters
      • Note: waiting on production environment to be ready
Review Criteria:

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.

Discussion Thread: https://www.xsede.org/web/staff/staff-message-board/-/message_boards/category/1284461
Review Summary:
  • (Lee) Why is GRAM listed as a component to test and UNICORE is not?
    • XSEDE prioritized and funded in PY4/5 a GRAM5 upgrade because at least 2 SPs and some gateways depend on it. Because XSEDE prioritized and funded UNICORE 6 delivery, we should test it also, although we have no SPs on record that are interested in operating it. So, GRAM5 and UNICORE 6 have been moved to the last things we test and are of low priority in the revised test plan document.
  • (Lee) Why test GridFTP and GSI-SSH?
    • We are looking for feedback on where our documentation and processes are confusing, unclear, or in any other way could be improved.
  • (Lee) Should we test a cloud and data resource too?
    • We are targeting the available XSEDE software and not a particular resource type.
  • (Victor) Ask tester's to review SP checklist
    • Changed Step 2 to "Review SP Checklist and follow instructions to integrate each component available to a new SP Level 1 resource".
  • (Victor) Ask tester to verify CA Certificate Installer and fetch-crl tool
    • Changed xsede-ca-certificates to "CA Certificate Installer" and added verification of fetch-crl tool
Revised Review Materials:
Public Review Link: https://software.xsede.org/jira/view/reviews/REVIEW-31
Review Facilitator: Shava Smallen
Review Material Developers: Shava Smallen, ssmallen@sdsc.edu, Test Plan author
Target Review Start Date:
Target Reviewer Feedback Due Date:
Target Written Feedback Assessment Due Date:
Target Review End Date:
Actual Review Start Date:
Actual Reviewer Feedback Received Date:
Actual Written Feedback Received Date:
Actual Review End Date:
Reviewer Feedback Friendly Reminder Date:
Reviewer Feedback Due Soon Reminder Date:
Reviewer Feedback Due Today Reminder Date:

 Description   

This is an evaluation and testing activity to analyze the current process of integrating a new resource. We will create a new test resource and run through the current steps to both introduce a new Level1 Service Provider and a new resource and document everything that is complicated, confusing, or didn’t work and how it can be improved.