Model Integrated Planning To Deploy Component Systems

1
Model Integrated Planning To Deploy Component
Systems
Jaiganesh Balasubramanian jai_at_dre.vanderbilt.edu
Department of Electrical Engineering and Computer
Science Vanderbilt University, Nashville
2
DRE Applications

• Typical issues with DRE Applications
• Heterogeneous environments
• Concurrency
• Multiple QoS requirements
• 24/7 availability
• Examples of DRE applications
• E-commerce
• Online trading systems
• Mission critical systems

3
Challenge

• Middleware must help enforce QoS requirements
  simultaneously on the target platform.
• Process involves both planning and preparing for
  deployment of components and their assemblies.
• Planning involves decisions specifying the target
  environment and making appropriate deployment
  decisions, such as identifying the packages that
  will be deployed in the hosts specified in the
  target environment.

4
Solution Approach

• Solution requires Model driven middleware tools
  that
• Can accurately depict the target environment.
• Determine how appropriate deployment decisions
  can be made based on an analysis of expected
  end-to-end QoS packages to be deployed in a given
  target environment.
• Models of the target environment along with
  models of packages can also be used to synthesize
  benchmarking suites that are customized to test
  different aspects of the DRE application and the
  component middleware.

5
(No Transcript)
6
Target Environment

• CoSMIC provides the Model Integrated Deployment
  and Configuration Environment for Composable
  Software Systems (MIDCESS) tool to specify the
  target environment for component systems.
• A target environment is a model of the computing
  resource environment (such as processor speed and
  type of operating system) in which a
  component-based application will execute

7
Terminologies

• Nodes , where the individual components and
  component packages are loaded and used to
  instantiate those components,
• Interconnects ,among nodes, to which
  inter-component software connections are mapped,
  to allow the instantiated components to
  intercommunicate, and
• Bridges ,among interconnects. Interconnects
  provide a direct connection between nodes, while
  bridges provide a routing capability between
  interconnects.

8
Who uses MIDCESS?
9
Modeling Paradigm (1/2)

• MIDCESS is a graphical tool that provides a
  visual interface for specifying the target
  environment for deploying DRE applications
• The modeling paradigm contains entities to model
  the various artifacts of the target environment
  for deploying composable software systems and
  also the interconnections between those artifacts
• The modeling paradigm also allows the domain
  administrators to visualize the target
  environment at various levels of abstractions
  i.e. at the level of domains and sub-domains.

10
Modeling Paradigm (2/2)

• MIDCESS also provides built-in constraint
  checkers that check for the semantic
  compatibility of the specified target environment
• For example, the constraint checker could check
  for connections involving bridges and make sure
  that no two nodes are directly connected using a
  bridge.
• Hierarchical modeling of the individual nodes
  that share certain basic attributes (such as
  their type), but vary in the processing power,
  supported OS etc.
• Specification of the attributes of each of the
  nodes.

11
Constraints Specification

• MIDCESS contains a constraint checker to ensure
  that the target environments specified by the
  tool are semantically compatible
• Constraints are defined using the Object
  Constraint Language (OCL), which is a strongly
  typed, declarative, query and constraint language
• MIDCESS defines constraints to enforce
  restrictions in the
• specification of node elements,
• specification of interconnect elements,
• specification of bridge elements,
• specification of resource elements, and
• interconnection of various elements of the
  domain.

12
Model Interpretation

• The MIDCESS model interpreter translates the
  various domain-related information captured in
  the models constructed using the meta-model into
  a set of descriptors, which are files containing
  meta-data that describes the target deployment
  information of component-based DRE applications.
• MIDCESS generates a domain descriptor that
  describes the domain aspect of the target model
  environment of composable software systems
• This descriptor is an XML document that conforms
  to a XML Schema defined by the DC specification.

13
Ongoing Work

• Develop a modeling paradigm that can specify the
  QoS requirements of the about to be deployed
  component application.
• Analyze the output of this tool and the MIDCESS
  tool as two separate constraints.
• Develop a constraint solver which will take into
  account the constraints and do an analysis of all
  the possibilities and come up with an answer,
  which is the deployment plan for deploying the
  component middleware.