DAnCE OMG RTWS

Tools & Techniques for Deployment & Configuration of QoS-enabled Component Applications: 

Tools & Techniques for Deployment & Configuration of QoS-enabled Component Applications Dr. Douglas C. Schmidt schmidt@dre.vanderbilt.edu www.dre.vanderbilt.edu/~schmidt Jaiganesh Balasubramanian jai@dre.vanderbilt.edu www.dre.vanderbilt.edu/~jai Dr. Aniruddha Gokhale gokhale@dre.vanderbilt.edu www.dre.vanderbilt.edu/~gokhale Gan Deng dengg@dre.vanderbilt.edu www.dre.vanderbilt.edu/~dengg

OMG Component Deployment & Configuration Spec (1/2): 

OMG Component Deployment & Configuration Spec (1/2) OMG Deployment & Configuration (D&C) specification (ptc/05-01-07) Goals of D&C Phase Promote component reuse Build complex applications by assembling existing components Automate common services configuration Declaratively Inject QoS policies into applications Dynamically deploy components to target heterogeneous domains

OMG Component Deployment & Configuration Spec (1/2): 

OMG Component Deployment & Configuration Spec (1/2) OMG Deployment & Configuration (D&C) specification (ptc/05-01-07)

OMG Component Deployment & Configuration Spec (2/2): 

Specification & Implementation Defining, partitioning, & implementation application functionality as standalone components Packaging Bundling a suite of software binary modules & metadata representing application components Installation Populating a repository with the packages required by the application Configuration Configuring packages with parameters to satisfy functional & systemic requirements of applications without constraining to physical resources Planning Making appropriate deployment decisions to identify entities (such as CPUs) of target environment where packages will be deployed Preparation Moving binaries to identified entities of target environment Launching Triggering installed binaries & bringing application to a ready state QoS Assurance & Adaptation Runtime resource management to maintain end-to-end QoS OMG Component Deployment & Configuration Spec (2/2) Key challenge: Implementing these D&C capabilities portably & efficiently

Slide5: 

Tech. Approach Model-driven weaving of crosscutting concerns for middleware & applications CIAO CoSMIC DAnCE CIAO – QoS-enabled component middleware CoSMIC – Modeling development, configuration, & deployment concerns DAnCE – Deployment & Configuration Engine QoS-enabled component middleware Putting the Pieces Together

OMG’s Deployment & Configuration Dimensions: 

OMG’s Deployment & Configuration Dimensions Data Model Metadata, usually in XML format Run-time Model Deployment interfaces (similar to CORBA services)

OMG’s Deployment & Configuration Dimensions: 

OMG’s Deployment & Configuration Dimensions Component Packaging & Assembly Component DLLs Component & Home Properties Component Interface Descriptors (.ccd) Packaging Tools Component Packages (*.cpk) Component & Home Properties Component Package Descriptors (.cpd) Implementation Artifact Descriptors (.iad) Assembly Tools Component Implementation Descriptor (*.cid)

OMG’s Deployment & Configuration Dimensions: 

OMG’s Deployment & Configuration Dimensions DAnCE implements the run-time model

DAnCE In Action: 

DAnCE In Action Execution Manager: Global/Domain level daemon process

DAnCE In Action: 

Domain Application Manager: A global coordinator interface for deploying an application into the target domain Node Manager: Local/node level daemon process DAnCE In Action

DAnCE In Action: 

Node Application Manager: A local coordinator interface for deploying an application into the particular node DAnCE In Action

DAnCE In Action: 

Node Application: A component server process which hosts containers Repository Manager: Stores component binaries & metadata to describe components DAnCE In Action

Resolving Design Challenges w/ Implementing DAnCE (1/3): 

Resolving Design Challenges w/ Implementing DAnCE (1/3) Context Each component has its lifecycle state, i.e., preactive, active, passive and deactivated Components in an assembly have dependencies between each other via ports Problem Must ensure component assembly always in semantically consistent state when state changes on individual components Solution Use the DomainApplicationManager to coordinate component assembly lifecycle operations DomainApplicationManager records the states of all components within an assembly Guys, can you please add another (small) diagram here that shows the solution?

Resolving Design Challenges w/ Implementing DAnCE (2/3): 

Context Component runs in a NodeApp process Must ensure real-time QoS configuration policies for DRE applications Problem Tight coupling between business logic & systematic configuration aspects There is no way to specify & enforce QoS policies for DRE applications Programming QoS aspects imperatively is tedious, error prone & insufficiently customizable Solution Makes real-time aspects an integral part of the framework so they can be composed into DRE applications Extending CIAO and DAnCE atop TAO’s Real-time CORBA features Real-time behavioral specification <rtpolicyset id="HIGH_PRIORITY"> <priority_model_policy type="server_declared“ priority=“6"/> </rtpolicyset> <instance id=“a_Position_Radar"> <name>BasicSP-PR-idd</name> <implementation>BasicSP-PR-mdd</implementation> <configProperty> <extension class="RT-POLICY-SET“ origin="CIAO"> HIGH_PRIORITY </extension> </configProperty> </instance> Resolving Design Challenges w/ Implementing DAnCE (2/3)

Resolving Design Challenges w/ Implementing DAnCE (3/3): 

Context The ORB provides a wide variety of middleware services, e.g., publish/subscribe services, naming, etc. Problem Component utilizes middleware services through an ad-hoc fashion (tightly coupled functional implementation with service configuration) No way to reuse components without hard coding Solution Encapsulates common usages of services as reusable libraries Allows services to be specified & configured explicitly through metadata Service could be configured and deployed through DAnCE Middleware Service Configurator Resolving Design Challenges w/ Implementing DAnCE (3/3)

Related Work: 

Related Work Guys, can you please add an overview of related work here, complete with some picture?!

Concluding Remarks: 

Concluding Remarks DAnCE leverages modeling languages & component middleware to support the Efficient storage & retrieval of component implementations Automatic deployment of components Configuring real-time behaviors and common middleware services into applications Future work on DAnCE will focus on: Applying reliable multicast mechanisms so various managers can communicate dependably & scalably Supporting uninterrupted dynamic component assembly reconfigurations, redeployments, & migrations Time/space optimizations DAnCE can be downloaded from www.dre.vanderbilt.edu/CIAO Dynamic Reconfiguration