Paul Avery

Ian Foster

Dec. 7, 2001

Version 5

[]{#__RefHeading___Toc532375859 .anchor}Initial US-iVDGL Organization
Plan

[Initial US-iVDGL Organization Plan 1](#__RefHeading___Toc532375859)

[1 Introduction 1](#introduction)

[2 Management 1](#management)

[2.1 Management description 2](#management-description)

[2.2 Relationship to international iVDGL
2](#__RefHeading___Toc532375863)

[3 US-IVDGL Work Teams 3](#__RefHeading___Toc532375864)

[3.1 Facilities work team 3](#facilities-work-team)

[3.2 Laboratory operations work team
3](#laboratory-operations-work-team)

[3.3 Applications work team 4](#applications-work-team)

[3.4 Education/Outreach work team 5](#educationoutreach-work-team)

[4 Personnel Assignments 5](#personnel-assignments)

[4.1 Management Definition Group 5](#management-definition-group)

[4.2 Facilities team 6](#facilities-team)

[4.3 Laboratory operation team 6](#laboratory-operation-team)

[4.4 Applications team 6](#applications-team)

[4.5 Education / Outreach team 7](#education-outreach-team)

[4.6 Unassigned personnel 7](#unassigned-personnel)

# Introduction

This document describes the initial organization, with abbreviated task
lists, of the U.S. part of the International Virtual Data Grid
Laboratory (iVDGL). IVDGL is expected to be an international laboratory
for the development and testing of virtual data grid middleware, in
association with a number of experimental projects in physics and other
disciplines. The U.S. part of iVDGL (US-iVDGL) is funded by an award
from the 2001 NSF ITR program. The full international laboratory will be
built on resources from US-iVDGL and a number of international partners,
as outlined in the iVDGL proposal to NSF.

To bring up the US-iVDGL effort in the first few months, we have decided
to organize our efforts into broad areas, represented by the following
work teams: (1) Facilities, (2) Laboratory Operations, (3) Applications
and (4) Education/Outreach. These are outlined below.

# Management

The US-iVDGL management structure was defined in the proposal to be
integrated with that of GriPhyN. After some discussion, however, we now
consider US-iVDGL to be a joint GriPhyN--PPDG project. Accordingly, we
should have a management structure that has representation from both
projects. The map below shows the organization of US-iVDGL (as defined
in the proposal) and its connections to GriPhyN. However, some changes
might need to be made in light of subsequent discussions about
management structure.

US-iVDGL Interim Management Chart

## Management description

We have discussed having two separate management groups in previous
meetings:

-   The Project Steering Group has senior people from the NSF proposal.
    This group advises the Directors on important Project decisions. The
    exact number and identification of members still needs to be
    determined, but should include the Project Directors, Project
    Coordinator and representatives from the experiments, Computer
    Science and Education/Outreach.

-   The Project Coordination Group is larger than the Steering Group and
    includes representatives from some of our other partners (TeraGrid,
    EU, etc.). The exact composition of this group needs to be
    determined. This group must have some representation outside the
    original NSF proposal participants in order to coordinate
    effectively with our partners, including TeraGrid, the LHC computing
    project and DataTAG.

## Relationship to international iVDGL

The international iVDGL will be organized as a joint effort of US-iVDGL
and a number of international partners. US-iVDGL will, on its own,
support and organize a testbed laboratory within the U.S. to test and
integrate the grid middleware of the GriPhyN and PPDG projects. This
effort will be extended through International iVDGL to an international
testbed with transoceanic links devoted to testing and integrating the
grid middleware of many data grid projects, including at least DataGrid
and its associated national projects, DataTAG, GridPP, and Japanese data
grid efforts, in addition to the U.S.-based work of GriPhyN, PPDG,
US-iVDGL, and DTF. A significant difference of organization comes from
the multiple funding sources of International iVDGL. A different
structure will be developed that recognizes the collaboration of several
projects that are funded and managed separately.

# US-IVDGL Work Teams

## Facilities work team

The facilities team carries out the following activities:

-   Identification of testbed sites. These sites include not only the
    ones described in the proposal, but additional ones from the "core
    experiments" (ATLAS, CMS, LIGO, SDSS, NVO) as well as those from
    other experiments such as ALICE, CMS Heavy Ion, D0, BTEV, etc.

-   Hardware procurements. We must acquire hardware for the Tier2 and
    Tier3 sites, including CPUs, RAID arrays, data servers, network
    switches, and other specialized equipment.

-   Software suites and toolkits. Software includes Grid toolkits (e.g.,
    Globus, VDT 1.0), schedulers (e.g., Condor), operating systems, and
    experiment specific application software. \[*PA & Huth: should this
    appear here or in applications?* *It can be argued either way.*\]

Specific tasks include:

-   Define and document criteria for becoming a site.

-   Create the MOUs for the different kinds of sites (Tier1, Tier2
    funded & unfunded, Tier3 funded & unfunded). \[*Question: Should the
    MOUs be done by this group?*\]

-   Collect written descriptions of each site\'s hardware configuration.

-   Research and document the number and kinds of clusters at each site.
    For example, one could imagine a "stable" cluster and a
    "development" cluster, each carrying out well-defined functions.

-   Research and document what configurations are "compatible" with a
    shared iVDGL.

-   Identify and document hardware components, technologies and vendors.

-   Test hardware configurations as needed.

-   Create a schedule for hardware acquisitions.

-   Identify and document what software suites, including versions, need
    to be common across all the sites (including Tier1,2,3).

-   Test to make sure that the software works.

-   Create a work team list including name, institution, e-mail and
    phone number.

-   Create a web page for all the above information

## Laboratory operations work team

The operations work team carries out the following activities:

-   Implemention and operation of the GOC

-   Performance monitoring

-   Networking

-   CS software support and development \[should this be two tasks?\]

-   Coordination of US-iVDGL sites

-   Security and authorization infrastructure

-   Liaison support for Virtual Organizations participating within
    US-iVDGL

Specific tasks include:

-   Document the scope and responsibilities of the GOC, at least for the
    early stages.

-   Document the range and scope of initial software support and
    robustification.

-   Develop, document and implement initial performance monitoring.

-   Develop, in common with the application team, relationships with our
    international colleagues.

-   Develop and document how the iVDGL will exploit national,
    international and research networks over time.

-   Create a work team list including name, institution, e-mail and
    phone number.

-   Create a list of site contacts, including name, institution, e-mail
    and phone number.

-   Create a web page for all the above information

## Applications work team

The applications work team carries out the following activities:

-   Identification of application groups

-   Planning the needs of the applications, including Grid software
    integration

-   Testbed development

Specific tasks include:

-   Identify and document the various applications groups participating
    in US-iVDGL. These include the ATLAS, CMS, LIGO, SDSS, NVO, plus
    other experiments such as D0, BTEV, ALICE and CMS HI. We also need
    to include biology as a user group, but this needs to be developed.

-   Outline in document form a plan for Grid software integration for
    each experiment for the next few months, recognizing that the
    particular needs differ by experiment.

-   Create a list of the application participants, including name,
    institution, phone and e-mail. For each application taking part,
    identify the contact person.

-   Develop and document a plan for inter-site tests for the first 6
    months. This needs to be done jointly with the operations team.

-   Create a work team list including name, institution, e-mail and
    phone number.

-   Create a web page for all the above information

## Education/Outreach work team

This team is responsible for developing various education/outreach
activities for US-iVDGL. The E/O work team carries out the following
activities:

-   Developing the research capabilities of the Minority Serving
    Institutions.

-   Developing undergraduate and graduate courses related to distributed
    and Grid computing.

-   Creating and maintaining a high-quality web page for E/O activities

Specific tasks include

-   Create a work team list including name, institution, e-mail and
    phone number.

-   Develop and document a plan for E/O activities for six months. This
    plan is not expected to be complete, but it should build on
    GriPhyN's E/O program.

-   Create a web page for all the above information

# Personnel Assignments

These personnel assignments are meant to cover the initial six month
startup of US-iVDGL. The co-leads are responsible for organizing
meetings, making sure that tasks are completed on schedule and reporting
to the Project Directors.

To get started, we have assigned people to the various groups below, but
these assignments can change depending on preferences. *Remember that
these groups are temporary and might be phased out after a few months*,
depending on future needs.

The goal is to assign *everyone* in the Project to a team to facilitate
sharing responsibilities, including document writing and web page
development.

## Management Definition Group

The Management Definition Group will help the Directors create the new
management structure, identify responsibilities, start the hiring
process, and assist the Directors in choosing participants. This group
is expected to have a very short lifetime, probably lasting until the
end of January o r perhaps February.

**Co-leads**

Ruth Pordes ruth@fnal.gov

Larry Price lprice@anl.gov

**Members**

John Huth huth@physics.harvard.edu

Lothar Bauerdick bauerdick@fnal.gov

Harvey Newman newman@hep.caltech.edu

Alex Szalay szalay@jhu.edu

Albert Lazzarini lazz@ligo.caltech.edu

Carl Kesselman carl@isi.edu

Miron Livny miron@cs.wisc.edu

Richard Mount richard.mount@slac.stanford.edu

Manuela Campanelli manuela@aei-potsdam.mpg.de

Mathias Kasemann matthias.kasemann@cern.ch

Les Robertson les.robertson@cern.ch

## Facilities team

**Co-leads**

Ian Fisk ifisk@ucsd.edu

Bruce Allen ballen@gravity.phys.uwm.edu

**Members**

Jorge Rodriguez jorge@phys.ufl.edu\
Ric h Baker baker@bnl.gov

Ed May may@anl.gov

Rob Gardner rwg@indiana.edu

Saul Youssef youssef@bu.edu

Jenny Schopf jms@mcs.anl.gov

Vivian O\'Dell odell@fnal.gov

Jim Shank shank@bu.edu

Julian Bunn julian@cacr.caltech.edu

Suresh Singh Caltech????

Alan Wiseman agw@gravity.phys.uwm.edu

Chris Griffin cgriffin@ufl.edu

Holger Stoeck holger@phys.ufl.edu

Jim Williams william@indiana.edu

## Laboratory operation team

**Co-leads**

Jim Williams william@indiana.edu

Carl Kesselman carl@isi.edu

**Members**

Mike Wilde wilde@mcs.anl.gov

Jenny Schopf jms@mcs.anl.gov

Dave Pokorney dp@nerdc.ufl.edu

Harvey Newman newman@hep.caltech.edu

Sylvain Ravot sylvain.ravot@cern.ch

Valerie Taylor taylor@eve.nwu.edu

Rick Cavanaugh cavanaug@phys.ufl.edu

## Applications team

**Co-leads**

Sam Finn LSFinn@psu.edu

Scott Koranda skoranda@ uwm.edu

**Members**

Rob Gardner rwg@indiana.edu

Lothar Bauerdick bauerdick@fnal.gov

John Huth huth@physics.harvard.edu

Albert Lazzarini lazz@ligo.caltech.edu

Bruce Allen ballen@gravity.phys.uwm.edu

Alan Wiseman agw@gravity.phys.uwm.edu

Patrick Brady patrick@gravity.phys.uwm.edu

Alex Szalay szalay@jhu.edu

Steve Kent skent@fnal.gov

James Annis annis@fnal.gov

Conrad Steenberg conrad@cithep.caltech.edu

Koen Holtman koen@hep.caltech.edu

Edwin Soedarmadji edwnchen@hurl.ugcs.caltech.edu

Jorge Rodriguez jorge@phys.ufl.edu

Dimitri Bourilkov bourilkov@phys.ufl.edu

Rick Cavanaugh cavanaug@phys.ufl.edu

Haifeng Pi haifen@phys.ufl.edu

Pablo Yepes yepes@rice.edu

Paul Sheldon paul.sheldon@vanderbilt.edu

Federico Carminati federico.carminati@cern.ch

## Education / Outreach team

**Lead**

Manuela Campanelli manuela@aei-potsdam.mpg.de

**Members**

Keith Baker baker@jlab.org

Tim Olson Tim_Olson@skc.edu

Rick Cavanaugh cavanaug@phys.ufl.edu

## Unassigned personnel

Torre Wenaus

Reagan Moore & his group

Other CS people from Ian, Carl or Miron groups?