SPI Software Process Infrastructure http spi cern ch

SPI Software Process & Infrastructure http: //spi. cern. ch EGEE France - 11 June 2004 Yannick Patois yannick. patois@cern. ch Y. Patois SPI - Software Process & Infrastructure

SPI Services Overview General Services CVS service Collaborative Facilities External Software Web Portal Task Management Mailing Lists Software Development Coding Quality Assurance Deployment and Installation Development Analysis and Design Release Testing Specifications Build systems Documentation Provide General Services needed by each project • CVS repository, Web Site, Software Library • Mailing Lists, Bug Reports, Task Management, Collaborative Facilities Provide solutions specific to the Software Development phases • Tools, Templates, Policies, Support, Documentation, Examples Y. Patois SPI - Software Process & Infrastructure 2

SPI Project Guidelines • Have different and separated services - Simple solutions, easy to learn, commonly needed services - Leave any process for later • • Work with the users Develop as little as possible Establish simple deliverables Everything is done starting from existing infrastructure - LCG and LCG projects (Pool, Seal, etc) LHC experiments IT division Big projects (G 4, Root, etc) • We did not start from tools for requirements, design, etc. • We started from development-related work - repository, releases, testing, bug report, etc The rest of the talk describes SPI services Y. Patois SPI - Software Process & Infrastructure 3

SPI Services (April 2004) • External Software • Savannah Project Portal • Code Documentation (doxygen, lxr, viewcvs) • Testing Frameworks • Development of LCG policies, templates • QA checklists and reports • Software Distribution • LCG Software Configuration Y. Patois • CVS server and AFS management for LCG App. Area • Automatic Nightly Build (Nicos) • Software Librarian, builds and releases (new, was Scram support) • Documentation and LCG Workbook SPI - Software Process & Infrastructure 4

SPI Web Site - http: //spi. cern. ch Y. Patois SPI - Software Process & Infrastructure 5

SPI External Software Service • • • We install software needed by projects. Open Source and Public Domain software (libraries and tools) like: • Compilers (icc, ecc) • HEP made packages • Scientific libraries (GSL) • General tools (python) • Test tools (cppunit, qmtest) • Database software (mysql, mysql++) • Documentation generators (lxr, doxygen) • XML parsers (Xerces. C) There are currently 50 different packages, plus others under evaluation. For more than 300 installations Y. Patois The platforms, are those needed by the users • Linux Red. Hat 7. 3 and compilers - gcc 3. 2 and 3. 2. 3 (rh 73_gcc 32) - icc 7. 1 (rh 73_icc 71) - ecc 7. 1 (rh 73_ecc 71) • Windows - Visual Studio. NET 7. 1: (win 32_vc 7). • Mac OSX (osx 103_gcc 33) • Platforms always been reviewed • We also provide configuration and installation area • A unique AFS location • Standard structure package_name/version/ platform/package_ content SPI - Software Process & Infrastructure 6

External Software – http: //spi. cern. ch/extsoft Y. Patois SPI - Software Process & Infrastructure 7

SPI Savannah Portal Service • • Functionality: • Bug tracking • Task management • Mailing lists, news, faqs • Access to CVS repository • Download area, etc The Web portal for software projects Customized from GNU (Source. Forge as origin) Totally web based Single entry point to all projects Uniform access to project information Set up common web infrastructure for a project without coding Y. Patois • What SPI changed • installation from GNU, general bug fixing and improvements • integration with AFS authentication • Integration with standard services already available • What SPI does • administration (project approval) • maintenance (submitted bugs) • development (support requests) • Status • >90 hosted projects • >650 registered users SPI - Software Process & Infrastructure 8

Savannah Service – http: //savannah. cern. ch Y. Patois SPI - Software Process & Infrastructure 9

SPI Testing Services • Software testing should be an integral part of the software development • The goal was to provide something that can be run automatically as often as needed (releases, development, etc) Automated testing SPI provides • Test frameworks • Cpp. Unit, Oval • Qmtest • Test support • Test policies • Test doc Software testing Acceptance test LHC experiments System test Sw-testing team Integration test Unit test • Different platforms/compilers Y. Patois SPI - Software Process & Infrastructure Software developer Use in Exp. Examples System Tests Integration Tests Work Package Test 10

Testing Support – http: //spi. cern. ch/testing Y. Patois SPI - Software Process & Infrastructure 11

Quality Assurance Service - http: //spi. cern. ch/qa • The main goal of QA activity help sw projects • assess and improve the quality of the software • provide tools to collect useful metrics/statistics which help to asses quality; • generate reports; • verify if project setup is correct with policies. • QA Tools and Focus • Automatic reports • Development/integration of automatic tools Y. Patois SPI - Software Process & Infrastructure 12

Quality Assurance Activities QA Checklist on each Release • Build the release • Run automatic tests • Statistics • • Test Inventory Documentation/Examples Inventory Savannah Statistics Code Inventory Rule Checker , Logiscope Automatic reports • • Generated at every release • Soon be generated by anybody from the web Published on the SPI web site LCG Policies • Configuration of a build system • CVS directory structure • QA Reports Well-defined, transparent, open • clear rules and checklist of assessed items • anybody at anytime may see statistics • create reports themselves • anybody may contribute Y. Patois • Evaluation and usage of external tools • • • Rule Checker Logiscope, Test coverage SLOC, Valgrind, ignominy SPI - Software Process & Infrastructure 13

QA Reports Y. Patois SPI - Software Process & Infrastructure 14

SPI Software Distribution Service • Simple solution to use • local installations (external sites, laptops, . . . ) • using simplest approach • python downloader + tar format • replicate the central AFS tree (in a optimized way) • package dependency from SCRAM • . . . until a complete, long-term solution available • Looking into pacman as a suitable solution • SPI will adopt what Grid Deployment decides to provide Y. Patois • Simple tool to install • successful for users: - POOL @ Karlsruhe - BNL nightly builds, CMS - developers at home, etc • very easy to use and reliable • Different use-cases should have different solutions • Our tool is adequate as a temporary solution for LCG Application Area Distribution • but long-term solutions must be investigated: - pacman, LCFGng. . SPI - Software Process & Infrastructure 15

Software Distribution – http: //spi. cern. ch/lcgsoft Y. Patois SPI - Software Process & Infrastructure 16

Summary • The set of services is working and fully available • • • Savannah Project Portal Software Testing External Software Service Quality Assurance and Policies Software Distribution …and many more • We have followed a simple strategy • • Work with the users Ask their help Develop as little as possible in order to have little maintenance Provide simple and modular solutions • We have commitment to provide a sustainable service • • Most people moved on to new projects, as it was planned The services are used by LCG projects, and many outside LCG (LHC experiments, EGEE JRA 1, IT department, etc. ) • The services are generic and to some extend customizable by SPI according to EGEE needs Y. Patois SPI - Software Process & Infrastructure 17