From EGIWiki
Jump to: navigation, search
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

Detailed agenda: Grid Operations Meeting 16 April 2012 14h00 Amsterdam time

EVO direct link Pwd: gridops
EVO details Indico page

1. Middleware releases and staged rollout

1.1 EMI release status

1.2 Staged Rollout

Upcoming EMI update 15 (see Cristina's presentation)

EMI2 is scheduled for the 7th of May.

2. Operational Issues

2.1 BDII instability

Possible connection between the problems (G.Borges):

For all NGIs:

2.2 VOMS Admin fails notifying about exipiring membership

2.2.1 Description of the problem

A bug was found affecting the VOMS Admin process of sending warning messages when user membership is about to expire. The VOMS Admin versions affected by the bug are:

These VOMS Admin versions enforce the user membership expiration (default every 12 months). The bug prevents the sending of a warning email before the users' membership expiration, VO managers are notified only once the user is suspended, after the membership expiration.

2.2.2 Possible workarounds

  1. Extension of VO membership up to 30 September 2012
    • For users whose membership is expiring before 30 Sep 2012
    • This will allow VOMS administrator to upgrade their services once the bug fix is available
    • instructions
  2. Manual notification of the list of users with expiring membership
    • Every month VOMS server administrator should produce, for every VO affected by the bug, a report of the users whose membership are expiring during the month and communicate those lists to the VO managers.

2.2.3 AuP grace period

For the VOs using the same VOMS releases reported above, users are requested to re-sign the VO AuP, as an additional step to renew the membership. Currently the default grace period is 24 hours, VOMS administrators are strongly suggested to extend this grace period to 7 days, a warning email is sent to the users at the beginning of the grace period, this change in configuration will give more time to users to perform their step (the users who do not resign the AuP are suspended at the end of the grace period).

2.3 New GOCDB roles in production

New roles were rolled in production on April 10th.

GOCDB users were automatically assigned to the new roles:

Important: For the operations tools nothing have changed after the switch to the new roles, if you notice any different behavior in the the tools, please report it in a GGUS ticket.

2.3.1 Problem reported and solved

4. AOB

4.1 Next meetings

Personal tools