# Presentation: 811535

## Grid and Security Development Projects

- Overview and Relevance to Run II Experiments
- Ruth Pordes

- Run II Review Sept 2004

- 14th Sept 2004

## Scope

- Run II part of CD Grid Projects and collaborative projects PPDG and Open Science Grid Consortium.
- Projects under this category:
- Workflow Management - Runjob
- Grid Security Projects (VO Management and Privilege)
- PPDG
- Open Science Grid
- Within CD coordinated through the Grid and Data Management Coordination meetings

- Run II Review Sept 2004

- 14th Sept 2004

## Slide 3

| Project | Who | Duration | Current Effort | Benefit to Run 2 |
| --- | --- | --- | --- | --- |
| Runjob  | CMS, D0 | Evolving over past 4 years. 
Planned developments should  be complete in 2/05 | 1 FTEs core effort
1 FTE integration from each experiment. | Central maintenance and common support between D0 and CMS.
CDF requirements would naturally lead to use of Runjob. CDF will then be able to benefit from existing development. |
| VO Management | CMS, Grid3, SAM, LCG | 1.5 years to date to deploy common VO management and potentially registration service. | ~1 FTE US CMS.
~.25 FTE CD for Site Callout support | Expect CDF and D0 to use some modules when migrate from KRB5 to X509 based infrastructure and participate in shared grid (OSG).  |
| VO Privilege | US CMS US ATLAS PPDG | Initial deliverables 11/04; Expect project to last another 9-12 months.  | ~1.5  FTE CMS
1 FTE US ATLAS/PPDG | Once CDF and D0 participate in shared and common grid infrasturcture (FermiGrid, OSG) will make use of common VO access and policy services. |

- Run II Review Sept 2004

- 14th Sept 2004

## Some Illustrative Aspects of these Projects...

- Run II Review Sept 2004

- 14th Sept 2004

## Runjob
Stakeholders use the Services in different ways:
CMS - Job Configuration Service
D0 - Job Configuration and Execution Service
CDF - do not use Runjob yet. 

Must support and evolve existing implementations &  at same time move to common core infrastructure.

Schedule and priorities of participants vary.

- Stakeholders use the Services in different ways:
- CMS - Job Configuration Service
- D0 - Job Configuration and Execution Service
- CDF - do not use Runjob yet.
- Must support and evolve existing implementations &  at same time move to common core infrastructure.
- Schedule and priorities of participants vary.

- Run II Review Sept 2004

- 14th Sept 2004

## Slide 6

- Run II Review Sept 2004

- 14th Sept 2004

## Delivery to main sponsor and distributed contributors (BNL, LCG) requires effort and compromise.

Support model for external user communities. (e.g. Biology at ANL)?

Long term commitment needed for collaborations.

- Support model for external user communities. (e.g. Biology at ANL)?
- Long term commitment needed for collaborations.

- VO Services:
- Run II legacy systems make use of Fermilab infrastructure (e.g. kerberos). Interface site infrastructure (FNAL Kerberos) with new Grid infrastructure during production operations.

- Run II Review Sept 2004

- 14th Sept 2004

## VO Privilege
support standard callouts from Globus Gatekeeper & apply Site Identify/Authorization Mapping and User Authorization policies.

Globus Dynamic Account developer (working also with EGEE) wants to collaborate

Balance need for practical concrete deliverables for Fermilab VOs and commitment to participate in common and general services.

- support standard callouts from Globus Gatekeeper & apply Site Identify/Authorization Mapping and User Authorization policies.
- Globus Dynamic Account developer (working also with EGEE) wants to collaborate
- Balance need for practical concrete deliverables for Fermilab VOs and commitment to participate in common and general services.

- Run II Review Sept 2004

- 14th Sept 2004

## Open Science Grid Technical Groups and Activities together with  PPDG Contributions

- Run II Review Sept 2004

- 14th Sept 2004

## Slide 10

| PPDG Common Project for OSG: | Aspects of Deployment of: Accounting, Authorization, Blueprint/Architecture, Storage, Integration | CDF waiting to define project.
SAMGrid waiting for sufficient effort to contribute |
| --- | --- | --- |
| OSG Security Technical Group:  | Incident Response; Registration and Proper Use policies; Coordination, cooperation with LCG Joint Security Group;  Representation to gLite & EGEE Security Middleware groups. | Run 2 will benefit when migrate to common grid infrastructure and when operating across LCG and US sites |
| OSG Storage Technical Group | Mass Storage Services. Disk Space Management. Replica Location Services.  | SRM implementations key; dCache a technology for large sites; Interoperability between SRM implementations in progress. |
| OSG Blueprint | Principles and Architecture of Open Science Grid. Collaboration/liaising with gLite and ARDA architecture groups. | Run 2 development and operational experience valuable contributions. Forum to facilitate common services and interfaces and evolve Grid technologies |
| OSG Integration & Deployment | Infrastructure and framework for set of cooperating Facilities for Agreed upon and  Opportunistic Sharing of Resources. | US LHC will help enable and  allow  Run 2 applications to benefit from US LHC and other resources.  |
| OSG Support Centers & Operations | Coordinate support centers and define operational needs and model.  | CD CSS contributions will support Run II. US CMS contributions will help in overall operational model.  |

- Run II Review Sept 2004

- 14th Sept 2004

## Joint Projects provide opportunity for Run 2 to be involved in and influence new developments while maintaining appropriate level of contributions and  pragmatic approach to commitments...

- Run II Review Sept 2004

- 14th Sept 2004