Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC1 Task 3.5 Test and...

Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC

1

Task 3.5 Test and Integration(http://ific.uv.es/grid/CROSSGRID-IFIC/)

Santiago González de la HozSantiago González de la HozInstituto de FIsica Corpuscular

(IFICIFIC)Consejo Superior de Investigaciones Científicas (CSICCSIC)

Spain


2

Summary

Goals Partners of this task and Integration Team Dependencies between this task and other

WP’s or Grid projects Infrastructure Tasks software How do we plan to organise the process of

testing wp3 tools? Time schedule Conclusions


3

Goals

To deliver a release version of WP3 before each prototype

Test all tools and services of WP3Integration and validation phase

which it will require significant effort from all of the tasks


4

Partners and Integration Team

PSNC, Poznan

CYFRONET, Cracow

UAB, Barcelona

CSIC, Valencia, Santander & RedIris


5

Partners and Integration Team

To reach the goals we need an Integration and Validation team

It is formed by people from each task of this WP and by people from each partner of this task

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


6

Dependencies

WP4 (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.

WP1 (CrossGrid Application Development) and WP2 (Grid Application Programming Environment): All tools and services of WP3 will be used by the applications

DATAGRID 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.


7

Infrastructure

We need a CVS repository, Package Repository and Support tools, in order to deliver a release version of WP3.

CVS RepositoryCVS RepositoryFor WP3 has been created in PSNC

(tulip.man.poznan.pl) WP3 central serverThe CrossGrid central server (not decided

where it will be located yet) will include all internal releases and sources of Wp’s central servers


8

Infrastructure

Package RepositoryPackage RepositoryDistribution of the WP3 softwareSource and binary RPM’s (The release version in

Datagrid project are RPM files) (http://datagrid.in2p3.fr/datagrid/testbed1/repositories/pkg-repository.html)

Acces via HTTP

Support ToolsSupport ToolsDocumentation (User Guide, Installation Guide, ...)Contac list Bug/incident tracking system (Datagrid uses

Bugzilla)


9

Test and Integration Process One idea is follow the Datagrid integration schedule

(http://marianne.in2p3.fr/datagrid/documentation) : Task3.5 Responsibilities

Task3.5 will provide a central, reliable, publicly accessible, backed-up CVS server (Just done by PSNC)

Task3.5 will also provide a central HTTP repository for the packaged source binary distributions of the WP3 software (???)

Task3.5 will also provide a central website from which support information can be obtained. (We have a WP3’s web page http://tulip.man.poznan.pl:8080)

Software tasks responsibilities The deliverables from each of the software tasks is expected in Month 10

(Task 3.5 Month 10 - 36) The software tasks must provide the detailed specifications for any public

package they provide or require. If the task software requires a specific operating system, architecture,

compiler, etc., the task must provide this information


10

Test and Integration Process Integration team responsibilities

Define package names to establish “standard” versioning rules among packages to be deployed with the Crossgrid software.

Prepare detailed schedule for when the Crossgrid sites will be expected to install the WP3 software.

Define the “reference platform (operating system, kernel, packages)”. (Datagrid project support the software on Intel-based Linux platforms).

The Integration team will begin to provide support to site administrators and to users when the WP3 software has first released.

For bugs in the WP3 software, the user should submit a bug report. The bug-report will assigned to a member of the Integration team (http://marianne.in2p3.fr/datagrid/bugzilla/) General proposition for the whole project

The integration team will provide documentation, training, and direct support for system administrators who are installing the WP3 software (http://marianne.in2p3.fr/datagrid/documentation/) General proposition for the whole project.


11

Test and Integration Process Intensive Integration

The WP3 software should be installed from the CVS server. To 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???).

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 WP3 software together, test it and deliver it.

The integration team will continuously build, deploy, and test the WP3 software until a beta-release of sufficient quality is obtained.

The 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 ??) .


12

Time Schedule

Preparation of schedule assuming first milestone is at month 12 (My point of view): Month 3:

Definition of the software requirements (tools and services) for each task in WP3.

Definition of the reference platform. CVS central Crossgrid and WP servers available. HTTP servers available.

Month 6: Co-ordination established with the other WP’s and Grid projects. First 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.


13

Time Schedule

Month 10: Collection of information from software tasks by the

Integration Team. Software tasks should begin releasing beta-version of code to

the Integration Team. Bug-reporting system in place. Reference platform install in ???? To initial tests and

integration. Month 12-15:

First prototype is delivered. Website is populated with support names and contacts. The integration team will provide documentation, training,

and direct supporting for system administrators who are installing the WP3 software.


14

Conclusions

How 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. 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.in2p3.fr/distributions/rpmlist/<names>)


15

Conclusions

Who and how should test the tools in WP3?Who: The Integration Team for the WP3 (Same

in DataGrid project). 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 WP3. DataGrid 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, IFIC1 Task 3.5 Test and...

Documents

Transcript of Crossgrid kick-off meeting, Cracow, March 2002 Santiago González de la Hoz, IFIC1 Task 3.5 Test and...