1 / 6

SA1 coordination

SA1 coordination. Maite Barroso, CERN SA1 F2F coordination meeting CERN. Agenda for the day. Track progress since the last meeting Agree plan for Y2 Plan for the next months, till next meeting in September At EGEE09, in Barcelona Prepare EU review, at the end of June. Agenda for the day.

bernie
Download Presentation

SA1 coordination

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SA1 coordination Maite Barroso, CERN SA1 F2F coordination meeting CERN

  2. Agenda for the day • Track progress since the last meeting • Agree plan for Y2 • Plan for the next months, till next meeting in September • At EGEE09, in Barcelona • Prepare EU review, at the end of June

  3. Agenda for the day • OAT milestones • C-COD and R-COD • EGI update • EGI release and deployment model • User support

  4. Country reports • each country (JRU) directly reports its SA1 related activity • including the country report metrics • including national and international resource use • The SA1 QR will become the direct assembly of these reports with minimal editing; still quarterly • Similar to SA1 country reports • Diff format so they can be easily aggregated (instead of digested and summarized, as they are now) • reason for this change • NGIs to establish reporting activity of their international and global NGI tasks • to regularly review the expanding metrics automation work. • Next: May-June-July • Template by mid-June; filled by the end of July

  5. Actions from today • OAT (James Casey): Define messaging deployment scenario based on early experience, matching scale needed and regional needs • By next meeting, so regions can plan HW and expertise • COD (Helene Cordier): • Define C-COD model to be prototyped in next 3 months (who will do it, how many FTEs), by the end of June • Define Key Performance Indicators for R-COD • Format similar to MSA1.3, seed resources metrics, etc • To be automated and displayed by the related tools/teams • Deployment (Antonio Retico): discuss with SA3 and JRA1 to define an implementation to the requirement on production repository always consistent

  6. Actions from today User Support (Torsten Antoni): • CENTRALLY COORDINATED FEW (2-3) FULL-TIME TPM TEAMS • More automation in ticket assignment to regions • Role of the central TPM teams: ticket assignment (of the few not automatically routed), escalation, monitoring • Refine and put in place this model in Y2 • Discuss and agree mw support with product teams/mw providers? So it is properly staffed Country reports: agreement to start with them at next quarter • Action on Maite to distribute template • To be filled by all partners and grouped by country at mid July

More Related