Difference between revisions of "EGI-InSPIRE:SA1.3-QR5"

From EGIWiki
Jump to: navigation, search
(4. Plans for the next period)
(3. Issues and Mitigation)
Line 67: Line 67:
 
! scope="col" | Issue Description  
 
! scope="col" | Issue Description  
 
! scope="col" | Mitigation Description
 
! scope="col" | Mitigation Description
 +
|-
 +
| Change of Personal for global Task "Coordination of Interoperations between NGIs and with other DCIs" due to paternal leave in the next few quarters.
 +
| The person taking over has been prepared over several months and has extensive experience with Grid Computing and Management. Some other people within the organization are hopefully understanding and helpful and will support him in this task if needed.
 +
|-
 +
| Some holding back of NGIs in early support of Globus. Some NGIs want others to go first and keep their Globus sites only national in the beginning until they are sure someone else has already found all the possible bugs.
 +
| Unsure about a really good mitigation. Possible better communication about what already works can help. Maybe some further exceptions for the calculation of availability are needed, because people are very afraid that not yet 100% working sites will look bad in some statistics. And we should have a way to reward very active NGIs which are pushing the development forward and volunteer for EA positions, like Germany.
 
|-
 
|-
 
|}
 
|}

Revision as of 15:17, 6 July 2011


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

Consitutional meeting

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
Change of Personal for global Task "Coordination of Interoperations between NGIs and with other DCIs" due to paternal leave in the next few quarters. The person taking over has been prepared over several months and has extensive experience with Grid Computing and Management. Some other people within the organization are hopefully understanding and helpful and will support him in this task if needed.
Some holding back of NGIs in early support of Globus. Some NGIs want others to go first and keep their Globus sites only national in the beginning until they are sure someone else has already found all the possible bugs. Unsure about a really good mitigation. Possible better communication about what already works can help. Maybe some further exceptions for the calculation of availability are needed, because people are very afraid that not yet 100% working sites will look bad in some statistics. And we should have a way to reward very active NGIs which are pushing the development forward and volunteer for EA positions, like Germany.

4. Plans for the next period

Interoperability:

  • Preparations for the EGI TF in Lyon.
  • Finalizing MS 414.
  • Deeper focus on Accounting with the outcome after the EMI Computeraccounting wg within the UNICORE and Globus integration task forces.