Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC1 Task 3.5 Test and Integration ( Santiago González de la Hoz Instituto de FIsica Corpuscular IFIC (IFIC) CSIC Consejo Superior de Investigaciones Científicas (CSIC) Spain

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

Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC3 Goals 3To deliver a release version of WP3 before each prototype 3Test all tools and services of WP3 3Integration 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, IFIC4 Partners and Integration Team 3PSNC, Poznan 3CYFRONET, Cracow 3UAB, Barcelona 3CSIC, Valencia, Santander & RedIris

Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC5 Partners and Integration Team 3To reach the goals we need an Integration and Validation team 3It is formed by people from each task of this WP and by people from each partner of this task 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

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

Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC7 Infrastructure 3We need a CVS repository, Package Repository and Support tools, in order to deliver a release version of WP3. 3CVS Repository ÞFor WP3 has been created in PSNC ( tulip.man.poznan.pl ) WP3 central server ÞThe CrossGrid 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, IFIC8 Infrastructure 3Package Repository ÞDistribution of the WP3 software ÞSource and binary RPM’s (The release version in Datagrid project are RPM files) ( ÞAcces via HTTP 3Support 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, IFIC9 Test and Integration Process 3One idea is follow the Datagrid integration schedule ( : ÞTask3.5 Responsibilities VTask3.5 will provide a central, reliable, publicly accessible, backed-up CVS server (Just done by PSNC) VTask3.5 will also provide a central HTTP repository for the packaged source binary distributions of the WP3 software (???) VTask3.5 will also provide a central website from which support information can be obtained. (We have a WP3’s web page ÞSoftware tasks responsibilities VThe deliverables from each of the software tasks is expected in Month 10 (Task 3.5 Month ) VThe software tasks must provide the detailed specifications for any public package they provide or require. VIf the task software requires a specific operating system, architecture, compiler, etc., the task must provide this information

Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC10 Test and Integration Process ÞIntegration team responsibilities VDefine package names to establish “standard” versioning rules among packages to be deployed with the Crossgrid software. VPrepare detailed schedule for when the Crossgrid sites will be expected to install the WP3 software. VDefine the “reference platform (operating system, kernel, packages)”. (Datagrid project support the software on Intel-based Linux platforms). VThe Integration team will begin to provide support to site administrators and to users when the WP3 software has first released. VFor bugs in the WP3 software, the user should submit a bug report. The bug-report will assigned to a member of the Integration team ( General proposition for the whole project VThe integration team will provide documentation, training, and direct support for system administrators who are installing the WP3 software ( General proposition for the whole project.

Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC11 Test and Integration Process ÞIntensive Integration VThe WP3 software should be installed from the CVS server. VTo produce the first functioning beta-release of the WP3 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???). VEach 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 WP3 software together, test it and deliver it. VThe integration team will continuously build, deploy, and test the WP3 software until a beta-release of sufficient quality is obtained. VThe Globus version 2.0 (alpha-15, beta-21) have been installed on two nodes at CERN and tested (Will we use the same version as them ??).

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

Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC13 Time Schedule ÞMonth 10: VCollection of information from software tasks by the Integration Team. VSoftware tasks should begin releasing beta-version of code to the Integration Team. VBug-reporting system in place. VReference platform install in ???? To initial tests and integration. ÞMonth 12-15: VFirst prototype is delivered. VWebsite is populated with support names and contacts. VThe integration team will provide documentation, training, and direct supporting for system administrators who are installing the WP3 software.

Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC14 Conclusions 3How the release version should be prepared? ÞSource code for the Datagrid can be obtained from a Central CVS Repository hosted by CC-IN2P3. This repository is intended primarily for developers. ÞAll software in Datagrid project is packaged as source and binary RPM files. VAll of the packages are available directly through a web interface either via direct browsing or via a formatted list. (wget -r -nd )

Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC15 Conclusions 3Who and how should test the tools in WP3? ÞWho: The Integration Team for the WP3 (Same in DataGrid project). VEach 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 WP3. VDataGrid 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.