1. G060643-00-Z LIGO's Physics at the Information Frontier Grant and OSG: Update Warren Anderson for Patrick Brady (PIF PI) OSG Executive Board Meeting Caltech - Dec 14, 2006

2. G060643-00-Z 2 Overview LIGO Data Grid (LDG) is Caltech, MIT, Penn State, U. Wisc-Milwaukee consortium. OSG support of LIGO data grid in 3 areas: » DOE Grids Certificate Authority (WBS 1.1.2.1.1.4) » VO Privilege Project (GUMS, VOMS, etc) » Virtual Data Toolkit (WBS 1.1.5.1) Other OSG-LIGO activities: » Caltech-ISI testing of Pegasus for LIGO workflow planning and execution on LDG/OSG (WBS 1.3.2.5) » UWM-Madison testing of Condor-C for LIGO workflow planning and execution on LDG/OSG

3. G060643-00-Z DEOGrids Certificates 13 action items originally identified Currently, there are: » 5 high priority items » 5 low priority items » 3 items which have been identified as internal to LIGO Status of OSG deliverable items: » High priority: one requires change to DOEGrids policy, two have proposed solutions, none of the five are completed. » Low priority: two require substantial changes to DOEGrids policy, one has a work-around. One of the six is completed. Priorities are not frozen. LIGO's evolving usage model leads to evolving priorities. » WGA will update OSG on new priorities as they stabilize.

4. G060643-00-Z VO Privilege Project LIGO (PSU) is evaluating VO Privilege Project (PP) tools (VOMS, GUMS, etc) for use on the LIGO Data Grid (LDG). LDG usage model - persistent user storage and user accounts with meaningful names (not pool accounts). Privilege project will not support LDG usage model. » Issues whose resolution is consistent with PP usage models have been successfully addressed. » LIGO, with help from PP personnel, is exploring LDAP interface to GUMS which might allow us to adapt GUMS to LDG usage model. Once technical issues are resolved, LDG sysadmins will still need to evaluate PP to determine if adoption saves them time and/or labor.

5. G060643-00-Z Virtual Data Toolkit LIGO relies on VDT for deployment of grid middleware across the LIGO Data Grid. LIGO has regular interactions with the VDT team » Bi-weekly conference call with Alain. » Weekly VDT Office Hours meetings. » Understand and rank problems experienced on LDG and assess solutions. This is a very productive relationship and is on track. LIGO issues » Will re-assess pacman as the distribution mechanism for some of these tools in spring 2007. » Would like upstream integration of VDT components – e.g. GSI patch for openssh.

6. G060643-00-Z Workflow planning LIGO is assessing two workflow management options. OSG-Caltech (well underway) » Use Pegasus for planning LIGO workflows on the OSG and LDG. » Need commitment to long-term support in addition to technical success if we are to adopt it as a production tool. UWM-Madison (recently started) » Have initiated testing of Condor-C for planning LIGO workflows on LDG and, in future, OSG resources. » Work is complimentary to OSG-Caltech effort and teams will meet/discuss in Jan 2007. Internal reports for both workflow options will be generated Aug. 2007 for consideration by LIGO Data Analysis Software and Computing Committees.

7. G060643-00-Z Extra Slide

8. G060643-00-Z Certificate Authority Issues High priority » OU=LIGO – requires DOEGrids policy change. » Notify RA of replacement – possible work-arounds, not fool-proof. » Update certificate metadata on replacement – underway? » LIGO specific email notifications – proposed work-around. » Secondary email address associated with certs – underway? Low priority » Longer duration certificates – against DOEGrids policy. » Require RA agent approval for replacement – against DOEGrids policy. » Allow VO field searches of database via script – done (Olson). » Stop certificate expiry emails after renewal – work-around proposed. » Better RA agent documentation - underway?