70 likes | 217 Views
TeraGrid QA/INCA Turnover. Jeff Koerner Q4 2010 meeting December 8, 2010. QA/INCA. Quality Assurance Staffing (QA): 2.96 FTEs By site: .085 ANL .25 IU .125 LONI .25 NCSA .25 NICS .50 PSC .25 Purdue .75 SDSC (.25 to lead group and .50 for member participation) .50 TACC.
E N D
TeraGrid QA/INCA Turnover Jeff Koerner Q4 2010 meeting December 8, 2010
QA/INCA • Quality Assurance • Staffing (QA): 2.96 FTEs • By site: • .085 ANL • .25 IU • .125 LONI • .25 NCSA • .25 NICS • .50 PSC • .25 Purdue • .75 SDSC (.25 to lead group and .50 for member participation) • .50 TACC
QA Cont. • By people: 2.16 FTEs* • .15 (Kate Ericson – Co-lead) • .05 (Shava Smallen – Co-lead) • .085 ANL (Joe Insley) • .25 IU (Mike Lowe) • .125 LONI (Alex Pacheco) • .25 NICS (Daniel Lucio) • .50 PSC (Derek Simmel and Rich Raymond) • .25 Purdue (Fengping Hu) • .25 SDSC (Kenneth Yoshimoto) • .25 TACC (David Carver) • * .80 missing at NCSA/SDSC/TACC which have staff shortages.
QA Cont. • Services: The QA group uses both Inca and Process Accounting services. • INCA • A monitoring tool for testing user-level functionality and performance. Currently used by the TeraGrid Operations and QA groups to assess reliability of CTSS. • Staffing: .7 FTE (SDSC RP & GIG) • Paul Hoover (.50) • Shava Smallen (.05) • Kate Ericson (.15) • Process Accounting • Scripts used to summarize process accounting data collected on TeraGrid login nodes. Used to measure usage of tools in order to prioritize QA debugging efforts.
QA/INCA Hardware • Hardware: • sapa.sdsc.edu (PowerEdge 2850) – hosts Inca server components • Intel(r) Xeon(tm) Processor at 3.4GHz/2MB Cache, 800MHz • Memory 4GB DDR2 400MHz (4X1GB), Single Ranked DIMMs Riser Card Riser • PCI-E Support Primary Hard Drive 73GB 15K RPM Ultra 320 • SCSI Hard Drive 2nd Hard Drive 73GB 15K RPM Ultra 320 SCSI Hard Drive • Software: Open source software only (i.e., no third party service agreements)
Transition Plan • Transition: • In order to transition the Inca deployment over to XD, the current Inca team will document the current process of pulling software registration’s from TeraGrid’s IIS server and how to translate that to Inca monitoring tests. To transfer the Inca deployment, the following steps will be needed: • Copy Inca deployment directory and associated cron scripts over to XD machine • Install Postgres on XD machine and copy over sapa.sdsc.edu’s Postgres database to XD machine. • New Inca admin should install incat (Inca administrative GUI) on their machine • Copy over Inca reporter repository to new XD web space
Transition Cont. • Transfer ownership of inca accounts on all machines to XD team. • Redirect or add new DNS entry for inca.teragrid.org to point to new XD machine • Process Accounting • Hardware: Runs on TG login nodes • Software: In house scripts • Transition: Documentation and summarization scripts will be transferred over to new XD team.