Globus and PPDG

1
Globus and PPDG

• Jennifer Schopf, for the Globus Project
• PPDG All Hands 10th June 2003, BNL

2
Globus Work on PPDG

• Jennifer Schopf, ANL
• Main PPDG contact for Globus, also monitoring
• Ian Foster, ANL
• High-level architecture and support, PPDG SG
• Bill Allcock, ANL
• GridFTP
• Ann Chervenak, ISI
• Replica Location Service
• Stu Martin, ANL
• GRAM architect, contact for CMS testbed summer to
  Fall 2002
• Von Welch, ANL
• Security (SiteAAA, CAS, VOMS)
• And many others of the Globus Team not explicitly
  listed

3
Summary of Accomplishments, Deliverables and
Milestones

• Coordination
• GT2
• GT3
• SiteAAA/VOMS/CAS
• GridFTP/RFT
• Monitoring
• Replica Location Service

4
Coordination

• Accomplishments
• Email lists and some phone meetings for Atlas and
  CMS
• Email lists of D0
• Support for the Argonne-Chicago ATLAS team in
  their efforts to perform "data challenge on
  demand" event generation using VDT, RSL, and
  Chimera.
• Support through the discuss lists and Bugzilla
  are available to all experiments.
• Deliverables/Milestones
• Support will continue

5
GT2

• Recent Accomplishments
• Release of version 2.4 includes fixes for over
  55 bugs!
• Closed 9 bugs listed in Bugzilla (256, 542, 596,
  625, 713, 722, 741, 745, 823)
• Only 5 open PPDG-related bugs still open in our
  system (53, 260, 347, 398, 872)
• Deliverables/Milestones
• Bugzilla bugs will continue to be answered, but
  few additional code changes will be implemented
  on the 2.x code base.

6
GT3

• Accomplishments
• GT3 beta release 6/6/03
• Deliverables/Milestones
• GT3 Final release planned for June 30, 2003
• Need feedback from the experiments to better
  understand the needs, requirements, and
  timelines, for use of the GT3.x code base

7
VOMS/CAS comparison

• Both architecturally similar
• Issues assertions to user which are presented to
  resource to acquire rights from resource
• VOMS issues group/role assertions
• These are presented to a resource which
  interprets those memberships to rights (policy is
  effectively distributed)
• CAS issues rights directly
• Requires no policy interpretation by resource
• We feel the finer granularity of CAS is important
  when policy maybe very dynamic or number of sites
  is large, causing the maintaining of consistent,
  distributed policy to be difficult

8
VOMS/CAS Comparison
9
SiteAAA/VOMS/CASAccomplishments

• Delivered alpha version of modified Globus Tool
  security libraries that allow for callout to
  local or VO authorization services to replace or
  augment normal Globus Toolkit authorization
• Callout designed with PPDG-SiteAAA WG
• Allows development of a callout to support VOMS
  group membership assertions in CMS as required by
  that group
• Work with Doug Olson and Craig Tull to use CAS as
  a VO group server
• Results were presented at CHEP03

10
SiteAAA/VOMS/CASDeliverables

• Use VOMS/CMS experience as baseline for
  implementation of similar functionality in GT3
• Determine any issues in design - e.g., are we
  missing information in callout needed for
  authorization
• Awaiting feedback from CMS community on how their
  VOMS integration goes
• Integration of CAS as a production service along
  with a CAS-enabled GridFTP server in the main
  Globus Toolkit release. It is unclear at this
  time if this work will appear in GT3.0 or the
  subsequent release.

11
GridFTP/RFTAccomplishments

• Focus on GridFTP stability and scalability
• Re-implementation of Globus GridFTP Server
• Improve stability, maintainability, ease of
  addition of features
• Licensing issue with wuftpd code
• Design and coding of XIO mainly completed
• Resolve the hanging issues with globus-url-copy
  (bug 256)
• Design the framework, TCP, file and GSI drivers
• Server design is well underway, and coding has
  begun

12
GridFTP/RFT Deliverables and Milestones

• Beta release of the new server as part of the
  GT3.2 Beta (late August, 2003)
• Guaranteed features are data transport and
  security
• Additional features will be released in November
• Striping for sure, but no other features are
  guaranteed
• Deliver a version of GridFTP for HPSS (using new
  server) with HPSS 5.2b release in late Q1 or
  early Q2 of 2004
• A better evaluation from the experiments is
  needed
• Users to evaluate the new code are needed
• Use of RFT by the PPDG experiments needs to be
  evaluated

13
Monitoring Accomplishments

• Several information providers (in addition to the
  standard set) are now available from the Grid
  Technology Repository (http//gtr.globus.org)
• Software path and version data, GridFTP server
  status, CAs accepted, and some service data.
• GLUE schema work
• Licensing issues resolved 2 weeks ago
• Compute Element (CE) schema is currently being
  used in the EDG
• Storage Element (SE) schema discussed in detail,
  moving forward
• The Network Element (NE) schema has begun to be
  addressed
• Joint with DataTag, UK EDG, GGF NM-WG
• Scalability analysis of MDS 2, RGMA, and Hawkeye
• http//people.cs.uchicago.edu/hai/hpdcv25.doc

14
Monitoring Deliverables/Milestones

• Plans for MDS 3, an OGSI-compliant set of
  services, are continuing as well
• Need input on data requirements from experiments
• Discussions with iVDGL and DOE Science Grid for
  suggested MDS-2 deployments in those projects
• GLUE- schema is ongoing
• Further effort is needed to prevent YAMS
  (yet-another-monitoring-system)

15
RLS Accomplishments

• Developed jointly with EDG WP2
• distributed service for maintaining mappings from
  logical to target names of replicas
• Used within the BaBar experiment at SC02
• Significant functionality and performance testing
  (gt1yr)
• Consists of a high-performance server front end,
  a relational database back-end (Postgres and
  mySQL available), and C, Java and command-line
  clients
• Other current deployments include the earth
  System Grid, GriPhyN LIGO, Globus Chimera and
  Pegasus, and IBM
• Part of the GT 3.0 beta release (last week)

16
RLS Deliverables/Milestones

• Need clarification of RLS (ISI) funding
• Will be implementing RLS as OGSA Services
• Ultimate goal refactor/redesign RLS to reflect
  continuing OGSA development
• Treat datasets as first-class OGSI-compliant
  services
• Take advantage of OGSA mechanisms for building
  efficient Grid service indexes
• Possibly treat equivalence sets of replicas as
  services
• Implement using OGSA ServiceGroups
• OGSA Data Replication Services Working Group
• Approved by GGF in May 2003
• Working group its purpose is to produce
  specification standards
• Group includes participants from IBM, Gridlab,
  EDG, Japan AIST, Yotta Yotta, others

17
PPDG Top 3 (plus) wishes

• More feedback on young code from experiments
• Active engagement from PPDG in deployment and use
• VOMS, RLS, etc.
• More information on use cases and usage patterns,
  esp. large file transfer behavior (data movement
  characteristics)
• Greater cooperation and integration of efforts
• Esp. for replication, monitoring, VOMS
• Additional requirements (if any) from PPDG for
  replica location services, GridFTP development,
  Information Providers, VOMS, CAS, etc.

18
Support

• In addition to PPDG, this work is partially
  supported by the DOE SciDAC Security and Policy
  for Group Collaboration and the DOE Science Grid
  projects, as well as from the Mathematical,
  Information, and Computational Sciences Division
  subprogram of the Office of Advanced Scientific
  Computing Research, Office of Science, U.S.
  Department of Energy, under contract
  W-31-109-Eng-38.