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

Transcription

1 Tools & Techniques for Deployment & Configuration of QoS- enabled Applications Gan Deng Dr. Aniruddha Gokhale Dr. Douglas C. Schmidt Institute for Software Integrated Systems Nashville, Tennessee 23 September 2004

2 Motivation for Deployment & Configuration Goals Promote component reuse Build complex applications by assembling existing Automate middleware services configuration Inject real-time QoS policies into applications declaratively Dynamically deploy to target heterogeneous domains Defer system optimization later based on particular component configuration & deployment settings Repository Platform/ Resource Configuration Field Radar Control System Flight Scheduling Assembly Real-time QoS policies Middleware Bus Airport Approach Control Data Center Deploy: Installation Instantiation Interconnection Client Real-Time Flight Status System Development

3 CCM Deployment & Configuration (D&C) Spec D&C spec was adopted by OMG in 2003 Intended to replace Packaging & Deployment chapter of CCM (CORBA 3.0) specification Supports Hierarchical assemblies Resource management QoS characteristics Automated deployment Vendor-independent deployment infrastructure DLL DLL Implementation QoS Properties Version Meta-data QoS Specs Assembly Deployer Checksum Dependencies DLL DLL Implementation QoS Properties Version Checksum Dependencies Meta-data List of Files Interconnections Meta-data Assembly Deployment Application Assembly

4 D&C & Model-Driven Architecture D&C is specified using a platformindependent model Defines deployment model Independent of CORBA & CCM (specified in UML) Can be refined into CCM-specific model (T1) Uses standard mappings to generate IDL (for on-line data) using UML Profile for CORBA (M1) XML Schema (for off-line data) using XMI (M2) M1 Intermediate transformation T2 Transforms PSM for CCM into suitable input for M1 & M2 PSM for CCM for IDL IDL Platform Independent Model (PIM) Platform Specific Model (PSM) for CCM T1 T2 PSM for CCM for XML XML Schema M2

5 Deployment & Configuration Segments PIM Software Target Execution Data Model Metadata to describe component-based applications & their requirements Metadata to describe heterogeneous distributed systems & their capabilities Metadata to describe a specific deployment plan for an application into a distributed system Run-time Model Repository Manager interfaces to browse, store, & retrieve such metadata Target Manager interfaces to collect & retrieve such metadata & commit resources Execution Manager interfaces to prepare environment, execute deployment plan on target, manage lifecycle Data model Metadata, usually in XML format Run-time model Deployment interfaces (similar to CORBA services)

6 Overview CIAO Tech. Approach Model-driven weaving of crosscutting concerns for middleware & applications Functional Model Systemic Model Analysis DAnCE CoSMIC Weaver Creates Impl Impl Impl Creates Assembly QoS-enabled component middleware Benchmarking <CONFIGURATION_PASS> <HOME> <CONFIGURATION_PASS> < > <HOME> < > <COMPONENT> <ID> <COMPONENT> < ></ID> <EVENT_SUPPLIER> <ID> < ></ID> < events <EVENT_SUPPLIER> this component supplies > < events this component supplies > </EVENT_SUPPLIER> </COMPONENT> </EVENT_SUPPLIER> </HOME> </COMPONENT> </CONFIGURATION_PASS> </HOME> </CONFIGURATION_PASS> Developer Resource Requirements Properties Executor Uses Deployment Plan Deploys Creates Access Resources Assembler Planner Creates Assembler Packages Configures Packager Repository Administrator CIAO QoS-enabled component middleware CoSMIC Modeling development, configuration, & deployment concerns DAnCE Deployment And Configuration Engine Synthesis Printer Laptop computer Desktop Ethernet Bridge COMPONENT REPOSITORY Domain Administrator Specifies Firewall Domain QoS Specs Configurations Dependencies

7 3b. Return container interface 3a. create Executor 6. return the assembly id Execution Manager Domain Application Manager DAnCE Infrastructure Overview Node Manager: Execution Manager: Local/node level Global/Domain daemon process level daemon process 1. Deploy assembly xyz.cdp 2. create node application (component server) 2b.Returnnodeapplicationreference Deployment Target Host Node Application 2a. create 3. create containers Node Manager Node Application Manager Repository Manager: Stores component binaries & metadata to describe Domain Application Manager: A global coordinator interface for deploying an application into the Node target Application: domain CIAO A component server CORE process which hosts containers 4d. Return home objref Container 4c. create CCMHome 4. Install homes 5a. create 4a. Query impluuid 4b. Retrieve impl binaries 5. Install 5b. Return comp objref Enterprise Repository Manager Node Application Manager: A local coordinator interface for deploying an application into the particular node

8 Deployment & Configuration Process Manager Container Home Canonical steps in the application deployment & configuration process (performed by CCM Deployment & Configuration engine): Create the environment within which containers reside Create containers for the Create & register homes for Create & register the themselves Establish connections between

9 Deployment & Configuration Process Step 1 Manager Container Home Canonical steps in the application deployment & configuration process (performed by CCM Deployment & Configuration engine): Create the environment within which containers reside Create containers for the Create & register homes for Create & register the themselves Establish connections between

10 Creating a DomainApplicationManager startlaunch() finishlaunch() Manager startlaunch() create_node_application() create process create objref init() install () install _home() finishlaunch() get objref

11 Deployment & Configuration Process Step 2 Manager Container Home Canonical steps in the application deployment & configuration process (performed by CCM Deployment & Configuration engine): Create the environment within which containers reside Create containers for the Create & register homes for Create & register the themselves Establish connections between

12 Creating a Container Manager startlaunch() create_node_application() init() install () install _home() create container Container ciao_install_home() install _servant() install _component()

13 Deployment & Configuration Process Step 3 Manager Container Home Canonical steps in the application deployment & configuration process (performed by CCM Deployment & Configuration engine): Create the environment within which containers reside Create containers for the Create & register homes for Create & register the themselves Establish connections between

14 Creating a Home Executor & Home Servant Manager startlaunch() create_node_application() open DLLs init() install () install _home() Container ciao_install_home() install _servant() install _component() Home create_component() create() _ciao_activate_component() create home executor create home servant activate home servant create home objref Home Executor create()

15 Deployment & Configuration Process Step 4 Manager Container Home Canonical steps in the application deployment & configuration process (performed by CCM Deployment & Configuration engine): Create the environment within which containers reside Create containers for the Create & register homes for Create & register the themselves Establish connections between

16 Creating a Manager startlaunch() create_node_application() init() install () install _home() Container ciao_install_home() install _servant() install _component() Home create_component() generic create() type-specific _ciao_activate_component() Home Executor create() activate component servant create component servant create component objref create component executor connect() connect_consumer() subscribe()

17 Deployment & Configuration Process Step 5 Manager Container Home Canonical steps in the application deployment & configuration process (performed by CCM Deployment & Configuration engine): Create the environment within which containers reside Create containers for the Create & register homes for Create & register the themselves Establish connections between

18 DomainApplicationManager startlaunch() finishlaunch() Establishing Connections get connection info Manager startlaunch() create_node_application() init() install () install _home() finishlaunch() connect() connect_consumer() subscribe() uses port emits port publishes port

19 Configuring Middleware Services (1/4) Traditional middleware like CORBA 2.x provide applications with access to common middleware services like naming and event service using the underlying ORB middleware. In contrast, in component middleware, the focus is on Providing reusability of by implementing just the application business logic. Enabling easier integration into different application run-time environments and contexts. Hence the component deployers have to provide mechanisms to integrate common middleware services into componentbased applications.

20 Configuring Middleware Services (2/4) Capture usage of common middleware services and formulate as patterns. Example, need to create, initialize and configure the event channel properties before using the Real-time Event service. Encapsulate all the usage patterns to provide reusable service libraries. Example, the RT Event Service library encapsulates the usage patterns for the TAO RT Event Service

21 Configuring Middleware Services (3/4) Service libraries Wrapper facades for the underlying traditional middleware services. Shields component developers from the tedious programming tasks for configuring and using the services. Need a service integration framework that can Automatically start these services. Configure the services based on the QoS properties specified by the component developers using the modeling tools

22 Configuring Middleware Services (4/4) DAnCE Service Configurator Manages the configuration of services, which are exposed as service configuration files. Example, RT Event Service Config captures the various usage options for the RT Event Service Library. Gets instructed by Manager and to automatically load the service Loads the service and configures the service based on the usage options.

23 Conclusion Conventional middleware lacks mechanisms to handle deployment concerns in DRE systems. DAnCE leverages modeling languages and component middleware to support the Efficient storage and retrieval of component implementations. Automatic deployment of. Integrating common middleware services into applications. Future work concentrate on: Applying reliable multicast mechanisms to the various managers to communicate. Enhance DAnCE to support dynamic component assembly reconfigurations, redeployments and migrations.

24 Conclusion