DATAGRID Testbed release 0 Organization and working model F.Etienne, A.Ghiselli CNRS/IN2P3 – Marseille, INFN-CNAF Bologna DATAGRID Conference, 7-9 March 2001 Amsterdam

27-9 March 2001DATAgrid Conference - Amsterdam Content Testbed 0 release goals Working model Organisation Conclusion

37-9 March 2001DATAgrid Conference - Amsterdam Goals of Testbed 0 release Grid basic services deployment at european level, based on Globus toolkit; main coordination issues are: – Information services –Resource access:Certification, Security and policies management –Installation kit and documentation Network layout monitoring tools First Grid Middleware tests First Grid Applications tests

47-9 March 2001DATAgrid Conference - Amsterdam Working model Goal: Testbed has to provide the grid-layout for test activity of each WP and organize the software release validation process. Working model defines the validation process of each software package released by the DATAGRID Work Packages.

57-9 March 2001DATAgrid Conference - Amsterdam 1.WP test activity: Testbed WP will provide the basic layout for test activity of each DATAGRID WPs. 2. WP Release: a team of people from WPs, applications, testbed and network will organize the test environment for this release, do the tests, provide feedback to the WP and validate the release for the next test phase. 3.Testbed Release : the previous software release will be integrated to the last official testbed release. This new release will be tested in a larger environment in order to be validated for the next final testing phase. 4.Official Testbed Release:a new team including also users will organize a quasi-production environment in order to certificate this release as new official testbed release. Working Model

67-9 March 2001DATAgrid Conference - Amsterdam MIDDLEWARE AND APPLICATIONS Specific WP test activity WPx team I WP Release + appl. test Testbed + WPx + appl. Team II Testbed Release :integration into testbed release and test in larger environment Testbed + WPs and appl. Team III Official Testbed Release test in quasi-production environment + Users Team Official Testbed RELEASE NETWORKNETWORK TESTBEDTESTBED Development Version Production Version

77-9 March 2001DATAgrid Conference - Amsterdam Testbed organization Permanent Group, to coordinate and plan the test activity: –Partner representatives –Technical committee –Site contacts –Testbed support Release Teams: one team for each Release validation phase

87-9 March 2001DATAgrid Conference - Amsterdam Permanent Group –Partners representatives To coordinate testbed activity and evolution To define resource access policies in collaboration with the owner of the resources To approve test plans

97-9 March 2001DATAgrid Conference - Amsterdam Permanent Group cont. Technical Committee: to coordinate grid basic services and define test plans to be approved by the partners. –Requirements group (WPs Middleware, applications) To define the testbed requirements for WP tests (resources, services..) and for the validation of WP software releases –Information service group coordinator The IS group has to plan and support the IS service configuration for the Testbed. –Certification Authority coordinator To solve the multiple CA certificate issue for DATAgrid with the CA managers. –Security group coordinator To find the best mechanism to implement the access policies using the Globus Security Infrastructure To provide the architectural model for security to ATF –Network layout and services : oneWP7 representative – technical input from WP7 and WP6 requirements output to WP7

107-9 March 2001DATAgrid Conference - Amsterdam Permanent Group cont. –Site Contacts :(a coordinator per organization) To manage grid site-resources To implement the access policies To install software packages decided by the technical committee and by the release team To provide local support for the official releases

117-9 March 2001DATAgrid Conference - Amsterdam Permanent Group cont. –Testbed Support To organize and provide support and documentation on the official testbed software to site contacts (and in collaboration with them) and users. Need of direct channel with the Globus Team (testbed support & IS support)

127-9 March 2001DATAgrid Conference - Amsterdam Release Teams Temporary groups set up for each specific WP release to certificate the different release validation phases. For each release the membership has to be set up. Clarifications: –the software code is owned by the WPs. –Testbed WP organizes the ‘release certification’ and distribute the installation kit of the integrated WP releases also called “Testbed official release”.

137-9 March 2001DATAgrid Conference - Amsterdam Partners ZIB (Berlin) PPARC RAL CNRS IN2P3 7 sites CZECH Republic 2 sites CERNINFN 9 sites Spain 5 sites ESA- Esrin 4 sites LIP (Lisboa) Russia 4 sites WP6 Coordinator: Francois Etienne Deputy : Antonia Ghiselli S.Jarp A.Ghiselli L.Gaido D. Newbold A.Sansum R.J.Wilson G.Brugnoni F.Etienne A.Merzky F.Schintke J.Gomes M.Ruda H.Sverenyak Sweden Lund O.Smirnova B.A.Llyin

147-9 March 2001DATAgrid Conference - Amsterdam Sites map Dubna Moscow RAL Lund Lisboa Santander Madrid Valencia Barcelona Paris Berlin Lyon Grenoble Marseille Brno Prague Torino Milano BO-CNAF PD-LNL Pisa Roma Catania ESRIN CERN HEP sites ESA sites IPSL Estec KNMI

157-9 March 2001DATAgrid Conference - Amsterdam Testbed progressively growing from quantum to production Grid

167-9 March 2001DATAgrid Conference - Amsterdam Conclusions Actions of this meeting: –Testbed organization in place –Define CA/Security rules –Define a GIS topology and deployment coordination –Network monitoring tools proposal –Collect test requests from site contacts, and eventually from Middleware WPs and Applications –Testbed0 resource list –---  test plan