1. Maite Barroso – WP4 meeting @ Barcelona – 13/05/2003 - n° 1 -WP4 day @ Barcelona- Closure Maite Barroso 13/05/2003 Maite.Barroso.Lopez@cern.ch

2. Maite Barroso – WP4 meeting @ Barcelona - 13/05/2003 - n° 2 Olof vision vs reality today Did Olof’s vision become reality? NOTE: components not finished yet are marked in red.

3. Maite Barroso – WP4 meeting @ Barcelona - 13/05/2003 - n° 3 Configuration today Node profile Configuration Database Node profile Configuration Database Abra-cadabra Hocus-pocus HLDL template CDB API PAN Cache Node profile NVA API PC

4. Maite Barroso – WP4 meeting @ Barcelona - 13/05/2003 - n° 4 Monitoring today Monitoring repository Agent Repository server Repository API Transport SQL DB Alarm GUI PC Node profile Sensor Monitoring Component

5. Maite Barroso – WP4 meeting @ Barcelona - 13/05/2003 - n° 5 Fault tolerance today Fault Tolerance Rule Editor Correlation Engine Rule HLDL Node profile Monitoring API PC CDB Job scheduling Actuator FT Component ???

6. Maite Barroso – WP4 meeting @ Barcelona - 13/05/2003 - n° 6 Installation&Maintenance today PC RPM Software repository RPM Cache Node profile Component NCM SPM Component SPM rpmtpkgt??

7. Maite Barroso – WP4 meeting @ Barcelona - 13/05/2003 - n° 7 Resource mgmt today Job scheduling Scheduler Runtime Control PBS Admin API LSF RMS Component Node profile Monitoring??

8. Maite Barroso – WP4 meeting @ Barcelona - 13/05/2003 - n° 8 Summary Good progress made in all the tasks since last workshop. Very good integration, support and response to bugs. CONGRATULATIONS! Testing plans. Keep on updating them regularly Priorities for coming months: 1)Continue support of released components 2)Finish developments and LCFGng components 3)Testing (use WP4 nodes), documentation 4)Prepare integration 5)Translate configuration and components to use the new configuration and installation framework

9. Maite Barroso – WP4 meeting @ Barcelona - 13/05/2003 - n° 9 DISCUSSION: What happens to EDG software after the lifetime of EDG? u GOAL: finding a single strategy that can be deployed independently of whether related projects (EGEE, LCG) will take over EDG software or not u EDG license allows anybody to use EDG software and further develop it as long as EDG is appropriately credited. This model allows other projects to take over EDG software u There was consensus that no separate body should be put in place to continue branding EDG. u PROPOSAL: to make EDG software publicly available in well known software repositories such as sourceforge. u EDG license guarantees source code distribution and re-use, EDG design can only be protected by patenting. It is too late for this.