1 / 14

OGF eScience Function

Work with researchers and developers to foster discovery, collaboration, and education in an interoperable Grid/cyber-infrastructure environment. Activities include workshops, group projects, and proposal development.

whiteaker
Download Presentation

OGF eScience Function

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OGF eScience Function Geoffrey FoxNovember 13 2006

  2. 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 2

  3. 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 • (Other activities including development of federal proposals) 3

  4. 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 • How many (National and Domain Specific) Grids are there and do they want interoperability 4

  5. 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) • I will report this meeting at Amsterdam 5

  6. eScience Group Activities 6

  7. 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 • Encourage others knowing some will sleep on 7

  8. 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) • Need plenty of advice as to topics/speakers etc. 8

  9. 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 topics, chairs/organizers, proposals 9

  10. 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 • Only return names of those willing to be responsive and join in telecons etc. 10

  11. People and Terms } • Allesandrini(*?) • Blatecky • Catlett(*) • De Roure • Fox • Gentzsch(*) • Klingenstein • Matsuoka • Gannon • Jin • Kielmann • Plale Term ends May 2007 with extension requested for fall 2007 * = wish to leave May 2007 \ } Term ends May 2008 11

  12. 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 • All but 4 VP/AD’s “terminate” May 2007 and only 2 out of the remaining 4 show much OGF activity 12

  13. 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) • “Presentations” i.e. My project or product 13

  14. 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 Interoperability benefit from global scope of OGF 14

More Related