1 / 18

GridCoord - Review

GridCoord - Review. Presentation of Technical Deliverables WP4 - Enhanced Collaboration Task 4.2.1 – “Open Middleware for Grids” workshop – Plans – Igor Rosenberg. The Use of Open Middleware for the Grids. Workshop on Thursday, October 13 th 11 invited speakers Theme : “open middleware”

aaron-davenport
Download Presentation

GridCoord - Review

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. GridCoord - Review Presentation of Technical Deliverables WP4 - Enhanced Collaboration Task 4.2.1 – “Open Middleware for Grids” workshop – Plans – Igor Rosenberg

  2. The Use of Open Middleware for the Grids • Workshop on Thursday, October 13th • 11 invited speakers • Theme : “open middleware” • Panel • Included in the GRIDs@Work week • October 10-14th • +240 people • Theme : “creating & using grid middleware” • 15 events packed in the same week (tutorials, workshops, meetings)

  3. Workshop: morning agenda

  4. Workshop: afternoon agenda

  5. Panel • «Industrial Views on Existing and Future Grid Middlewares» • Chair: Denis Caromel • Mark Gilbert, Microsoft, EMIC • Jean-Pierre Prost, IBM • Daniel Serain, ORACLE • David Snelling, Fujitsu Laboratories of Europe, UK • Philippe TRAUTMANN, Sun, EMEA SE manager • Wolfgang Gentzsch, D-Grid

  6. Workshop conclusions (1) • Grid is still in infancy • A commonly agreed basis is needed for a head start • The community has to involve even more

  7. Workshop conclusions (2) • Grid in general is still unexplored • A programming nightmare • Fundamental research remains to be made • Business grids haven't focussed on user requirements • Gap between science grids and business grids • The Grid world is open source ≠ enterprise • Missing programming models • Missing properties

  8. Workshop conclusions(3) • Many missing features: • Specifications, accounting, interoperability, standards, sustainability, composability, schedulers, stability, dedicated tools, business models... • Required: vendor-independent system, from which to build upon • There will be a true benefit from a common set (services, interoperable layers, components) • Focus on the infrastructure, which will bear all the traffic.

  9. Workshop conclusions (4) The user community has a role to play • enable the uptake of the technologies proposed. • push the different communities to worry about • real user management • VO policies • international exchange. • This major involvement will accelerate the need for standards, and will pave the way to tomorrow’s Grid.

  10. The main Grid inhibitors • QoS, SLA management, end-to-end security, resources acquisition procedures, fault tolerance.. • Dedicated tools and environments, grid programming models (components-based models, service based model, workflows) . • Standards, interoperability, coordination between middleware. • Accounting and billing solutions, intellectual property coverage, legal issues, licensing, common business models.

  11. A wish list for Grid middleware • Interoperability between scheduling offerings and provisioning, interoperability between different implementations, network aware scheduling, scalability, standards based SLA negotiation, components and standard interfaces. • Simplified Grid programming and deployment environment, integration frameworks for grid/web application development. • Business models.

  12. The Grids@Work week agenda

  13. October 10-14th, 2005

  14. ProActive Grid Plugtests Highly heterogeneous : • Machines: IBM, SGI, Sun, Bull, Mac • OS: Linux, Windows, Solaris, MacOS, SGI Irix • JVMs: Sun, SGI, BEA • Protocols: ssh, rsh, sshGSI, Globus Gram • Job Schedulers: PBS, LSF, Grid Engine, Oar, Prun, Globus October 2004 20 sites in the world: 800 processors Total power: 100 Giga Flops October 2005 40 sites in the world 2700 processors Total power: 450 Giga Flops

  15. The PlugTests • Difficulties in setting up the Grid itself • Participating sites administrative/legal difficulties • Not enough flexibility (firewall permissions) • Grid construction and maintenance • subGrids presenting defects to their own API • Missing protocols • Operating System incompatibility (gLite) • Missing middleware features • Good experience, will help the Grid community in its improvement and development • User feedback generally good • Computational results  ease of use

  16. Conclusion • PlugTests, workshops (GridCoord, CoreGrid, Unicore), meetings, tutorials • A success (+240 people) • This kind of hands-on event, where one team deploys some kind of a Grid, specifying some restrictions for using it, can only be good for the Grid community. • allows knowledge sharing • Fosters communication • PlugTests a technical achievement and attractor for the community.

  17. Some key sentences of the panel • Enterprises just wait for more maturity of the Grid middleware. • Open source reference implementations are very important. They are required to help validating the standards, to help the early adoption of the standards, and the business uptake of grid technologies. • The actual service level is typically only best effort. • A competitive environment has to be built, but this will only be possible through standards. • We need to find an agreement on one open service architecture. • We need to standardize and automate provisioning of servers and data, with different ROI (return on investment), guaranteed QoS (quality of service), accounting, and enforced security policies. • Grid world is open source, and not enterprise; bringing these two worlds together is challenging. • A lot of the Grid issues are solvable in the coming 4-5 research years.

More Related