• Europe/Zurich
  • English
  • Login
Filter
 
Focus on:  Hide Contributions
iCal export
lecture WLCG-OSG-EGEE Operations meeting
Date/Time: Monday, 8 January 2007 - 16:00 (Europe/Zurich)
Location: CERN conferencing service (joining details below) ( 28-R-15 )
Chairperson:
Description: grid-operations-meeting@cern.ch
Weekly OSG, EGEE, WLCG infrastructure coordination meeting.
We discuss the weekly running of the production grid infrastructure based on weekly reports from the attendees. The reported issues are discussed, assigned to the relevant teams, followed up and escalated when needed. The meeting is also the forum for the sites to get a summary of the weekly WLCG activities and plans
Attendees:
  • OSG operations team
  • EGEE operations team
  • EGEE ROC managers
  • WLCG coordination representatives
  • WLCG Tier-1 representatives
  • other site representatives (optional)
  • GGUS representatives
  • VO representatives

    • To dial in to the conference:
    a. Dial +41227676000
    b. Enter access code 0157610

    OR click HERE

    Material: list of actions link minutes link

     
     Monday, 8 January 2007
     16:00
    Feedback on last meeting's minutes (5')    
     16:05
    EGEE Items (25')    
    • Grid-Operator-on-Duty handover (5')
      From ROC Italy (backup: ROC UK/I) to ROC CERN (backup: ROC France)

      Tickets:
      New tickets: 19
      1st email: 11
      2nd email: 11
      'Case transfered to political instances': 2
      Qurantine: 16
      Site OK: 18

      Notes:

    • Possible suspension of site ClusterUL (GGUS Ticket #16273)
    • Possible suspension of site TAU-LCG2 (GGUS TicketS #15135 and 15135)
    		 
    • VOMS configuration update effective Jan 9th 2007 due to new hostcert of voms.cern.ch (5')
    		 
    • Operational issues raised by VOs (5') 
      None at time of writing the agenda (14:00 UTC)
    		 
    • EGEE issues coming from ROC reports (10')
      Reports were not received from these ROCs:
      Reports were not received from these non-HEP VOs:

      1. VOMS and VO membership expiration date: A french dteam user was unable to generate a VOMS proxy from DTEAM VOMS. The error message was not clear: "Error: dteam: User unknown to this VO".
        After some deeper investigation, it appeared that his VO membership was expired within the VOMS Database. Indeed, it seems that a VO expiration delay is set to 1 year by default. The involved user didn't receive any notification concerning this expiration. Moreover, as the CERN was closed, no Dteam administrator was able to change the expiration date. Such a case could become very tricky with a VOMS entry used for production purposes as the related user could not generate any proxy to submit his/her production jobs. In order to avoid to manage several expiration dates, could we change the VO membership expiration policy to use the user certificate expiration date as the VO membership expiration date by default ?
        We also suggest that a mail must be systematically sent to the user when his/her VO membership is about to expire. (France ROC)


    		 
     16:30
    OSG Items (20')     
    No items for discussion.
     16:50
    WLCG Items (45')    
     
    Harry Renshall  
    • WLCG related Issues coming from experiment VOs and Tier-1/Tier-2 reports (15') Tier 1 Site Report unknown type filedown arrow  
      Reports were not received from:
      > Tier-1 sites:
      > VOs:

    • None
    		 
     17:35
    Review of action items (20')   list of actions link    
     17:55
    AOB (5')