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=MeMMMu292nDvDa9n98Dv9e
- Password: SA1
- Phone Bridge:
ID: 1630851
Password: 7164
    • 10:00 10:10
      Admin matters
      1. QR7
      2. DSA1.5: Operations Cookbook
      3. MSA1.11: Security Policy Integration
      4. MSA1.12
      5. 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:50
    National seed resources

    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:50 11:10
    Next steps to put regional Nagios with central dashboard/regional views in production
  • evaluation from RODs
  • next steps
  • slides
  • 11:30 11:45
    January EGEE league table
  • one site candidate for suspension in AP ROC: INDIACMS-TIFR (7%, 8%, 45%)
  • one ROC with average availability below 70%: IGALC (63%), second consecutive month
  • please, chase sites to fill the comments: https://twiki.cern.ch/twiki/bin/view/EGEE/MonthlyAvailability. Could ROCs open tickets against sites not filling this properly?
  • 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:45 12:00
    AOB
  • End of CIC site reports as input for weekly operations meeting
  • APEL problems: requets for postmortem (and where in the procedures shall we include this?)
  • In Amsterdam on March 03 2 pm we will have a face to face OTAG meeting, I would like to invite the ROC/NGI representatives to attend this meeting. The agenda is under discussion, however the purpose is to gather input from NGIs about new requirements.
  • incident in CA change of the Biomed serveur VOMS: AP, CE, FR, IT, RU, SEE, SWE, and UKI, to ensure that their 14 sites having biomed SEs are upgraded.
    Please find enclosed the list of sites and related GGUS tickets explaining the procedure to follow due do the french CA name change from GRID-FR to GRID2-FR.
    A focussed broadcast on these 14 sites/ROCs will also be sent out today.
  • more information