Long Term Ecological ResearchNetwork Information System

LTER Grid Pilot Study

LTER Information Manager’s Meeting

Montreal, Canada4-7 August 2005

Mark Servilla (LNO)

Pilot Study Goals

• Demonstrate the vision of the LTER Grid to the LTER community

• Demonstrate how grid and middleware technologies can be applied to enhance collaboration and sharing within and external to the LTER community

• Demonstrate an effective working relationship with the LTER Network office, NCSA, ISI, and GRIDS Center staff

• Demonstrate the potential of super computers for LTER science

• Collect requirements for a detailed design of the LTER Grid

Strategies

• Contrived scientific experiment• Short duration (6-month) end

milestone• Demonstration of final product• Directly involve stake-holders• Identify key and usable Grid

infrastructure

LTER Grid Pilot Study

• LTER Network Office– University of New Mexico

• NCSA– University of Illinois at Urbana-Champaign

• ISI– University of Southern California

• KBS LTER (Dr. Stuart Gage)– Michigan State University

• SEEK– NCEAS at the University of California, Santa

Barbara

LTER Requirements

• LTER Portal/Single Sign-on• Security

– Authentication– Access Control

• Audit Logging– Data Access

• Intellectual Rights Protection• Data Use Policy

– Resource Access

• High Performance Computing Resources• Data Storage Resources• Collaboration Tools

Pilot Study Experiment“Acoustic Pattern Matching”

• Environmental Acoustic Monitoring– Embedded

microphone– Sampling every

30 minutes for 30 seconds

– Conversion to *.wav file format

Pilot Study Experiment“Acoustic Pattern Matching”

• Ornithologic (bird) pattern matching– DSP/Matlab

workbench– Match unknown

dataset to an known signature

User Scenario

• User logs onto portal (single sign-on)

• Selects known signature file(s)

• Performs data search via Metacat for unknown acoustic file(s)

• Performs acoustic matching on HPC; match probability identified to user

Architectural Components

• Web application - noname (J2EE using struts and jglobus)

• Certificate Management – MyProxy/LDAP (now being used by TeraGrid)

• Data Transfer - GridFTP• Job Management - GRAM (pre-WS)• GSI Authentication – Metacat GT4 Container• Metadata Database - Metacat 1.5 modified for

GSI (Java servlet)• Data Discovery - Metacat Query Inteface (Java

servlet using struts framework)• DSP Analysis - Matlab

Infrastructure Scenario

1. Portal accepts user credentials and passes to MyProxy

2. MyProxy validates thru LDAP and issues certificate back to Portal

3. Portal accepts acoustic signature selection by user

4. Portal accepts acoustic query; passes query and certificate to GT4/Metacat; request logged

5. Metacat returns query results to Portal; return logged

6. Portal accepts selection of unknowns by user; passes certificate and data transfer request to data POP and HPC

7. POP and HPC accepts certificate; POP, via GridFTP, transfers data to HPC

8. HPC performs matching; returns results back to Portal

213

45

6

7

8

Current Status

• March 2005– Generate detailed work-flow

and application(s) specified– Generate detailed project plan– Identify components, services,

and APIs– Identify roles and

responsibilities– Generate detailed

architecture– Identify site, personnel, and

data involved– Team meeting at NCSA

• April 2005– System and User

Environment configuration– Software/hardware

development and integration

• June 2005– Software/hardware development

and integration

• July 2005– Release of functioning prototype– Prototype testing and evaluation– Site deployment of

software/hardware– Site integration of

software/hardware– Site testing and evaluation

• August 2005– Release of working system– System testing and evaluation– Preparation of demonstration

• September 2005– Demonstration