ArchitectureLevel Support for Software Component Deployment in Resource Constrained Environments

1
Architecture-Level Support for Software
ComponentDeployment in Resource Constrained
Environments
Marija Mikic-Rakic
Nenad Medvidovic
Computer Science Department University of
Southern California

• Presenters
• Rajesh Gwalani
• Sushil Srinivasan

2
Introduction

• Software Deployment
• Installing or updating software system after the
  software has been developed released.
• Key Activities
• Deployment of a system on to a host.
• Component upgrade in the existing system.
• Static Analysis of proposed system configuration
  before the deployment.
• Dynamic analysis of new configuration after the
  deployment.

3
Introduction (contd.)

• Problems with Human-operated deployment
• Many versions of components.
• Vendors lack control.
• Multiple version systems.
• Problems with existing automated deployment
  methods
• Patches do not provide control.
• Other approaches do not consider system
  architecture require additional facilities.
• Solution
• Light weight s/w system architecture that
  facilitates deployment.
• Has support for intelligent, dynamic upgrades of
  component versions.

4
Software Architecture

• Forms basis for deployment
• Defined in terms of
• Components
• Connectors
• Configuration
• Architectural Style

5
TDS (example application)
6
PRISM Architectural Style

• Target
• Components
• Ports
• Connectors
• Message
• Request
• Notification
• Peer Message
• Substrate independence

7
Connectors

• Dynamic interface update
• Run-time configuration
• Types
• Horizontal
• Peer
• Border

8
Architecture Modeling Analysis

• Levels of Architecture
• Application Level
• Meta Level
• Types of Messages
• Application Data
• Component Content
• Architectural Model
• Meta Level Components
• Admin Component
• Continuous Analysis

9
Architecture Implementation

• Light Weight Architecture implementation
  infrastructure.
• Application Built by extending classes.
• Architecture Class
• Steps
• Subclass Component class.
• Instantiate Architecture class.
• Define instances of Components Connectors.
• Attach Components to Connectors.
• Meta-level Components may be added.

10
Architecture Implementation (contd.)
11
System Deployment

• Basic Requirements
• Skeleton Configuration preloaded on each host.
• Admin Component has pointer to Architecture
  object.
• Deployment Process
• Centralized ownership
• Distributed ownership

12
Deployment
Centralized Ownership
Distributed Ownership
13
Centralized Deployment
M
14
Deployment Environment

• Integrated Extended MS Visio Tool for Prism
  DE
• Tool boxes to specify h/w configuration, s/w
  components connectors.
• Validated configuration deployed by a button
  click.
• Supports Centralized ownership.
• Generates architectural description in ADL.

15
Component Upgrade

• Run-time support for reliable upgrades.
• Possible problems with component upgrade.
• Choice to be made
• Deploy new version discard old.
• Retain old version.
• Deploy both versions.

16
Multi Version Components (MVC)

• MVC
• Authority Specification
• Log Compare results
• Periodic record of state of each
• component for roll back.

17
MVC Implementation

• Special Purpose Connectors
• MVC-Top
• MVC-Bottom
• MVC-Side
• Connectors invokes operation within a version.
• GUI available for MVC
• Overhead of MVC

18
GUI for MVC
19
Related work

• Software Dock 5
• Release Dock
• Field Dock
• Hercules 2
• Supports multiple procedure execution
• Drawbacks

20
Conclusion Further Work

• Implementation infrastructure is light weighted
  and portable.
• Connectors may be used to implement security
  protocols.
• Long term goals.
• Performance enhancements.
• Optimal component deployment.
• Self-awareness run-time monitoring.