Build, Test and Certification of Grid and distributed software Community Group

1. Build, Test and Certification of Grid and distributed software Community Group Current practices and short term plans in Building, Testing and Certifying Grid software Marc-Elian Bégin ETICS Project CERN

2. Content • Agenda • Charter and Group definition • State-of-the-art in Build, Test and Certification 2

3. Agenda • Title: Current practices and short term plans in build, testing and certifying Grid software • Introduction • VDT/Condor (Becky Gietzel – UoW) • Globus (Charles Bacon – University of Chicago) • gLite (Laurence Field – CERN) • Discussion 3

4. Presentation topics Here are the topics proposed to the presenters: • Challenges in building and testing complex Grid software • Overview of current release procedure, focusing on how current Grid software is being built and tested • Does automation play a role in current build and test procedures? If yes, what? • If we had more time and effort to invest, where should we invest it? • Is there anything our community could do to help improving participants build and test system and procedures? 4

5. Charter definition • Focus/Purpose • “provide a platform for exchange and gather best practices on the topic of build, test and certification of Grid software” • Co-chairs: • Peter Couvares: University of Wisconsin-Madison, Condor/NMI • Marc-Elian Bégin: CERN, ETICS Project • Looking for a Co-chair from Industry 5

6. Roadmap 6

7. Milestones This needs to be updated/reviewed!! 7

8. Scope • Focused on current practices and short term plans • Discuss latest tools and techniques • This group is not there to mandate how Grid middleware and application software should be built, tested and certified • We hope that through its group member, the group will both represent academia and industry 8

9. Deliverable • Final output of the group will be a single document: • Best practices in building, testing and certifying Grid middleware and Grid application software 9

10. Exit Strategy • The mission of this group is to report on current knowledge in the field of build, test and certification for Grid software • Once the document is released and accepted, the goal of this group will have being reached • At that point, the group will either be dissolved or a new charter will have to be defined 10

11. State-of-the-art • Different efforts are taking place regarding “Build, test and certification”: • ETICS • NMI • OMII-Europe/UK 11

12. ETICS in a nutshell • ETICS stands fore-Infrastructure for Testing, Integration and Configuration of Software • Project started on January 1st, 2006 and has a duration of two years • Goal is to provide efficient automated tools for building and testing • ETICS is born from the experience of developing, integrating and testing grid and distributed software Build, test and certification of Grid software - OGF19, Chapel Hill, USA

13. The ETICS partners Build system, software configuration, service infrastructure, dissemination, EGEE, gLite, project coord. Software configuration, service infrastructure, dissemination The Condor batch system, distributed testing tools, service infrastructure, NMI Web portals and tools, quality process, dissemination, DILIGENT Test methods and metrics, unit testing tools, EBIT Build, test and certification of Grid software - OGF19, Chapel Hill, USA

14. Web Application Web Service Service Architecture Via browser Build/Test Artefacts Report DB Project DB NMI Execution Engine Clients NMI Client Wrapper WNs ETICS Infrastructure Build, test and certification of Grid software - OGF19, Chapel Hill, USA

15. Features of the ETICS Service • Out-of-the-box automatic build/test system • Multiplatform support for development and testing • Powerful and flexible automatic dependency management (internal and external dependencies) • Trigger coding convention checks, unit test, documentation tools and collect and publish the results • Possible to build everything from source or use pre-built binary packages • Designed to support several Version Control Systems • Possible to register artefacts on the repository • Publishes run-time configuration information such as environment variables, runtime dependencies, etc … • Produce different package formats (rpms, tar, msi, debs) • Produces rich build and test reports Build, test and certification of Grid software - OGF19, Chapel Hill, USA

16. Reports Build, test and certification of Grid software - OGF19, Chapel Hill, USA

17. 2006 OpenGridForum NMI execution engine • NMI is an execution engine internally used by ETICS to manage remote build and test jobs on different platforms • NMI is a layer built on the top of Condor • Condor is a middleware distribution that “provides mechanisms and policies supporting High Throughput Computing (HTC) on large collections of distributed computing resources” • Both NMI and Condor are developed and supported by our partner, the University of Wisconsin in Madison, USA

18. 2006 OpenGridForum NMI Web interface

19. OMII-UK Mission… OMII-UK aims to provide software and support to enable a sustained future for the UK e-Science community and its international collaborators • Promote the use of good-quality open-source software • Reduce the risk of moving to new e-infrastructure world • Recognise distinct user communities: by domain and function

20. Need A Support Infrastructure… • Collaborative Open-Source Software • Developer focussed: Sourceforge, NeSCForge • Community Repository (http://www.omii.ac.uk) • Software being used by the community • Contributed software from community • May have variable quality (e.g. Freshmeat) • May claim standards compliance • Portability and dependencies key for Grid deployment

21. Metrics to aid software selection • Portability: • Build on different platforms • Deploy and run on dynamically deployed infrastructure • Standards Compliance: WSDL, XML, … • Jobs: OGSA-BES, JSDL, HPCP • Accounting: RUS, UR • Data Access: WS-DAI, WS-DAIX, WS-DAIR • Collaboration with OMII-Europe, ETICS & NMI