1. Apr 30, 20081/11 VO Services Project – Stakeholders’ Meeting Gabriele Garzoglio VO Services Project Stakeholders’ Meeting Apr 30, 2008 Gabriele Garzoglio Computing Division, Fermilab Overview Goals and Stakeholders The VO Service project: Status, Effort WBS Focus of Phase III (Nov 07 - Now) Requests on the table

2. Apr 30, 20082/11 VO Services Project – Stakeholders’ Meeting Goals 1.Get input from stakeholders on priorities and tasks 2.Present project status and current WBS Gabriele Garzoglio Stakeholders CD, USCMS, USATLAS, OSG VOMRS: CERN, LHC VOs

3. Apr 30, 20083/11 VO Services Project – Stakeholders’ Meeting Gabriele Garzoglio Project Definition From Project Database: “The VO Services project provides user registration services and fine-graned access management to computing and storage resources on the Grid.”

4. Apr 30, 20084/11 VO Services Project – Stakeholders’ Meeting Scope: Software Components Policy Enforcement Points (PEP) –PRIMA, PRIMA-WS –gLExec (collaboration w/ EGEE) Policy Decision Point (PDP) –GUMS –GUMS Operational / Monitoring framework Registration Services –VOMRS Related Projects, external to VO Services –SAZ (FermiGrid) –gPLazma (dCache) Gabriele Garzoglio

5. Apr 30, 20085/11 VO Services Project – Stakeholders’ Meeting Nominal Effort Gabriele Garzoglio PersonResponsibility% FTELocated atPaid by G. GarzoglioProj. Management30 FNALCD I. SfiligoiPRIMA, gLExec50 FNALUSCMS T. LevshinaVOMRS30 FNALCD J. PackardGUMS50 BNLOSG Other experts: J. Hover (BNL) J. Weigand (FNAL) Nominal Effort Table 2008 2007

6. Apr 30, 20086/11 VO Services Project – Stakeholders’ Meeting WBS Phase III 1.Support and deployment (High Priority) 1.Support the PRIMA and GUMS code. Few %, Ongoing 2.Support “stable” VOMRS release 15% Tanya, Ongoing. 3.Deployment at sites. (Few %, Ongoing) 4.VOMRS maintenance (High Prio) 1.Fix critical bugs 2. Implementation of “vital” features 3.Convergence of VOMS-admin 2.5 with VOMRS. 5.gLExec maintenance (High Prio) Gabriele Garzoglio Ongoing Maintenance/Support Activities

7. Apr 30, 20087/11 VO Services Project – Stakeholders’ Meeting WBS Phase III 2.Improve robustness of GUMS (Medium-Low Prio) 1.Improve GUMS configuration management (3 FTE weeks) 1.implement stand-alone configuration validator 2.improve debugging capabilities (date fields in database?). 3.add query interface for “last changed date”. 2.Redundant servers configuration (Done: FermiGrid HA) 3.Refuse authorization if cannot synch with VOMS several times (1 FTE Week) 3.Improve GUMS usability (Medium Prio) 1.Implement history log querying interface (2 FTE week) 2.Map pool accounts to DN AND FQAN, rather than DN only. 3.Pool accounts should NOT be mapped to users during VOMS synchronization simply to create vo name maps 4.Recycle pool accounts (4 FTE weeks) 5.Validation Tool to Check the Site Authorization Infrastructure configuration (1 st Release Done) Gabriele Garzoglio Feature improvements for GUMS - New Proposal in Phase III - Expired or Addressed in another project

8. Apr 30, 20088/11 VO Services Project – Stakeholders’ Meeting WBS Phase III 9.Support Storage Groups in Defining Next Generation Storage Authorization Models (Medium Prio) 14.Investigate Mechanisms to Define and Enforce VO and Site AuthZ Policies (SBIR w/ TechX) 8.Authorization Interoperability (Medium-High Prio) 1.Manage transition of development team [Done Jan 08] 2.Project Oversight [Ongoing] 3.Define Interoperability XACML Profile (Feb 08) 4.Develop XACML/SAML library (Chad / Hakon) 5.Test XACML / SAML library with different infrastructures 6.Integrate XACML/SAML library with existing infrastructures 7.Packaging, deployment, and user documentation 8.Test interoperability Gabriele Garzoglio Investigative and Refurbishing work

9. Apr 30, 20089/11 VO Services Project – Stakeholders’ Meeting WBS Phase III 10.Enable VOMS-signed Attribute Certificate Validation (stop VOMS/GUMS synch.) 11.Site Validation Service 12.Integrate Shibboleth with Registration and Authorization infrastructure 13.Broaden and standardize authorization call-out interfaces Gabriele Garzoglio Requests bound by limited effort and other work Not enough effort available 6.Improve software validation (8 FTE weeks) (Low Prio) 1.Improve validation of basic functionalities 2.Implement validation of software dependencies. 7.Outreach (Medium Prio) (Ongoing) 1.Understand Requirements from new VOs and groups 2.Keep contacts with other groups, such as EGEE and GT.

10. Apr 30, 200810/11 VO Services Project – Stakeholders’ Meeting Focus of Phase III (Nov 07 – Now) Ongoing Maintenance and Support Authorization Interoperability (Due Aug 08) –Successful collaboration w/ EGEE, Globus, and Condor via MWSG and regular meetings Investigate Mechanisms to Define and Enforce VO and Site AuthZ Policies (SBIR Phase I Done; Phase II pending) Validation tool to check consistency of site AuthZ configuration (1 st release Done) Gabriele Garzoglio

11. Apr 30, 200811/11 VO Services Project – Stakeholders’ Meeting OSG Requests Document usage of AuthZ configuration variables at a site –Extends: “3.5 Validation Tool to Check the Site Authorization Infrastructure configuration” Document differences in the usage of FQAN between EGEE and OSG Check VOMS identity before GUMS synch. 10.Enable VOMS-signed Attribute Certificate Validation (stop VOMS/GUMS synch.) Gabriele Garzoglio