1 / 11

An SLA framework for the GT4 Grid middleware

An SLA framework for the GT4 Grid middleware. Igor Rosenberg Atos Origin Spain In collaboration with René Heek (HLRS) Ana Juan (Atos Origin). Motivation, problem area. Recognised problem of assuring a decent Quality of Service (QoS)

zeroun
Download Presentation

An SLA framework for the GT4 Grid middleware

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. An SLA framework for the GT4 Grid middleware Igor Rosenberg Atos Origin Spain In collaboration with René Heek (HLRS) Ana Juan (Atos Origin)

  2. Motivation, problem area • Recognised problem of assuring a decent Quality of Service (QoS) • Service Level Agreements (SLAs) are probably the most important documents in every business-aware framework –at least they should be. • Existing implementations supporting full SLA management?

  3. Research Objectives • State-of-the-art of SLA frameworks • Discover business needs based on real experiences • Define and implement the missing pieces.

  4. Research approach, Methodology … BE25 Other projects BE2 BE3 BE1 ... • BEinGrid SLA Cluster: • horizontal look at SLA best practices and gap-analysis Middleware 1 Mdw -n Middleware 2

  5. The BEinGRID Methodology • Extract SLA Common Technical Requirements Needs expressed in a given scenario • Define Common Capabilities A functionality which answers this technical need • Define Design Patterns The middleware-agnostic architecture needed to provide this functionality • Define Components Middleware-specific implementations

  6. Major Outcomes/Results • SLA Common Technical Requirements • Common Capabilities • Design Patterns • Components • SLA Template Specification • Publication and Discovery • Negotiation • Optimization of Resource Selection • Monitoring • Evaluation • Re-negotiation • Accounting • SLA Negotiation for GT4 • SLA Optimisation of Resource Selection for GRASP, and for GT4 • SLA Monitoring and Evaluation for GRASP, and for GT4 • SLA Accounting for GRIA and GT4 • Results: • Requirementsforgeneric SLA frameworks • A gap analysis • A set of components • Justifiedbybusinessbenefits

  7. BEinGrid SLA Software components

  8. Global view of the SLA Framework for GT4 v4.0.5 Most BEinGrid capacities are in the SLA framework • Negotiation • Optimisation • Monitoring and Evaluation • Accounting Not yet contemplated Ganglia + MDS included

  9. Gap analysis, comparing various frameworks

  10. Conclusion and outlook • Conclusion • generic technical requirements, common capabilities, design patterns, and components. • Justify a simple architecture based on components: a framework for SLAs for GT4 • Compared it to other existing frameworks • Futurework: • Finishimplementation (November2008?) and validate • Add extra capabilities • Publication and Discovery (marketplace?) • Brokering of templates/negotation • Proposeexamplesfor • Negotiationstrategies • Crisis Handling (changingstrategiesbasedonviolations) • Proveinteroperabilitywithotherframeworks(GRASP, GRIA, UNICORE)

  11.  Game over  Thank you for your attention Any questions?

More Related