cosmic: tool-suite for weaving deployment & configuration crosscutting concerns of ccm-based dre...

1
CoSMIC: Tool-suite for Weaving Deployment & Configuration Crosscutting Concerns of CCM- based DRE Systems Dr. Aniruddha Gokhale (PI) Institute for Software Integrated Systems, Vanderbilt University, Nashville, TN 37235 (2) Example: Real-time Publisher/Subscriber Service Deployment & Configuration Crosscutting Concerns •Context – Publisher/subscriber services are highly configurable XML-based specification of QoS properties •Problems Multiple dissimilar services Semantically invalid operating policies Error-prone handwritten XML •Solution Use models to enforce policy constraints & synthesize configuration files (7) EQAL: Capturing Event QoS Aspects in PICML EQAL is part of CoSMIC tool suite and is part of PICML Built in the Generic Modeling Environment (GME) Addresses publisher/subscriber service configuration and deployment challenges Models specify service configurations and deployments Aspects decouple D&C concerns Constraints ensure semantic validity Interpreters generate descriptor files (5) IDML: Capturing Interface Definition Aspects in PICML Graphical modeling language. Component middleware building blocks. Integrated with PICML. Export model to equivalent XML format. Generate middleware- specific application code. IDL generator finished Planned generators for EJB and SLICE IDL XML EJB Create Model Export Generat e Modify Model SLICE IDL Generator Generate (6) Importing CCM Applications Into IDML IDL Importer translates IDL into IDML’s XML format. Import XML into graphical modeling tool. Translate to other middleware platform. Develop model further Regenerate IDL. Generate application code for a different middleware platform. IDL XML Import Modify Model IDL Importer IDL EJB SLICE (9) Towards Platform Independence via MOF-Compliant Modeling Use MOF to IDL mapping to generate IDL interfaces. Inheriting from the MOF abstract IDL interfaces. Used to implement a repository for models. Through repository, models are accessible to other MOF- compliant tools. For generation For further development For reuse in other projects For analysis &simulation MOF Modeling Environment Model Repository MOF Abstract Mapping (IDL) MOF2IDL Repository IDL inherits implement MOF-Compliant Tool MOF-Compliant Tool (1) Deployment & Configuration (D&C) Overview •Specifies interfaces for deployment of component- based applications •Will replace Packaging & Deployment chapter of CCM specification •Platform Independent Model (PIM) •Defined in two dimensions –Data models vs. management (run-time) models –Component software vs. target vs. execution •Meta-information is captured using XML descriptors M eta-data C om ponent C om ponent M eta-data Im plementation Q oS Properties C hecksum Version D ependencies D LL D LL ListofFiles Q oS Specs C om ponent Interconnections Assem bly D eploym ent Application Assem bly Assem bly Im plem entation D LL D LL M eta-data Q oS Properties C hecksum V ersion D ependencies D eployer •Descriptors are passive entities •Manipulated by Actors •Different Stages Development •Developer •Assembler •Packager Target •Domain Administrator Deployment •Repository Administrator •Planner •Executor •Actors are abstract (3) D&C Activities & Stages: Addressing D&C Crosscutting Concerns P lanner D eploym entPlan U ses C reates C om ponent R esource R equirem ents Impl Im pl Im pl Properties D eveloper Assem bler C reates Assem bler C om ponentAssem bly C om ponent C om ponent C om ponent C om ponent C reates Packager C om ponentPackages CO M PO NENT REPO SITO R Y Q oS Specs C onfigurations D ependencies R epository Adm inistrator C onfigures Dom ain Dom ain A dm inistrator Specifies D esktop Printer Laptop com puter Ethernet Bridge Firew all Access R esources Executor D eploys (8) Model Checking & Analysis in CoSMIC Context - DRE system CoSMIC models must be analyzed for functional correctness & QoS properties - CoSMIC provides limited constraint-checking but no model checking & analysis Problem - Selecting the right analysis tool - Choosing the right tool data interchange & interoperability communication model - Preserving semantics of data during transforms - Lossless communication of data & its semantics Solution - KSU’s Cadena model checker for analysis & model refinement - Leverage DARPA MoBIES technology, e.g., Unified Data Model (UDM), Open Tool Interchange Format (OTIF), & Graph Transformation Tool (GReAT) - Two way export & import of models and properties between CoSMIC & Cadena - Lossless data communication via exporting only common information and/or decorating models with extra information. Merging of variations on import. http:// www.dre.vanderbilt.edu/ cosmic Team: Bala Natarajan, Krishnakumar Balasubramanian, Tao Lu, Arvind Krishna, Jaiganesh Balasubramanian, Jeff Parsons, Gan Deng, Emre Turkay, Boris Kolpackov, Gabriele Trombetti, George Edwards. Acknowledgments: Dr. Douglas C. Schmidt Collaborators: LMCO (4) Resolving D&C Challenges via Platform-Independent Component Modeling Language (PICML) • Context – Configuring & Deploying component-based applications using XML meta-data • Problem – Meta-data split across multiple XML descriptors – Inter-dependencies between descriptors – XML is error-prone to read/write manually – No guarantees about semantic validity (only syntactic validation possible) – If meta-data is wrong, what about my application? • Solution Platform Independent Component Modeling Language (PICML) • Modeling paradigm developed using Generic Modeling Environment (GME) Capture dependencies visually Define semantic constraints using Object Constraint Language (OCL) Generate domain specific meta-data from models – Correct-by-construction

Upload: austin-campbell

Post on 04-Jan-2016

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: CoSMIC: Tool-suite for Weaving Deployment & Configuration Crosscutting Concerns of CCM-based DRE Systems Dr. Aniruddha Gokhale (PI) Institute for Software

CoSMIC: Tool-suite for Weaving Deployment & Configuration Crosscutting Concerns of CCM-based DRE SystemsDr. Aniruddha Gokhale (PI)

Institute for Software Integrated Systems, Vanderbilt University, Nashville, TN 37235

(2) Example: Real-time Publisher/Subscriber Service Deployment & Configuration Crosscutting Concerns

• Context– Publisher/subscriber services

are highly configurable– XML-based specification of QoS

properties• Problems

– Multiple dissimilar services– Semantically invalid operating

policies– Error-prone handwritten XML

• Solution– Use models to enforce policy

constraints & synthesize configuration files

(7) EQAL: Capturing Event QoS Aspects in PICML

• EQAL is part of CoSMIC tool suite and is part of PICML– Built in the Generic Modeling Environment (GME)– Addresses publisher/subscriber service configuration and deployment

challenges• Models specify service configurations and deployments• Aspects decouple D&C concerns• Constraints ensure semantic validity• Interpreters generate descriptor files

(5) IDML: Capturing Interface Definition Aspects in PICML

• Graphical modeling language.• Component middleware building

blocks.• Integrated with PICML.• Export model to equivalent XML

format.• Generate middleware-specific

application code.– IDL generator finished– Planned generators for EJB and

SLICEIDL

XML

EJB

Create Model

Export

Generate

Modify Model

SLICE

IDL Generator

Generate

(6) Importing CCM Applications Into IDML

• IDL Importer translates IDL into IDML’s XML format.

• Import XML into graphical modeling tool.– Translate to other middleware

platform.

• Develop model further– Regenerate IDL.

– Generate application code for a different middleware platform.

IDL

XML Import

Modify Model

IDL Importer

IDL EJB SLICE

(9) Towards Platform Independence via MOF-Compliant Modeling

• Use MOF to IDL mapping to generate IDL interfaces.– Inheriting from the MOF abstract IDL

interfaces.– Used to implement a repository for

models.• Through repository, models are

accessible to other MOF-compliant tools.– For generation– For further development– For reuse in other projects– For analysis &simulation

MOF Modeling EnvironmentModel Repository

MOF Abstract Mapping (IDL)

MOF2IDLRepository IDL

inherits

implement

MOF-Compliant Tool MOF-Compliant Tool

(1) Deployment & Configuration (D&C) Overview

• Specifies interfaces for deployment of component-based applications

• Will replace Packaging & Deployment chapter of CCM specification

• Platform Independent Model (PIM)

• Defined in two dimensions

–Data models vs. management (run-time) models

–Component software vs. target vs. execution

• Meta-information is captured using XML descriptors

Meta-data

Component Component

Meta-data

Implementation

QoSProperties

Checksum

Version Dependencies

DLL DLL

List of FilesQoS Specs ComponentInterconnections

Assembly

DeploymentApplication

Assembly Assembly

ImplementationDLL DLL

Meta-data

QoSProperties

Checksum

Version Dependencies

Deployer

• Descriptors are passive entities• Manipulated by Actors• Different Stages

–Development• Developer• Assembler• Packager

–Target• Domain Administrator

–Deployment• Repository Administrator• Planner• Executor

• Actors are abstract

(3) D&C Activities & Stages: Addressing D&C Crosscutting Concerns

Planner

Deployment PlanUses

CreatesComponent

ResourceRequirements

Impl Impl Impl

PropertiesDeveloper

Assembler

Creates

Assembler

Component Assembly

ComponentComponent

ComponentComponent

Creates Packager

Component Packages

COMPONENT REPOSITORY

QoS Specs

Configurations

Dependencies

RepositoryAdministrator

Configures

Domain

DomainAdministrator

Specifies

Desktop Printer Laptop computer

Ethernet Bridge

Firewall

AccessResources

Executor

Deploys

(8) Model Checking & Analysis in CoSMICContext- DRE system CoSMIC models must

be analyzed for functional correctness & QoS properties

- CoSMIC provides limited constraint-checking but no model checking & analysis

Problem- Selecting the right analysis tool- Choosing the right tool data

interchange & interoperability communication model

- Preserving semantics of data during transforms

- Lossless communication of data & its semantics

Solution- KSU’s Cadena model checker for analysis & model refinement- Leverage DARPA MoBIES technology, e.g., Unified Data Model (UDM), Open Tool

Interchange Format (OTIF), & Graph Transformation Tool (GReAT)- Two way export & import of models and properties between CoSMIC & Cadena- Lossless data communication via exporting only common information and/or decorating

models with extra information. Merging of variations on import.

http://www.dre.vanderbilt.edu/cosmicTeam: Bala Natarajan, Krishnakumar Balasubramanian, Tao Lu, Arvind Krishna, Jaiganesh Balasubramanian, Jeff Parsons, Gan Deng, Emre Turkay, Boris Kolpackov, Gabriele Trombetti, George Edwards.Acknowledgments: Dr. Douglas C. Schmidt Collaborators: LMCO (Eagan, Dallas), KSU and UAB

(4) Resolving D&C Challenges via Platform-Independent Component Modeling Language (PICML)

• Context– Configuring & Deploying component-

based applications using XML meta-data• Problem

– Meta-data split across multiple XML descriptors

– Inter-dependencies between descriptors– XML is error-prone to read/write manually– No guarantees about semantic validity

(only syntactic validation possible)– If meta-data is wrong, what about my

application?

• Solution– Platform Independent Component Modeling Language (PICML)

• Modeling paradigm developed using Generic Modeling Environment (GME)– Capture dependencies visually– Define semantic constraints using Object Constraint Language (OCL)– Generate domain specific meta-data from models– Correct-by-construction