CIAO ComponentIntegrated ACE ORB

1
CIAO Component-Integrated ACE ORB

• Nanbor Wang
• Center of Distributed Object Computing
• Department of Computer Science
• Washington University in St. Louis
• nanbor_at_cs.wustl.edu

2
CORBA 2.x Object Model

• Application developers are forced to play
  multiple roles
• Application functional component developers
• tightly coupled application modules
• Computational resource provisioners
• ensuring the availability of common object
  services
• ad-hoc management
• System configurators
• boiler plate code
• manual application deployment
• Resulting in tight couplings
• Brittle implementation
• Hard to adapt and maintain
• Increase time-to-market

3
The CORBA Component Model (CCM)

• Enhances CORBA Object Model
• Provides common run-time environment
• application servers
• containers
• COS Notification, Security, Persistent State,
  Transaction
• Uses metadata to describe application
  composition, resource allocation, and
  infrastructure configurations
• component dependencies
• component connections
• component configuration
• component run-time services, e.g., transactional,
  persistence state

4
Current CCM Fails to Address Advanced QoS
Requirements
QoS-enabled CCM ? CCM RT CORBAWhy doesn't
running a RT ORB beneath CCM make it a
QoS-enabled CCM implementation?

• Applications requires a wide variety of
  infrastructure support, e.g., QoS guarantees
• Plain CCM has no mechanisms to specify and
  enforce QoS policies
• QoS policies need to be assured end-to-end for
  components connections
• Ensuring QoS policies in component
  implementations leads to
• QoS mechanisms that are hard to utilize and go
  beyond component implementations
• Component connections
• private connections
• bandwidth reservation
• Component collaborations
• Thread pools
• Thread borrowing
• Tight couplings among component implementations
• Difficulty in reusing existing components
  (without QoS knowledge)

5
QoS-Enabled Component Middleware

• Separate the concerns for QoS managements
• Separate the roles
• Application component developers
• QoS assurance mechanism developers
• QoS provisioning managers
• ORB configurators
• Compose QoS assurance mechanisms
• ORB OS
• Application-specific Adaptive
• Specify metadata for QoS requirements of
• components
• component connections

Extend component middleware to support more
advanced infrastructure and resource management
6
Component-Integrated ACE ORB

• Extension to component assembly descriptors
• Component and connection QoS specifications
• ORB modules
• Adaptation modules
• QoS-enabled containers
• Policy-based adaptation insertion
• Client-side policy aggregates
• Integrating RT-CORBA ACE QoS API (AQoSA)
• Benchmark and document test applications using
  various combinations of QoS aggregates

7
Current Status and Future Work

• Current Status
• CCM Core
• IDL extension
• XML and Configuration
• Packaging and Deployment
• CIDL compiler
• Future Work
• Case Study Boeing MoBIES component model
• Support other QoS assurance mechanismsIntegratin
  g with BBNs QuO
• Integration with Vanderbilt Universitys
  Model-Integrating Computing Tools
• Project Statushttp//www.cs.wustl.edu/nanbor/pro
  jects/