Task 3 5 Test and Integration http ific

Task 3. 5 Test and Integration (http: //ific. uv. es/grid/CROSSGRID-IFIC/) Santiago González de la Hoz Instituto de FIsica Corpuscular (IFIC) IFIC Consejo Superior de Investigaciones Científicas (CSIC) CSIC Spain Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC 1

Summary 3 Goals 3 Partners of this task and Integration Team 3 Dependencies between this task and other WP’s or Grid projects 3 Infrastructure Tasks software 3 How do we plan to organise the process of testing wp 3 tools? 3 Time schedule Crossgrid kick-off meeting, 3 Conclusions Cracow, March 2002 Santiago González de la Hoz, IFIC 2

Goals 3 To deliver a release version of WP 3 before each prototype 3 Test all tools and services of WP 3 3 Integration and validation phase which it will require significant effort from all of the tasks Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC 3

Partners and Integration Team 3 PSNC, Poznan 3 CYFRONET, Cracow 3 UAB, Barcelona 3 CSIC, Valencia, Santander & Red. Iris Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC 4

Partners and Integration Team 3 To reach the goals we need an Integration and Validation team 3 It is formed by people from each task of this WP and by people from each partner of this task Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC 3 Integration team: ÞLukasz Dutka (Cyfronet) task 3. 3 & 3. 4 ÞPawel Wolniewicz (PSNC) task 3. 1 ÞMiquel A. Senar (UAB) task 3. 2 ÞSantiago González (CSIC) task 3. 5 5

Dependencies 3 WP 4 (International Testbed Organisation): This task is very strongly correlated with the prototypes released in WP 4 because the testbed will provide the framework to run the applications made in the different WP’s. 3 WP 1 (Cross. Grid Application Development) and WP 2 (Grid Application Programming Environment): All tools and services of WP 3 will be used by the applications 3 DATAGRID project: The WP 6 (Testbed & Demonstrators) and more concretely with the Integration Team because they are doing the tests and integration of the Data. Grid middleware at the moment. Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC 6

Infrastructure 3 We need a CVS repository, Package Repository and Support tools, in order to deliver a release version of WP 3. 3 CVS Repository ÞFor WP 3 has been created in PSNC (tulip. man. poznan. pl) WP 3 central server ÞThe Cross. Grid central server (not decided where it will be located yet) will include all internal releases and sources of Wp’s central servers Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC 7

Infrastructure 3 Package Repository ÞDistribution of the WP 3 software ÞSource and binary RPM’s (The release version in Datagrid project are RPM files) (http: //datagrid. in 2 p 3. fr/datagrid/testbed 1/repositories/pkg-repository. html) ÞAcces via HTTP 3 Support Tools ÞDocumentation (User Guide, Installation Guide, . . . ) ÞContac list ÞBug/incident tracking system (Datagrid uses Bugzilla) Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC 8

Test and Integration Process 3 One idea is follow the Datagrid integration schedule (http: //marianne. in 2 p 3. fr/datagrid/documentation) : Þ Task 3. 5 Responsibilities V Task 3. 5 will provide a central, reliable, publicly accessible, backed-up CVS server (Just done by PSNC) V Task 3. 5 will also provide a central HTTP repository for the packaged source binary distributions of the WP 3 software (? ? ? ) V Task 3. 5 will also provide a central website from which support information can be obtained. (We have a WP 3’s web page http: //tulip. man. poznan. pl: 8080) Þ Software tasks responsibilities V The deliverables from each of the software tasks is expected in Month 10 (Task 3. 5 Month 10 - 36) V The software tasks must provide the detailed specifications for any public package they provide or require. V Ifmeeting, the task software requires a specific operating system, architecture, Crossgrid kick-off compiler, etc. , the task must provide this information Cracow, March 2002 Santiago González de la Hoz, IFIC 9

Test and Integration Process Þ Integration team responsibilities V Define package names to establish “standard” versioning rules among packages to be deployed with the Crossgrid software. V Prepare detailed schedule for when the Crossgrid sites will be expected to install the WP 3 software. V Define the “reference platform (operating system, kernel, packages)”. (Datagrid project support the software on Intel-based Linux platforms). V The Integration team will begin to provide support to site administrators and to users when the WP 3 software has first released. V For bugs in the WP 3 software, the user should submit a bug report. The bug-report will assigned to a member of the Integration team (http: //marianne. in 2 p 3. fr/datagrid/bugzilla/) General proposition for the whole project V The integration team will provide documentation, training, and direct support for system administrators who are installing the WP 3 software (http: //marianne. in 2 p 3. fr/datagrid/documentation/) General Crossgrid kick-offproposition meeting, for the whole project. Cracow, March 2002 Santiago González de la Hoz, IFIC 10

Test and Integration Process Þ Intensive Integration V The WP 3 software should be installed from the CVS server. V To produce the first functioning beta-release of the WP 3 software, all of the members of the integration team should be physically in the same place and having enough resources to build a small “grid”. (Datagrid project have two sites at CERN, one dedicated to develop and the other to production, Our where? ? ? ). V Each of the partners should have in place a minimum set of machines with the basic software packages (Globus, datagrid, . . . ) on top of which they’ll develop their own tools (This would be a local testbed, month 6 in the project Annex). Crossgrid will be a real distributed environment in opposite to Datagrid. But we need a TESTBED site (local cluster) to do the test and the integration, in order to put all WP 3 software together, test it and deliver it. V The integration team will continuously build, deploy, and test the WP 3 software until a beta-release of sufficient quality is obtained. V The Globus version 2. 0 (alpha-15, beta-21) have been installed on two Crossgrid kick-offnodes meeting, at CERN and tested (Will we use the same version as them ? ? ). Cracow, March 2002 Santiago González de la Hoz, IFIC 11

Time Schedule 3 Preparation of schedule assuming first milestone is at month 12 (My point of view): Þ Month 3: V Definition of the software requirements (tools and services) for each task in WP 3. V Definition of the reference platform. V CVS central Crossgrid and WP servers available. V HTTP servers available. Þ Month 6: V Co-ordination established with the other WP’s and Grid projects. V First local (in each site) testbed should be in place with the Datagrid’s tools installed, where each task develops and test their and services. Crossgrid kick-offtools meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC 12

Time Schedule Þ Month 10: V Collection of information from software tasks by the Integration Team. V Software tasks should begin releasing beta-version of code to the Integration Team. V Bug-reporting system in place. V Reference platform install in ? ? To initial tests and integration. Þ Month 12 -15: V First prototype is delivered. V Website is populated with support names and contacts. V The integration team will provide documentation, training, and direct supporting for system administrators who are installing the WP 3 software. Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC 13

Conclusions 3 How the release version should be prepared? ÞSource code for the Datagrid can be obtained from a Central CVS Repository hosted by CC-IN 2 P 3. This repository is intended primarily for developers. ÞAll software in Datagrid project is packaged as source and binary RPM files. V All of the packages are available directly through a web interface either via direct browsing or via a formatted list. (wget -r -nd http: //datagrid. in 2 p 3. fr/distributions/rpmlist/<names>) Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC 14

Conclusions 3 Who and how should test the tools in WP 3? ÞWho: The Integration Team for the WP 3 (Same in Data. Grid project). V Each task must test its software before releasing code to Integration Team ÞHow: We need a site to do the test and integration to deliver a release version of WP 3. V Data. Grid project is centralising all the software at CERN and the Integration Team is ready to spend approximately three weeks at CERN during the intensive integration phase. Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC 15