OGF eScience Function

Geoffrey Fox

OGF21 Seattl

October 17 2007

2

Four major types of eScience Activities

• Group activities such as those in GIN (Interoperability)

• Groups perform long term activities in focused areas

• Typically does not get much high level visibility except for GIN

• Newish groups in Education, Reliability, Instrumentation

• Typically one or more distinct 90 minute sessions

• Timely community activities arranged in the two-five months before meeting and including panels, tutorials and short

workshops

• Current submissions to community program

• Typically one or two 90 minute sessions per submission

• Long lead time single track workshops with invited and

contributed presentations in topics of broad interest to OGF.

• Typically 4 or 5 90 minute sessions

• Software Provider Track started at OGF19

Research and Community Groups

• Build, Test and Certification of Grid Software Community Group (btc-cg)

• Education and Training (et-cg)

• Grid Reliability and Robustness RG (gridrel-rg) • Certificate Authority Operations RG (caops-wg)

• Grid Interoperation Now Community Group (gin-cg) • Production Grid Services-RG (pgs-rg)

• Remote Instrumentation Services in Grid Environment - RG (risge-rg)

• Applications Developers and Users RG (apps-rg) • Astronomy Applications RG (astro-rg)

• Humanities, Arts, and Social Sciences RG (hass-rg) • Life Sciences Grid RG (lsg-rg)

• Particle and Nuclear Physics Applications RG (pnpa-rg) • Preservation Environments RG (pe-rg)

• Semantic Grid RG (sem-rg)

eScience Council Leadership

• Vice-President:

• Geoffrey Fox • Active AD’s:

• David De Roure

• Thilo Kielmann • Inactive/retired AD’s:

• Victor Allesandrini

• Alan Blatecky

• Charlie Catlett

• Dennis Gannon

• Wolfgang Gentzsch

• Hai Jin

• Ken Klingenstein

• Satoshi Matsuoka

• Beth Plale

Total attendance at OGF Meetings

Research and Educatio

Attendance at OGF Meetings

Commercia

Attendance at OGF Meetings

Community Program

• Community oriented activities with relatively light weight approval process with call 3-5 months before meeting and decisions 2-3 months before

• Joint between Enterprise and eScience

• Exploratory (Birds of a Feather) sessions that could leads to groups or full one-day workshops

• Tutorials but not well done in OGF as no easy thoughtful

coordination and don’t easily attract Grid users (as opposed to Grid builders)

• Need to establish a track with a uniform audience like we have for software development

• Small workshops often led by groups such as OGF21

GridNet2 eScience workshop ₉ Grid SubsystemsGrid Services Users

Software Development Sessions

• Grids are built from services which hopefully respect standards

• However there are several building blocks or subsystems like Globus or SRB which are used in many Grid projects

• TeraGrid EGEE Geon LEAD MyGrid China National Grid Naregi are Grid Projects

• Form initially at least de facto standards

• What is OGSA in the “non Green Field” of existing subsystems?

• OGF will offer “user group” sessions in “Grid Subsystems” in a set of

consecutive sessions aimed at those building Grids and not at people using Grids

• OGF can provide one-stop shopping so don’t need to attend XYZweek for all XYZ

• GIN-Standards-Software

vendors Interaction at OGF21?₁₀ Grid Services Grid Subsystems

Users

OGF19 Software Development Track

• Clarens Grid Portal Toolkit • Condor Scheduling system

• Genesis II OGSA Grid Infrastructure • Globus core Grid Infrastructure

• Grid Federated Identity (GridShib, GAARDS, MyProxy) • GridSphere portlet container for portals

• Ninf-G core Grid RPC Infrastructure

• NWS and BQP Network/Queuing Tools

• OGCE Open Grid Computing Environments collection of portlets (for Science Gateways)

• OMII core Grid infrastructure (includes OGSA-DAI and Taverna) • SRB data Grid infrastructure

• Unicore core Grid infrastructure

OGF21 Software Providers Track

• Univa Driving Grid Adoption With Industrial-Strength Open-Source Solutions

• Microsoft What can Microsoft products do for you? (Steven Newhouse & Savas Parastatidis)

• Oracle Achieving transparency in operating and managing the Grid

• Globus and Community for OGF (4 Sessions) • caGrid 1.0 (Infrastructure for NIH Cancer Grid) • SAGA Grid-aware Application Interface

• OGSA-DAI OGF compatible Grid Database

• OMII-UK Reducing the gap between researchers and resources (2 Sessions)

• OMII Europe Interoperation and Interface

• Introduce Graphical Grid Service Authoring Toolkit

• GIN Grid Interoperability Group meets Software Providers wrap-up Panel

13

Recent

Workshop Topics

• Federated Identity at OGF19 organized by Ken Klingenstein and Satoshi Matsuoka

• Semantic Web 2.0 at OGF19 organized by Dave De Roure

• Resource Aggregation Grids at OGF20 organized by Wolfgang Gentzsch

• Web 2.0 at OGF21 organized by Geoffrey Fox and Dave De Roure

• Probably will not have a workshop at OGF22 but rather support a data

workshop led by Standards function

• OGF23 Earth Science and OGF24 eScience for “non-heroes” (mortals)

• Preferred organization of one –day workshops

• Invited and Contributed Talks

• Panel aimed at summarizing topic as relevant to Grids or Grid technology

• After meeting one could

• Post presentations

• Convert panel discussion into a “review” “synopsis” or “Best Practice” for area covered

Future eScience Function Strategy

•

Grids and even eScience are quite mature (OGF21

implies 7 years at 3 meetings a year)

•

eScience and Grids are substantially

better funded

in

Europe

than USA and perhaps Asia

•

Support

mature field

by stressing Software provider

sessions describing software used/useable by

Grid/eScience developers

• especially OGF22 in USA

• Add more commercial suppliers

• Ask NSF to bring the grantees of their software hardening solicitations

•

Support

future of OGF

by initiatives in areas where

Emerging Trends for OGF eScience

• Gartner IT Highlights

• Computing fabric

• Unified communications

• Business process modeling

• Green IT

• Metadata management

• Virtualization 2.0

• Mashup and composite apps

• Web platform and WOA

• Real World Web

• Social software

• OGF eScience Initiatives

• Autonomics

• Data centric Science

• Virtualization

• Workflow

• Web 2.0

• Manycore (simpler MPI, Graphics, CCR) Programming Environments and Interfaces

}

Mapping to Research and Community Groups

• General

• Build, Test and Certification of Grid Software Community Group (btc-cg)

• Education and Training (et-cg)

• Certificate Authority Operations RG (caops-wg)

• Grid Interoperation Now Community Group (gin-cg)

• Production Grid Services-RG (pgs-rg) (Campus Grids)

• Autonomics

• Grid Reliability and Robustness RG (gridrel-rg)

• Data-centric Science

• Preservation Environments RG (pe-rg)

• Remote Instrumentation Services in Grid Environment - RG (risge-rg)

• Applications Developers and Users RG (apps-rg)

• Astronomy Applications RG (astro-rg)

• Humanities, Arts, and Social Sciences RG (hass-rg)

• Life Sciences Grid RG (lsg-rg)

• Particle and Nuclear Physics Applications RG (pnpa-rg)

• Several relevant standards groups

• Web 2.0

• Semantic Grid RG (sem-rg) and (hass-rg) again

• Workflow

• Workflow Management RG (wfm-rg) and (sem-rg) again for mashups

• Virtualization: Grid and Virtualization WG in standards

Actions and Issues

• Will try to add more active AD’s through Nomcom process

• Who should we tap?

• How best to enhance software developer activities?

• How to reach out to natural communities?

• e.g. High Performance Computing (MPI natural)

• Any other communities we should address?

• Offer workshops in Green areas (Workflow, MPI-NT) and offer tutorials in orange and red areas (Web 2.0,

Virtualization, Autonomics)?

• What should we do for data-centric science?

• Are there other areas?

• How to re-invigorate groups such as Life Sciences?

• Community program healthier than groups (GIN very healthy)

• How to cope with Attendance continent effect