Focus on:  Hide Contributions
Login

SA1 coordination meeting

→ Europe/Zurich
28-R-06 (CERN)

28-R-06

CERN
Description

Minutes, https://edms.cern.ch/document/923879

Actions, https://twiki.cern.ch/twiki/bin/view/EGEE/SA1_CoordinationTasks

This meeting is 10:00 to 11:30 UTC+1
Remote Participation via EVO in the EGEE Community.
Meeting Access Information:
- Meeting URL
http://evo.caltech.edu/evoGate/koala.jnlp?meeting=MvM2Ml2D2iDIDu9a9lDe9v
- Password: SA1
- Phone Bridge:
ID: 1715260
Password: 7164
    • 10:00 → 10:10
      Admin matters
      1. DSA1.5: Operations Cookbook
      2. MSA1.12: Revised Operation Process, Policy, Procedures and Interfaces for EGI
      3. DSA1.2.2
    • 10:10 → 10:30
      Transition to EGI

      The details of next meeting in Amsterdam are up - https://www.egi.eu/indico/conferenceDisplay.py?confId=1


      Follow actions from F2F SA1 coordination meeting

    • O-E-9: Coordination of middleware roll-out and deployment: did the new responsibles already start? report about early experience, if applicable
    • O-E-10: Coordination of resource allocation and of brokering support for VOs from NGIs, from Poland to Amsterdam. Action on Poland to document present procedures to be transferred to Amsterdam.
    • O-E-11: Coordination of interoperations between NGIs and other grids. EGI.eu, from CERN to Sweden. New responsible name known?
    • O-E-14: Operation of production grid core software services, catch-all services for international VOs, catch-all CA, from all ROCs to GRNET. Clarify list of services included
    • dteam future
    • NGI prototyping progress and issues
  • 10:30 → 10:40
    National seed resources

    The input received till now (from France and CE) is available here:
    https://edms.cern.ch/document/1065562

    These national seed resources are specified in table 8: Regional resource Commitments, estimated at the end of project year 1, page 209:

    https://edms.cern.ch/document/1014682/1

    I would like to request each ROC or Country/JRU/NGI/partner to understand the usage of the production infrastructure done to introduce new VOs/users in the region (probably using the regional infrastructure VOs?), and come back to me with some figures or some text describing this activity through the whole EGEE III project. I would appreciate if this is send to me before the end of February.
    Please, ROC managers, pass this to your JRU contacts so we get information from everybody (though a summary per region should be enough).

  • 10:40 → 10:55
    APEL incident postmortem 15m
    more information
  • 10:55 → 11:10
    February EGEE league table

    three sites candidate for suspension:
    AP ROC:
    - INDIACMS-TIFR (13%, 7%, 8%)
    - PH-ATENEO (37%, 31%, 47%)

    Russian ROC:
    - ru-Moscow-MEPHI-LCG2 (0%, 0%, 41%)

  • all ROC above average availability, back to normal.
  • All sites did fill the comments: https://twiki.cern.ch/twiki/bin/view/EGEE/MonthlyAvailability.
  • For suspended sites, remember to check the ops procedures: ROC managers have to regularly give their attention to all their suspended sites, so that they are processed within the given maximum time of four months. If they are not certified by them, maybe the site should be closed?
  • 11:10 → 11:30
    Next steps to put regional Nagios with central dashboard/regional views in production
  • evaluation from RODs
  • next steps
  • 11:30 → 11:45
    AOB
    • Powered by Indico v3.3.2-pre