1 / 11

QoS-aware Containers in Tapas Architecture: Design & Development Goals

Explore the design and development of Quality of Service (QoS)-aware containers in Tapas Architecture based on J2EE, with a focus on end-to-end QoS application requirements, core services provisioning, and a case study in a distributed auction scenario.

talisa
Download Presentation

QoS-aware Containers in Tapas Architecture: Design & Development Goals

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. TAPAS Architecture: QoS-aware Containers V. Ghini, G. Lodi, N. Mezzetti, F. Panzieri Department of Computer Science University of Bologna

  2. Summary • Goals • An Auction Scenario • Basic QoS services • Tapas Architecture • Future work and references

  3. Goals • Design and development of QoS-aware containers, based on J2EE • This entails: • Deriving end-to-end QoS application requirements from SLAs • Identifying core services for end-to-end QoS provisioning • Case of study: distributed auction scenario

  4. Legend: SLA contract role Auction Scenario TTP CSP Buyer Seller Marketplace / Auctioneer Credit Rating Agency ASP ISP SSP Retail Bank

  5. Auction: non-functional requirements [Adesso02] • Reliability oriented requirements: • High availability • Failure Recovery • Fault tolerance • Performance oriented requirements: • Timeliness of execution • Relative processing speed • Security oriented requirements: • Authentication • Privacy Fairness?

  6. Basic QoS services (1/2) Basic QoS services are necessary to provide end-to-end QoS, independently of the type of application Three principal services: • Configuration Service • Run Time Support Service • Trust Management Service

  7. Basic QoS Services (2/2) • Configuration Service (CS): • Resource Discovery • QoS Negotiation • Resource Reservation • Run Time Support Service (RTSS): • QoS Monitoring • QoS Adaptation • Resource release • termination and advanced garbage collector

  8. Tapas Architecture:Component Execution Environment Application Tier Application Container QoS Contract (SLA) TAPAS Tier 1 2 CS TMS RTSS

  9. Component Execution Environment Application Container + EJB EJB RTSS TMS CS TGCP: -ENS -EPGM J2EE Services TTM Tapas Architecture input output

  10. Tapas Architecture

  11. Future Work and References • Future Work: • design and development of RTSS, CS, and TMS based on input QoS parameters • References • [Adesso02] Warner Beckman, Marina Oleneva “Application Hosting Requirements”, 27 May 2002, Dortmund • [JC02] Jon Crowcroft “Channel Islands in a Reflective Ocean: Large Scale Event Distribution in Heterogeneous Networks”, 23 May 2002, University of Cambridge

More Related