OGF eScience Function

Geoffrey Fo

November 13 2006

Science Function

Charter:Work with scientific, engineering and education researchers, developers and users to enable discovery, collaboration, education/training in an interoperable

Grid/cyber-infrastructure environment Grid Technology Research Major Grid Projects Applications & Users

Area Name Area Focus What the Area Delivers

Structured workshops and a major annual conference on a variety of grid and distributed computing related technologies. Strict refereeing

Document (s): NEWORG documents including a refereeing process and publication for NEWORG Individual documents and special issues Science based web site; community tools

Research into next generation Grid/CI

and distributed computing technologies

Workshops: Structured workshops between major grid projects around the world to discuss best practices, interoperation, requirements, issues and priorities

Exhibits, Interoperability, best practice forums, software user groups Document: Ongoing development of the “Document” to align NEWORG standards roadmap with major grid projects priorities and directions Align with other Science functions

Enhancing functionality and interoperability of

Grid/cyber-infrastructure among

the major grid projects around the

world

Web and Program content, demonstrations, and outreach delivered primarily via NEWORG and partner events, NEWORG website and special outreach programs. Define requirements interacting with other GGF functions

Promote development of domain specific best practice and standards. Lead enhancement of

science and engineering by use of

eScience Activities from OGF18

• Group activities such as those in GIN (Interoperability)

• Note two new groups in Education and Reliability

• Groups perform long term activities in focused areas

• This activity typically does not get much high level visibility except for GIN

• Timely activities arranged in the three months before meeting

and including panels, tutorials and short workshops

• Current submissions to community program

• Long lead time single track workshops with invited and

contributed presentations in topics of broad interest to OGF. These refereed (or otherwise high quality) activities are

documented with reviews contributing to OGF Best Practice series. Individual talks appear on OGF web site and in

Journal Special Issues

Possible workshop topics suggested at

OGF18

• Federated Identity ************** OGF19

• Data management/virtualization

• SRB VOSpace

• Web 2.0 ********************* OGF19

• Amazon

• Utility Computing

• JSDL for eScience

• Virtual machines

• On demand Grids

• Interoperable Workflow for eScience

• Using portal technology for eScience

• Service Discovery for eScience

• Semantic Grid

• Autonomic Grids

• Firewalls

• VO and Collaboration tools

• Incentives for eScience Resource provisioning

Next and Current Steps

• Chapel Hill OGF19 (Blatecky General and PC Chair)

• Federated Identity Satoshi/Ken

• Web 2.0 and Grids Dave/Geoffrey

• Manchester OGF20 (Gentzsch General Chair, Berry PC

Chair)

• Community Resource Aggregation as National and Campus Grids

• Data Management

• EuroGIN

• Commercial Web 2.0 (Catlett)

• Meeting here at SC not Amsterdam

• No telecons

• Modestly responded emails (optimize with pure eScience email list but no change – response still low)

Proposed Group Actions

•

Close

GB (Grid Benchmarking), GGF-PROC

(GGF Process), ACE (Collaboration), APPAGG

(Appliance Aggregation), UPDT (Tools)

•

Approve

BTC (Build Test Certification) with

added participation (Wisconsin, OMII)

•

PGS

(Production Grid Services) notes many

workshops overlap their charter

eScience VP/AD’s

• Major role of eScience VP/AD’s seems to be leading projects

such as supporting events and organizing new activities like users groups

• PC Chairs are obvious projects but modest time scale (1 year)

• Note “reviews/summaries” produced by one-day workshops

viewed as helping to snapshot current Grid status (so-called BKM or Best Known Methods) for Enterprise – these need leadership as well

• Maybe VP/AD’s have a role in GFSG but easier to make

progress in limited area?

• Such as Interaction on TSC – Technical Strategy Committee

• Participation in (weekly) Management meetings

• Encouraging interaction with other functions

• Note core OGF community is 50 commercial and 100

research/education/government (latter include standards)

Lightweight eScience I

• eScience could be more effective in a lightweight cheaper

organization where easier to get critical things like mobilize PC done

• Needs a co-ordinator and a deputy (aka VP and an AD or two)

to act as corporate memory

• Email or Wiki or similar between these two/three people internally and externally to OGF must be effective

• How do we identify project leaders – from the world or from AD pool

• Does need continued web site improvement (it is much better)

and better records of telecon

• Telecons should have “key people” identified, crisp minutes posted quickly, and their opinions pro-actively solicited if they miss a telecon

• Does need a MUCH larger advisory board to draw workshop

Lightweight eScience II

•

Propose declaring current VP/AD’s and

vaguely alive group chairs as eScience

advisory board

•

Propose adding other names after discussion

•

Is there any downside in large advisory board?

•

Propose asking Nomcom to suggest new VP

and two new AD’s (deputies) giving special

consideration to those with May 2008

termination dates

People and Terms

• Allesandrini(*?)

• Blatecky

• Catlett(*)

• De Roure

• Fox

• Gentzsch(*)

• Klingenstein

• Matsuoka

• Gannon

• Jin

• Kielmann

• Plale

}

extension requested for fall 2007 * = wish to leave May 2007

}

NOMCOM Action Items

•

Need to define characteristics and number of new

VP and AD’s

• Previously easier as aimed at “2 per area” although this

seems definitely “wrong”

• Could for example ask for interest/expertise in

interoperability or in being conference chair

•

Suggest possible candidates to NOMCOM

OGF19 eScience Status

• Can we really organize the two one day workshops?

• If so – need help in identifying participants • Current Proposals for Community Program:

• GIN-I: GIN and the HPC profile

• GIN-II: GIN feedback to standards

• Second Workshop on Reliability and Robustness in Grid Computing Systems

• Introduce: Graphical Creation of Globus Based Grid Services

• The Application Service Grid -- SOA meets Grid Computing • Transactional Grids

• Secure Replication of Data in the Grid

• GRADIENT- Grid based Enterprise Data Integration Framework • How to use benchmarks when evaluating new servers

• Traditional Community Activities

• Tutorial of specialized material (my project)

Other Issues

•

What should we do if OGF19 shows modest

number of proposals and organizers worry about

two workshops

• We don’t have much time

•

OGF20 launched early and seems in good shape

•

Lets launch OGF21 program planning NOW

•

Low priority topics

• OGF@other meetings doesn’t seem to help OGF much

• Write proposals involving OGF – Education and