[1. The Particle Physics Data Grid 2](#the-particle-physics-data-grid)

[1.1. Concept of the Proposal 2](#__RefHeading___Toc59292428)

[1.2. Background and Accomplishments: the Collaboratory Pilot
2](#background-and-accomplishments-the-collaboratory-pilot)

[1.2.1. 2](#section-1)

[1.3. Goals and Requirements -- from Fabric to Physics
2](#goals-and-requirements-from-fabric-to-physics)

[1.3.1. The Grid Fabric 2](#__RefHeading___Toc59292433)

[- extend and harden the system to be more performant and maintainable
2](#__RefHeading___Toc59292434)

[1.3.1.1. High Throughput Data Access and Transport
2](#__RefHeading___Toc59292435)

[Application community to test and evaluate new data transport layers
and data caching capabilities 2](#__RefHeading___Toc59292436)

[1.3.1.2. Facility Services through Standard Interfaces
2](#__RefHeading___Toc59292437)

[1.3.1.3. Grid System Services 2](#__RefHeading___Toc59292438)

[1.3.1.4. Access Control 2](#__RefHeading___Toc59292439)

[1.3.1.5. Accounting and Accountability 2](#__RefHeading___Toc59292440)

[Understand the scope and boundaries between policy and accounting.
Evaluate and talk to existing efforts (e.g. NCSA). Work will be done to
better understand experiment and facility management requirements,
deploy and evaluate short to medium term technologies in our application
systems and facilities. 3](#__RefHeading___Toc59292441)

[1.3.1.6. Security 3](#__RefHeading___Toc59292442)

[1.3.2. End-to-end Physics Application Usage of the Grid
3](#__RefHeading___Toc59292443)

[1.3.2.1. Robust, Scalable Storage, Data, Meta-Data and Job Management,
3](#__RefHeading___Toc59292445)

[1.3.2.2. Information Management 3](#__RefHeading___Toc59292447)

[1.3.2.3. Usability 3](#__RefHeading___Toc59292452)

[1.4. Development and Deployment -- a Coordinated Approach
3](#development-and-deployment-a-coordinated-approach)

[1.4.1. AManaged Scalable System -- 1/2 page -- Harvey, John,
4](#amanaged-scalable-system-12-page-harvey-john)

[1.4.2. The Grid Facility Infrastructure -- 1/2 page - Bruce, Don,
Wyatt, Richard, Lothar
4](#the-grid-facility-infrastructure-12-page---don)

[1.4.3. Data Grid Services Architecture -- 1 paragraph -- Greg, Miron,
Ruth, 4](#__RefHeading___Toc59292457)

[1.4.4. PPDG Common Project Program of Work -- 2/3 page
4](#ppdg-common-project-program-of-work-23-page)

[1.4.4.1. Grid System Management Services -- Regan, Arie, Harvey,
Richard 4](#grid-system-management-services-regan-arie-harvey-richard)

[1.4.4.2. Facility Grid Service Interfaces -- volunteers please
4](#facility-grid-service-interfaces-don)

[1.4.4.3. System Integration and Deployment -- volunteers please
4](#system-integration-and-deployment-lothar)

[1.4.5. Computer Science Program of Work -- 2/3 page
4](#computer-science-program-of-work-miron)

[1.4.5.1. Condor -- Miron, Peter 4](#__RefHeading___Toc59292463)

[1.4.5.2. Globus -- Greg, Ian 4](#__RefHeading___Toc59292464)

[1.4.5.3. SRB - Reagan 4](#__RefHeading___Toc59292465)

[1.4.5.4. SRM - Arie 5](#__RefHeading___Toc59292466)

[1.4.6. Experiments Program of Work 5](#experiments-program-of-work)

[1.4.6.1. High Energy Physics - 1 page 5](#high-energy-physics---1-page)

[1.4.6.2. Nuclear Physics -- 2/3 page 5](#__RefHeading___Toc59292469)

[1.4.7. Laboratory Facility Program of Work -- 1 page
6](#__RefHeading___Toc59292470)

[1.4.7.1. BNL -- Bruce, Jerome, David 6](#__RefHeading___Toc59292471)

[1.4.7.2. Fermilab -- Wyatt, Lothar, Don 6](#__RefHeading___Toc59292472)

[1.4.7.3. LBNL - Bill Johnston, Doug 6](#__RefHeading___Toc59292473)

[1.4.7.4. SLAC - Richard, Bob 6](#__RefHeading___Toc59292474)

[1.4.7.5. TJNAF -- Chip, Sandy 6](#__RefHeading___Toc59292475)

[1.4.8. Convergence and Stability -- 1/2 page -- volunteer please?
6](#convergence-and-stability-qa-metrics-testing-ruth)

[1.4.8.1. Quality Assurance and Metrics 6](#__RefHeading___Toc59292477)

[1.4.8.2. SoftwareTesting 6](#__RefHeading___Toc59292478)

[1.4.8.3. Application Integration 6](#__RefHeading___Toc59292479)

[1.4.9. Deliverables and Milestones 6](#deliverables-and-milestones)

[1.4.9.1. Phase 0 --PPDG Year 3 -- 1/2 page
6](#phase-0-ppdg-year-3-12-page)

[1.4.9.2. Phase I 12 months (June2004-2005) -- 1/2 page
6](#phase-i-12-months-june2004-2005-12-page)

[1.4.9.3. Phase II 12 months (June 2005-2006) -- 1/2 page
6](#phase-ii-12-months-june-2005-2006-12-page)

[1.4.10. Partnerships and Coordination (1/2 page) 6](#section-35)

[1.4.11. Transition and Support (1 paragraph)
6](#__RefHeading___Toc59292485)

[1.4.12. PPDG Management Plan (1/2 page)
6](#ppdg-management-plan-12-page)

[1.4.13. Outreach and Education (1 paragraph)
6](#outreach-and-education-1-paragraph)

[1.4.14. Budget summary and justification (1 paragraph)
6](#budget-summary-and-justification-1-paragraph)

[1.5. Subcontract or Consortium Arrangements
6](#subcontract-or-consortium-arrangements)

[2. Literature Cited 6](#literature-cited)

**The Particle Physics Data Grid** **\
From Fabric to Physics**

DRAFT: V1.0; 12/15/03

*Total page count: 9 paragraphs (2.5 pages) + 11 pages \~: 13.5 pages*

*In this draft names are assigned to some of the paragraphs.*

# The Particle Physics Data Grid 

##  Concept of the Proposal

To be written

##  Background and Accomplishments: the Collaboratory Pilot

###  {#section .unnumbered}

### 

During the past three years the collaboratory has continued to make
significant progress in the actual use of grid technologies in the
production data processing systems of the participating experiments . We
have seen an across the board increase in the use of the standard common
grid technologies. During the current (third SciDAC) year of the
collaboratory we have increased our focus and commitment to joint
projects and started the transition to a service based grid
infrastructure.

The last two years have seen a significant change towards the acceptance
of grids as a viable technology to address the experiments' distributed
computing needs. In all the experiments participating in PPDG,
developments and deployments of distributed computing and grid
technologies involve many more people than those on the "PPDG team" per
se. PPDG's dependence on external deliverables, the evolving
requirements of the experiment collaborations, the increasingly broad
responsibilities of the wide computer science groups and the need to
communicate and collaborate both nationally and internationally with
many outside projects and communities continue to challenge our ability
to manage and coordinate success in the projects deliverables and goals.
We will continue to try to rise to the challenge.

### 

### Goals and Requirements -- from Fabric to Physics 

Goal is a usable, scalable, manageable production quality grid that
meets the data analysis of the experiemnts. This grid consistes : a
collection of hardware resources which can be linked (from the users'
point of view) with a single job submission system and carry out
specific tasks for the VO; a set of software services which can be
deployed to any hardware collection which chooses to install them; and
governance, policy and agreements to cover the use and operation of the
grid. We believe that there are significant technical, financial and
sociological benefits to working together towards a common
infrastructure and a joint approach.

###  The Grid Fabric

> Build a common grid infrastruture building on existing systems of
> varying levels of capability and technology (sam, srm, rrs, grid3, vdt
> etc)

####  - extend and harden the system to be more performant and maintainable {#extend-and-harden-the-system-to-be-more-performant-and-maintainable .unnumbered}

### End-to-end Physics Application Usage of the Grid

Deploying end-to-end applications and vertically complete systems
requires us to acquire, integrate and operate the full suite of grid
services needed. The experiments on PPDG make choices for each
functional requirement from the range of available technologies --
including common grid middleware and existing services where possible,
building and/or adapting their own specific solutions when necessary. In
the first stage of PPDG many of the solutions were indeed experiment
specific or developed. The goal of PPDG both in the first stage and in
the proposed next steps building on these solutions and the maturing
standard technologies, to further the goals of standardization and
commonality.

PDDG believes that its strategy of leverage of other development
projects, its pragmatic use of available services, and its focus on the
short and near term requirements and capabiliies has proven successful
in terms of meeting experiments needs and meeting planned milestones.

End to end system management.

#### 

#### 

\-

#### 

#### Development and Deployment -- a Coordinated Approach

During the period from June 2004 to June 2006, PPDG will continue the
deployment of end-to-end distributed applications for the experiments
through the use, hardening and extension of common Grid technologies.
Complete and robust grid systems must provide standards and standardly
accessible services that are universally available and supported. PPDG
plans to continue its work towards this goal. PPDG will include a common
project to benefit all the participating groups through a coordinated
program to

Extend, deploy and support the common Grid technologies.

Extend and deploy specific needed Grid System Services for management
and operation of the Grid infrastructure.

Adapt and interface the Laboratory Facility infrastructures to a
standard Grid environment.

Establish a common Grid infrastructure to include some fraction of the
resources of the DOE Laboratory Facilities on the project.

PPDG will additionally continue, albeit with somewhat reduced scope, to
work on short to medium term deliverables for each of the participating
teams. These projects will operate, as now, through peer collaborations
between Computer Science and Experiment teams.

The common project program of work is complementary to that of other
projects with which PPDG collaborates: the DOE Science Grid includes DOE
facilities that are in the main not part of PPDG; the iVDGL project
includes NSF institutions collaborating towards a shared grid laboratory
for use by the participating experiments. The program of work is aligned
with that of the Open Science Grid strategy, which proposes a roadmap
for a national grid infrastructure federating existing laboratory and
university facilities starting with the resources for the LHC
experiments.

The common project will be directed by an expanded Executive Team,
including a full time technical manager. The effort in the common
project will be contributed from each of the existing teams, and enable
a coherent program of work of benefit across all groups on PPDG.

### AManaged Scalable System -- 1/2 page -- Harvey, John, 

###  The Grid Facility Infrastructure -- 1/2 page - Don

###  Anything but Architecture (Principles)-- 1 paragraph -- Miron

###  PPDG Common Project Program of Work -- 2/3 page

#### Grid System Management Services -- Regan, Arie, Harvey, Richard

The PPDG is developing standard services that may be used to support
organization of distributed data into collections, data access, and data
analysis. The services need to work across administrative domains,
across a wide variety of storage resources, and across project specific
name spaces for users, resources, files, and applications. Grid services
that are being created within the Global Grid Forum, create state
information that is mapped onto the appropriate name space and managed
in a catalog. The ability to execute multiple services as a data flow is
now being added to the Grid environment. Each service is represented
using either a Web Service Definition Language or an Open Grid Services
Architecture definition. By creating standard service interfaces to the
existing resources, a grid can be constructed that extends across
multiple sites. Grid service management systems build data flow
processing systems that invoke grid services. The current Grid data flow
systems apply applications to files. The next generation Grid data flow
systems will apply web services to result sets obtained by queries on
collections.

#### Facility Grid Service Interfaces -- Don

\- Interfaces to Storage services

\- Interfaces to Data movement

\- Provision of Monitoring, Policy and Resource Information

\- Access, Authorization, Auditing and Accounting Interfaces

\- Processing Service

\- Application and Software Packaging

\- Service and Resource Configuration

#### System Integration and Deployment -- Lothar

####  {#section-6 .unnumbered}

### Computer Science Program of Work -- Miron

####  

#### 

#### 

#### 

#### 

#### 

#### 

#### 

#### 

#### 

#### 

#### 

#### 

#### 

#### 

#### 

#### 

#### 

#### 

#### 

###  Experiments Program of Work 

####  High Energy Physics - 1 page

> **ATLAS -- John, Jim, Rob**
>
> from Atlas Year 3 plan**:**
>
> \- data challenges of increasing complexities.
>
> \- allow all US ATLAS physicists to run distributed analysis.
>
> \- This will require hardening and automation of many tasks.
>
> \- Resource brokering and handling have yet to be deployed at any
> level of sophistication.
>
> \- coordinate analysis efforts with other groups.
>
> **BaBar -- Richard, Adil**
>
> from BaBar Year 3 plan:

1.  

2.  Production quality. All the scripts to monitor SRB servers, check
    consistency of catalog with what is transferred, scripts to bulk
    load, automatically register new users, manage disk cache space,
    staging requests. Many of these scripts would be built on top of the
    more lower-level scripts provided by the SRB, in the cases where SRB
    applications do not exist, or the higher-level scripts are thought
    to be of more general interest, these will be integrated back into
    the SRB as part of a standard release This set of tasks should take
    approximately months to complete. . Since each project has unique
    management requirements, the ability to apply the scripts in a
    peer-to-peer federated environment will require close coordination
    with the proposed peer-to-peer federation development effort. The
    goal is a set of scripts that recognize the management policies of
    each site in the federation, while establishing metadata consistency
    between federated sites.

> \- scripts and apps to do deep-copying of selected events.
>
> \- Monitoring of transfer rates, load etc.
>
> \-

3.  Interact with RLS or maybe use the federated MCAT mainly for data
    analysis. Allow jobs to query the SRB either directly or through
    BaBar bookkeeping tools mainly for data distribution. Interaction
    with the RLS would require populating the RLS with information from
    the SRB that will permit access via the RLS to the files stored in
    the SRB. We anticipate that this task will be completed in a year.

    . The deployment of the SRB into production within BaBar will also
    permit an understanding of the web-services (grid-services) that are
    needed for data distribution. We can then work on replacing the
    various operations with OGSA compliant services. This should permit
    us to integrate with grid middleware used for data analysis. **This
    task should take a year.**

4.  

> **CMS -- Lothar, Harvey, Ruth**
>
> **CDF/D0 --** CDF and D0 have converged to using a common
> metadata/location catalog. D0 will continue its work toward a complete
> end-to-end deployment of a physics application grid which is
> performant for the experiment. CDF is interested in working
> specifically toward interactive analysis on the Grid. The SAMGrid
> project will need to incorporate VO management and authorization tools
> from the Fermilab facilities work. It will work with other groups
> toward common job submission and request tools. Both experiments
> intend to contribute to moving SAMGrid toward a more services-oriented
> set of components using interfaces as agreed with the common grid
> infrastructure project.

[]{#__RefHeading___Toc59292469 .anchor}Nuclear Physics -- Doug, Jerome

[]{#__RefHeading___Toc59292470 .anchor}Laboratory Facility Program of
Work -- TBD

#### 

#### 

#### 

#### 

#### 

#### Convergence and Stability -- QA, metrics, testing-- Ruth

#### 

#### 

#### 

#### Deliverables and Milestones 

#### Phase 0 --PPDG Year 3 -- 1/2 page

#### Phase I 12 months (June2004-2005) -- 1/2 page

#### Phase II 12 months (June 2005-2006) -- 1/2 page

###  

### Partnerships and Coordination (1/2 page)

### 

###  PPDG Management Plan (1/2 page)

### Outreach and Education (1 paragraph)

### Budget summary and justification (1 paragraph)

## Subcontract or Consortium Arrangements

# Literature Cited