Quality Assurance Working Group Doru Marcusiu, NCSA QA Working Group Lead TeraGrid Annual Review April, 2009

The Motivation Projects such as LEAD pioneering new and unanticipated usage modes of service interfaces, such as GRAM and GridFTP, have led to new user requirements and increased complexity of service failure modes, resulting in increased difficulty in problem resolution of service failures. 2

The Response Formation of a team comprised of RP system administrators, Globus software developers, LEAD gateway project staff, and science gateway area lead –Weekly review of LEAD science gateway experiences using grid service interfaces –Discussion of science gateway usage mode, users expectations, and service limitations –Identification of software enhancements, suggestions for alternate usage modes, and documentation of problems –Recommendation for persistent, focused effort to improve service availability and reliability 3

QA Working Group The goal of this working group is 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

QA-wg Status Formal proposal to establish a new working group presented to TG Forum late 3Q08 –Identified working group lead –Identified members comprised of RP site technical staff –Developed group charter and mission Availability Improvements –Evaluating INCA tests for validity/accuracy and identifying most commonly reported errors –Started translation of INCA errors to more meaningful explanations –Started improving problem resolution procedures for detected errors 5

QA-wg Status Reliability Improvements –Started evaluating existing Globus software tests to include as part of the TeraGrid software deployment process –Started discussion about improving software reliability by additional software testing using tests that represent end user and science gateway work flows 6