Subject: For VO Admins and other VOMRS privileged users
From: Maria Dimou-Zacharova <[email-masked]>
To: <[email-masked]>, <[email-masked]>, <[email-masked]>, <[email-masked]>, <[email-masked]>, <[email-masked]>, <[email-masked]>, <[email-masked]>, <[email-masked]>, <[email-masked]>, <[email-masked]>, <[email-masked]>
Cc: vomrs-grid-support <[email-masked]>, Andrea Ceccanti <[email-masked]>, Vincenzo Ciaschini <[email-masked]>, <[email-masked]>
Date: Mon, 21 Jul 2008 17:38:54 +0200

Dear VO Administrators and Representatives,

at the March 2008 Grid Deployment Board (GDB) you were presented with a
proposal to converge vomrs and voms-admin in order to save development
and service resources and, also, to simplify operation [R1].

Following your approval, the VOM(R)S Working Group (WG) assembled
the VOMRS features still not available in VOMS-admin and recorded them
both in savannah [R2] and also below.

Please do read through the appended list of features that need to be ported
to voms-admin.

Then, please send us the item(s), if any, in this list containing
feature(s) *no more* needed by you and explain the reason for that.
Do not hesitate to ask if a feature description is unclear.
Use [email-masked] for this correspondence.

We need your input before planning the required development work in detail.

Please check our twiki [R3] for more information or join one of our regular
meetings [R4].

Thank you in advance for your answer.

Best Regards,

Maria Dimou on behalf of the VOM(R)S WG.

======================================================================
List of features missing in voms-admin [R2]
-------------------------------------------
1.  Member status values 'suspended' and 'expired' (not only due to an 
expired certificate).

2.  Member institutional expiration (a date copied from an external db 
or added by VO Admin).

3.  Group/Group_Role-related items:
3.1 Group membership access (Open/Restricted, i.e. not everyone can 
subscribe without approval to all Groups).
3.2 Group description (a text field that explains what this Group is about).
3.3 Group_Role membership access (Open/Restricted, i.e not everyone can 
subscribe without approval to all VOMS Roles).
3.4 Group_Role description  (a text field that explains what this VOMS 
Role is about).
3.5 Ability to attach Group_Role to Group (some VOMS Roles don't make 
sense from within some Groups).

4.  Dynamic list of collected personal information (the VO Admin can 
decide which personal information to collect,
     from passport number to hair colour. LHC experiment VOs do not use 
this feature).

5.  Event subscription (one can decide which email notifications (s)he 
wishes to receive when an event occurs, e.g.
     candidate VO member to approve, request to join a Group or 
Group_Role etc).

6.  Interfacing third-party directory during registration and membership 
validation (e.g. LHC experiment VOs now
     extract all required personal information of the candidates from 
the CERN HR db).

7.  Configurable online help in web UI (one can tailor the web page of 
his/her VO Registration with info specific to the VO).

8.  UI-related items:
8.1 Web UI: Sortable output, selectable output informantion (in VOMRS 
you can tick the fields you wish displayed when searhing).
8.2 Ability to execute actions for multiple users simultaneously (in 
VOMRS you can, for example, add/remove a long list of users from a Group).

References:
===========

R 1  Original presentation on the subject
http://indico.cern.ch/getFile.py/access?sessionId=9&resId=1&materialId=0&confId=20227

R 2  VOMRS<-->Voms-admin convergence features:
https://savannah.cern.ch/search/?words=vom%28r%29s+convergence&type_of_search=bugs&Search=Search&exact=1#options

R 3  VOM(R)S activity notes:
https://twiki.cern.ch/twiki/bin/view/LCG/VomsWG

R 4  VOM(R)S WG Communication:
http://indico.cern.ch/categoryDisplay.py?categId=1217
--