1. Task Meetings
|Date (dd/mm/yyyy)||Url Indico Agenda||Title||Outcome|
|04 May||https://www.egi.eu/indico/conferenceDisplay.py?confId=469||Globus integration task force meeting||13 participants
|06 May||https://www.egi.eu/indico/conferenceDisplay.py?confId=465||UNICORE integration task force meeting||8 participants
Standard meeting with slight focus on new GOCDB service types
|18 May||https://www.egi.eu/indico/conferenceDisplay.py?confId=485||Globus integration task force meeting||at least 13 active participants
Meeting during EGCF1, Munich, dedicated to Accounting and GridSAFE
|06 June||https://www.egi.eu/indico/conferenceDisplay.py?confId=496||Globus integration task force meeting||11 participants
Participation in ComputeAccounting wg, discussing Staged-Rollout and EA
|15 June||https://www.egi.eu/indico/conferenceDisplay.py?confId=498||UNICORE integration task force meeting||7 participants
Standard meeting, finalizing list of new GOCDB service types
|11 July||Globus integration task force meeting|
|14 July||UNICORE integration task force meeting|
2. Main Achievements
Within Interoperability the Globus integration task force https://wiki.egi.eu/wiki/Globus_integration_task_force has been started (similar to the UNICORE integration task force) and work on MS 414 "Integrating Resources into the EGI Production Infrastructure" https://documents.egi.eu/public/ShowDocument?docid=650 has begun.
One of the biggest issues with GOCDB UNICORE integration could be solved by implementing an alternative solution to enter ServiceEndPointURLs into GOCDB. After some bug reports all RFC 3986 chars can now be entered into the URL field. The first UNICORE services have been added to GOCDB. UNICORE SAM Nagios probes should be included in SAM Release 13.
Globus SAM Nagios Probes should be included already in SAM Release 12.
3. Issues and Mitigation
|Issue Description||Mitigation Description|