Dr' Harald Kornmayer

1
Dr. Harald Kornmayer Institute for Scientific
Computing Forschungszentrum Karlsruhe Germany for
the whole g-Eclipse consortium
2
An integrated, Grid enabled workbench tool
forGrid apllication users, Grid developersand
Grid operatorsbased on the Eclipse platform
3
Vision

• Many projects developed promising Grid tools
• Each project had its own portal framework
• Easy exchange of results was impossible
• User centric approaches
• ? an integrated plattform
• Grid users
• Grid operators
• Grid application developers
• Based on an industry compliant open-source tool

• Grid community
• Emerging technology
• infrastructure for e-Science

• Grid actors
• Grid users / e-Scientist
• Grid resource managers
• Grid application developers

g-Eclipse

• Eclipse community
• Based on a reliable eco system
• Very active open source community
• Big impact in and support from industry

4
Partners

• Many good tools developed in CrossGrid
• 4 partners with CrossGrid background
• 1 new academic partner
• experience in Workflows
• 1 new industrial partner
• Key player in german Eclipse community
• Tool development based on Eclipse

University of Cyprus
5
Project

• STREP
• 6 Partners
• Start 1. July 2006
• Duration 24 months
• approx. 2 M funding
• http//www.geclipse.eu
• Coordinator
• Forschungszentrum Karlsruhe, Germany
• Harald Kornmayer

6
Objectives

• Development of an integrated platform for Grid
  users, Grid developers and Grid operators using
  the Eclipse platform
• Integration of existing Grid tools from partners
  in the emerging g-Eclipse framework
• Migrating Desktop, GridBench, Grid Visualisation
  Kernel (GVK)
• Exemplary support for the widely deployed gLite
  middleware during the first project year
• selection of a second middleware in year 2
• Provision of the g-Eclipse framework for other EC
  Grid projects
• Integration support for third party developments
• Fostering an open source project within the
  Eclipse community

7
Challenges

• Abstraction of the complexity of Grid middleware
• ?Defining standard actions for Grid actors
• Simplification of access to different Grid
  resources
• ? Development of a general framework
• Integration of different Grid tools in one
  platform/eco system
• ?Design of a general architecture
• For different tools
• For different middlewares
• Third party contributions

8
Eclipse

• www.eclipse.org
• Very successful open source community
• Big impact in industry
• Architecture iswell designed
• Build for extensibility

9
Workpackages

• WP1 Architecture, Integration and Quality
  assurance
• WP2 Grid User perspective
• WP3 Grid Operators perspective
• WP4 Grid developer perspective
• WP5 Dissemination, Exploitation and Training
• WP6 Collaboration
• The reason why Im here today!
• Collaboration is crucial for us!
• WP7 Project management

10
WP1 Architecture

• WP1 Architecture, Integration and Quality
  assurance
• Leader FZK
• Architecture
• Implementation of Core plugins
• Testing and Quality
• Integration
• Interface to Eclipse foundation

11
WP2 User perspective

• WP2 Grid User perspective
• Leader PSNC
• Job submission plugin
• Data management plugin
• Comand console plugin
• Grid visualisation plugin
• Support for first industrial adopter
• Reimplement some of the MD functionalities on a
  real solid basement (? Eclipse)

12
WP3 Operator perspective

• WP3 Grid Operators perspective
• Leader UCY
• infrastructure monitoring plugin
• infrastructure configuration plugin
• benchmarking and test plugin
• VO management plugin
• Use the knowledge of GridBench and CrossGrid
  testbed group (and the good skills of
  int.eu.grid)

13
WP3 Developer perspective

• WP4 Grid Developer perspective
• Leader JKU
• Developing and debugging plugins
• Deployment plugins
• Workflow builder plugins
• Application monitoring plugins

14
WP5-7 AOB

• WP5 Dissemination, Exploitation and Training
• Leader INO
• We now the business from CrossGrid! (? or ?)
• WP6 Collaboration
• Leader JKU
• Required by the EC for all projects
• Standards, project benchmarks, repositories,
  roadmaps,
• WP7 Project management
• FZK

15
Time scheduling
16
Middleware infrastructure

• Middleware
• 1st year gLite
• 2nd year support for a WSRF compliant middleware
  (GT4, UNICORE-GS)
• Decision will be made in the first review
• Infrastructure
• g-Eclipse will not run any infrastructure
• NEEDS access to existing infrastructure
• int.eu.grid
• to continue with the excellent spirit from
  CrossGrid
• (size, ideas, experience, )
• EGEE, D-Grid,

17
Expected results impacts

• With the help of int.eu.grid and its
  infrastructure, g-Eclipse aims for
• An eco system of tools to build Grid-enabled,
  interactive graphical user interfaces
• An eco system to speed up the development and
  deployment of Grid applications
• An eco system to reduce the cost of the
  operation of Grid infrastructure resources
• Wide adoption of this integrated eco system
• g-Eclipse open source community to guarantee
  sustainability of this eco system
• Awareness of Grid technology in industry by using
  one of their standard eco system