German Cancio/ WP4 -1 WP4 comments for the TestBed German Cancio / WP4 [email protected].

8
German Cancio/ WP4 -1 WP4 comments for the TestBed German Cancio / WP4 German.Cancio@cern. ch

Transcript of German Cancio/ WP4 -1 WP4 comments for the TestBed German Cancio / WP4 [email protected].

Page 1: German Cancio/ WP4 -1 WP4 comments for the TestBed German Cancio / WP4 German.Cancio@cern.ch.

German Cancio/ WP4 -1

WP4 comments for the TestBed

German Cancio / WP4

[email protected]

Page 2: German Cancio/ WP4 -1 WP4 comments for the TestBed German Cancio / WP4 German.Cancio@cern.ch.

Author - Title- Date - n° 2

Outline

Software packages taxonomy

Packaging software and software repositories

Certification

Miscellaneous

Page 3: German Cancio/ WP4 -1 WP4 comments for the TestBed German Cancio / WP4 German.Cancio@cern.ch.

Author - Title- Date - n° 3

Software Packages Taxonomy (I)

In the WP6 document, we see two SW package types: Middleware SW packages (WP1-5,WP7) Application SW packages

… but from WP4 we see more: Base Operating System (ie. RedHat Linux X.Y) Globus packages Software required by Applications

f.ex. ROOT, CERNLIB,Objectivity,GNU tools,…

Site specific packages (next slide)

Page 4: German Cancio/ WP4 -1 WP4 comments for the TestBed German Cancio / WP4 German.Cancio@cern.ch.

Author - Title- Date - n° 4

Software Packages Taxonomy (II)

Site specific packages: Batch systems (LSF, PBS..)

Mass storage systems (CASTOR,..)

AFS clients

Other locally required packages, like security policy enforcement tools (disabling ports,…)

Who is providing/configuring/installing all these? OS, Globus, Objectivity et al., LSF, AFS,…

Who will do the support for these?

Page 5: German Cancio/ WP4 -1 WP4 comments for the TestBed German Cancio / WP4 German.Cancio@cern.ch.

Author - Title- Date - n° 5

Software Packaging and WP4

WP4 will deliver an interim installation system in M9 (Maite’s talk).

In order to use this system, software has to be packaged accordingly.

Certainly the M/W and the applications will package their own SW.

Who will do this for all the other required SW?

In general, WP4 provides A toolset for distributing/installing packages on fabric nodes,

but not the packages themselves Guidelines on how to package SW, but does not package SW

Page 6: German Cancio/ WP4 -1 WP4 comments for the TestBed German Cancio / WP4 German.Cancio@cern.ch.

Author - Title- Date - n° 6

SW Package Repositories In order to ease the task of distributing SW packages to the TestBed sites, SW Package Repositories could be set up.

(this are not code repositories a la CVS but contain ready-to-use binaries)

Who sets them up? Who manages them? Who decides what packages /versions are available?

How many Repositories would exist? A single Repository? One per ‘Virtual Organization’? What about site specific packages? What about licensed software (like LSF, AFS, Objectivity)?

Page 7: German Cancio/ WP4 -1 WP4 comments for the TestBed German Cancio / WP4 German.Cancio@cern.ch.

Author - Title- Date - n° 7

Certification

A certification procedure has to be defined for ensuring the correct interaction between the different packages.

Who certifies the packages which are not DataGRID deliverables? Who decides which packages to certify?

Who certifies a given set of packages for being installed on the nodes of a given testbed?

This has to include site specific packages!

Is this the goal of WP6’s “integration”?

Page 8: German Cancio/ WP4 -1 WP4 comments for the TestBed German Cancio / WP4 German.Cancio@cern.ch.

Author - Title- Date - n° 8

Summary

For WP4:

The integration of 3rd-party packages is not clear. OS, App-required, Licensed, site-specific

Should a package repository be set up?

The certification model is not clear.