Participants:
Maria Dimou, Joni Hahkala, Tanya Levshina (on the telephone), Karoly
Lorentey.
Agenda: Approved in advance via email:
. Status of the actions of our 15-17 September meeting http://cern.ch/dimou/lcg/registrar/TF/meetings/2004-09-15/minutes (All) . Review of the plan (Maria) . News from FNAL management (Tanya) . News from ORGDB privileged access (Karoly) . Walk through the registration flow http://cern.ch/dimou/lcg/registrar/TF/VOMRS_Registration_flow.gif (Tanya (please, edit changes) and Karoly). . New savannah tickets (Tanya, please add old requests you still have in emails, if any).
Repeating all actions below from the minutes of the previous meeting:
(*** ACTION ***) On Ian's suggestion Maria will create 3 savannah tickets containing all the existing VOMS/VOMRS-related tickets across groups per category (Major, Normal, Enhancements). PENDING
Ticket 4699: This is of the category "Major". (*** ACTION ***) Joni should edit the summary to add the "VOMS" string and remove the names of the users, not to disclose, indirectly, the names of the VO members. DONE
Ticket 4700: This is of the category "Normal". (*** ACTION ***) Joni should edit the summary to add the "VOMS" string. DONE
Ticket 860: Maria closed this ticket with Karoly's anwer. She opened ticket 1185 to describe the task of defining what to store on user's CA information. Please read the tickets for details. (*** ACTION ***) Tanya: VOMRS should also store the user certificate serial number and his/her CA's contact URL. PENDING
Ticket 1132: (*** ACTION ***) Tanya will make the necessary changes so that newly registered VOMRS users don't receive 2 almost identical emails when they pass from status "New" to "Approved" in the VO. By this date, Maria completed her action on making sure VOMRS notification emails will never fall into spam again. She informed the TF by email on the reasons and the solution (whitelisted the string "VOMRS" at the CERN central email gateway level). PENDING
Tickets 1133 and 1141: Discussed with Tanya, understood and closed by Maria. The reason was that Maria's certificate had expired. It would be good if the error message were not so misleading. (*** ACTION ***) Tanya should re-open the ticket if such an enhancement can be envisaged by the VOMRS developers. PENDING
Ticket 1136: This is about CVS locations for EGEE and LCG software. (*** ACTION ***) Maria should make a CERN afs account for Tanya and do the necessary for her to obtain CVS access. PENDING
(*** ACTION ***) Tanya will enter in the savannah group lcgoperation the bugs she has observed. Example: Simultaneous "commit" of changes via the User Interface and the VOMS db API causes the db tables to go out of sync. This is, most probably not a database problem but an application problem of voms-admin. PENDING
(*** ACTION ***) Karoly will make sure that bug fixes of the savannah group lcgoperation will be made available in the development branch as well (JRA1) and vice-versa, i.e.bug fixes for tickets in the savannah group JRA1mdw will be fed into the EGEE and LCG development/deployment CVS. DONE
(*** ACTION ***) Joni will register in the savannah/JRA1mdw category the task (classify = Major) to allow VO names of more than 6 characters to be accepted. This is not a problem for LHC experiment VOs but it will be for several EGEE ones. VO=NA4test is already defined and it is one of them. The solution should be found between Joni, Vincenzo, Karoly and Akos. DONE
(*** ACTION ***) Create a new savannah ticket on VO nicknames and multiple DNs. By the time these notes are written Ian created Ticket 4861. DONE (see comment on ticket for latest status).
(*** ACTION ***) Karoly to email the following questions to Wim van Leersum (ORGDB expert) and make the answers available to the TF:
PARTIALLY DONE. WE NEED TO ANALYSE THE LINKED EMAIL THREAD AT THE NEXT CHECKPOINT MEETING.
(*** ACTION ***) Karoly, with his Oracle login, search in ORGDB and relay results to the TF:
PARTIALLY DONE. WE NEED TO ANALYSE THE LINKED EMAIL THREAD AT THE NEXT CHECKPOINT MEETING.
The answers on the above will help us decide whether we should use the Contract_End_Date or Participation_End_Date to calculate the initial value of the VODB_Expiry_Date or not. They may also result to a recommendation to CERN IT Management on information quality improvement for CERN HR db. (*** ACTION ***) Maria. PENDING (it can only be done when the ORGDB content quality is fully understood).
The ORGDB view with the necessary and sufficient Personal User data, according to the Requirements' definitions may need to be tailored according to experiments' rules (*** ACTION ***) Karoly and Maria to investigate and inform the TF. PENDING
Tanya showed the VOMRS user interface to the participants. (*** ACTION ***) Maria who is a registered member will make available to the TF a list of features. PENDING (Tanya suggested that this gets done after the massive amount of VOMS code changes stabilise).
(*** ACTION ***) Tanya expressed worries that US-CMS users won't accept to type their birthdate, even if it is only DDMM (no year) and even if it is not logged in clear, simply a string saying that it was provided. She also said they might be reluctant to register in CERN HR db, even if this is LHC experiment policy. She should give the TF feedback from discussions on this matter with her community. PENDING
(*** ACTION ***) Someone (Maria?) should give the VO managers and resource administrators a recommendation on usage of Groups (Group Roles) and Roles. The VOMS-admin "Capabilities" attribute will not be used. Partially DONE i.e. we have concluded on a recommended number and naming of Groups and Roles. Maria is writing a document that will be announced a.s.a.p.
(*** ACTION ***) Maria create savannah ticket for VOMS admin and VOMRS to set Return-email-address to the one of the VO manager for user notifications that can't reach the recipients. PENDING
(*** ACTION ***) TF to re-discuss the Usage Rules re-acceptance prompt in more detail. PENDING
VOMS admin software will be supported by Karoly Lorentey and all reported bugs will be fixed. (*** ACTION ***) LCG deployment management has to plan for maintenance continuity after Karoly's departure from CERN). PENDING
EDG trust manager will be supported by Joni Hahkala and all reported bugs will be fixed. (*** ACTION ***) LCG/EGEE management has to plan for maintenance continuity after Joni's departure from CERN). PENDING
VOMRS will be installed at CERN and Maria will perform all the necessary testing of the software. PENDING (Tanya suggested that this gets done after the massive amount of VOMS code changes stabilise).
(*** ACTION ***) Ian should investigate with the LCG Deployment management whether resources could be found elsewhere in the community to assist Tanya in the VOMRS development work. PENDING
The access to all necessary data in ORGDB is now more than critical. Tanya
said that her management's final official commitment will depend on the quality
of these data. So far, they acknowledge LCG's commitment to use VOMRS but the
only person doing code adaptation is Tanya. She prepared a
VOMRS_new_req_4.doc integrating
comments she received from Maria and Karoly.
(*** ACTION ***) Tanya plans
to make a UML diagram in addition to the VOMRS
Registration Process flow as soon as possible. It will include details
on the user's CA information that must be stored according to Ticket
1185.
Karoly fixed several bugs in voms-admin. Version 0.7.4 is now available. (*** ACTION ***) Karoly will email the rpms to Tanya.
The VOMS deployment plan suggests these meetings take place monthly. Suggested date is December 6th 2004 at 16hrs.
Maria Dimou, IT/GD, Grid Infrastructure Services
