1 / 12

Managing Cross-Cutting QoS Issues in MULTE Middleware

Managing Cross-Cutting QoS Issues in MULTE Middleware. T. Plagemann, F. Eliassen, B. Hafskjold, T. Kristensen , R.H. Macdonald and H.O. Rafaelsen University of Oslo, Norwegian Defence Research Establishment, University of Tromsø Norway

starbuck
Download Presentation

Managing Cross-Cutting QoS Issues in MULTE 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. Managing Cross-Cutting QoS Issues inMULTE Middleware T. Plagemann, F. Eliassen, B. Hafskjold, T. Kristensen, R.H. Macdonald and H.O. Rafaelsen University of Oslo, Norwegian Defence Research Establishment, University of Tromsø Norway Workshop on Quality of Service in Distributed Object Systems at 14th European Conference on on Object-Oriented Programming (ECOOP 2000)

  2. Outline • MULTE project approach • Goals for QoS management • Abstract QoS architecture • layered model • Current prototype - MULTE-ORB • QoS specification and negotiation • flexible protocol framework • flexible management and signalling • Conclusion

  3. MULTE-ORB: General Principles • General goal: flexible protocol support for multimedia applications • decomposition of complex protocols into fine-granular micro-protocols • Quality-of-Service (QoS) • functional behaviour • Principles: • run-time configuration and re-configuration • selection of optimal protocol configuration • implementing open and explicit bindings • Application domains • distance education (OMODIS LoD) • command and control systems • Prototype integrates Da CaPo in COOL-ORB

  4. Goals for QoS Management • Dynamic QoS support • adaptable at runtime • Transparency vs. fine-grained control • Policy control • QoS mapping, control, adaption, ... • Automatic support for compatibility control • Support for seamless system evolution

  5. Application ASA B M Resource Mem Net CPU Abstract QoS Architecture top- down end-to-end

  6. ASA, B and M • QoS mediator language (M) • intermediate syntax for QoS • Model of Bindings and Stream (B) • language for describing streams/bindings • Application Specific Adapter (ASA) • video conference H.323 ASA

  7. Enables objects to specify QoS and performs QoS negotiation Generic Message Protocol Stream COOL Protocol COOL Protocol IIOP QIOP IIOP Da CaPo (v2) Da CaPo (v3) Generic Transport Protocol Flexible protocol framework Da CaPo (v1) Chorus IPC TCP/IP TCP/IP MULTE-ORB Prototype - I • Based on commercial CORBA implementation COOL COOL extensions Object and message level Transport level ChorusOS OS

  8. Management Protocol Management Toolbox MULTE-ORB Prototype - II App • Da CaPo signalling Data Protocol • Different management modules • connection mgnt • QoS negotiation • resource mgnt • monitors • reconfiguration • Policies Net

  9. QoS Specification at Object and Message Layer - I • QoS per object: • too coarse solution • QoS per binding: • changes in QoS requirements require renegotiation of binding • QoS per method invocation: • each method invocation results in a request and reply message • messages are transported over one transport connection • QoS per parameter: • most flexible and most complex approach • multiplexing different parameters with different QoS over one transport connection? or using multiple connections? • QoS per binding and per method invocation

  10. object.method() object.method() object.method() setQoSParameter(Q1) setQoSParameter(Q2) binding established QoS Specification at Object and Message Layer - II • QoS per binding and per method invocation • setQoSParameter(struct QoSparameter **qp)to inform stub about QoS requirements

  11. Conclusion • QoS architecture • 3 level access (M, B, ASA) • automatic conformance testing • dynamic QoS, runtime (re-)configuration • flexible data and signalling protocols • Basis in CORBA implementation • conforms to standard, backwards compatible • Integrated prototype with OMODIS LoD • map to B • ASA for given application (optimization) • generate protocols after database query

  12. Further Information http://www.unik.no/~multe tomkri@unik.no Questions?

More Related