1 / 7

Start of Quality Assurance Working Group

TeraGrid Quarterly Meeting Nov. 30 - Dec. 2, 2009 San Diego, CA Quality Assurance (QA) Working Group Kate Ericson (SDSC) Shava Smallen (SDSC). Start of Quality Assurance Working Group.

marius
Download Presentation

Start of Quality Assurance Working Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TeraGrid Quarterly Meeting Nov. 30 - Dec. 2, 2009San Diego, CAQuality Assurance (QA) Working GroupKate Ericson (SDSC)Shava Smallen (SDSC)

  2. Start of Quality Assurance Working Group After focused efforts with user groups (e.g. LEAD) and NSF direction, funding was allocated towards both Quality Assurance (QA) and Common User Environment (CUE) to improve TG user experience Initial charter for QA developed late 2008. Included CUE for a short time QA led by Doru Marcusiu at NCSA, CUE led by Shawn Brown at PSC

  3. Original QA WG Vision To identify and implement ways in which TeraGrid software components/services and production deployments can be improved to reduce the number of failures requiring operator intervention that are encountered at TeraGrid resource provider sites.

  4. Original QA Goals/Milestones Initially to increase availability of CTSS services: Improve time from detected failure to notification Reviewed Inca error notification configuration and policies Created web page view of who gets notified for each CTSS test Map errors to potential problem resolution procedures Linked Inca test failures to TG knowledge base articles and added method for admins to share problem resolution information Improve description of error and map to lower level failures to reduce admin time hunting for error interpretation

  5. Original QA Goals/Milestones Later planned to increase reliability of services: Organize and identify priorities and timelines for new QA testing cycle Which services are most widely used Which services fail most often (created Inca page view to start on this) Identify existing tests to be used and/or develop new tests Started evaluating existing Inca tests Develop HPC testbed

  6. Current QA WG Status Continue effort started by the group, important to Operations and Inca efforts Most staff has been re-identified, but still need to match 2.71 FTEs of PY5 funding

  7. 2009 QA Goals Two meetings this month to discuss staff and finishing short term deliverables: reviewing existing Inca tests for need documenting possible Inca test solutions in Knowledge Base editing and advertising TG Grid admin guide Work with CUE to coordinate groups under new leadership identify staff test CUE functionality as requested (e.g. env variables.ssh config) combine their module guide with QA admin guide and distribute After TAIS awarded, build a transition plan for the rest of PY5

More Related