Distribution and Configuration Support for PNO Applications'

1
Distribution and Configuration Support for PNO
Applications.

• Thomas Unterschütz, Veit Vogel
• T-Nova
• Deutsche Telekom Innovationsgesellschaft mbH
• Next Generation Services Architectures and
  Platforms
• Email Thomas.Unterschuetz_at_Telekom.de
• Phone [phone]
• Fax [phone]

2
Distribution and Configuration Support for PNO
Applications.

• Purpose
• MiddlewareTelecom Domain ServicesHow to achieve
  QoS
• DistributionQoS aspects of distributionProject
  focus
• StandardisationActual project situation

• Content
• Assumptions Quality of Service
• DeploymentOverview and details
• Conclusionsand prospects

3
The Project.

• A few words about the project
• Project
• Distribution and configuration support for
  distributed PNO applications
• Co-operation ofEuropean Carriers
• Research InstitutesUniversities

4
Assumptions.

• Assumptions
• CORBA based approach for middleware platforms
• ...we expect CORBA to be the most important
  middleware
• ...we see the CORBA Component Model (CCM) as the
  most important aggregation model

5
Assumptions.

• Assumptions
• Approach for middleware platforms
• Highly distributed systems
• ...we expect the futures (telecom-)services to be
  highly distributed
• ...we expect the futures (telecom-)services to
  be most component based

6
Assumptions.

• Assumptions
• Approach for middleware platforms
• Highly distributed services
• Telecom applications
• ...are extremely heterogeneous, complex dynamic,
  scalable, available, fault tolerant...

!"
7
Assumptions.

• Assumptions
• Approach for middleware platforms
• Highly distributed services
• Telecom applications
• ...are extremely heterogeneous, complex dynamic,
  scalable, available, fault tolerant...

8
Quality of Service.

• Requested QoS
• Availability
• Load capacity
• Bandwidth
• Delay
• Others as security, customisation, simplicity

!"
9
Quality of Service.

• Requested QoS for telecom applications
• Availability
• Load capacity
• Bandwidth
• Delay
• Others as security, customisation, simplicity

10
Quality of Service.
7

• Requested QoSfor telecom applications
• Availability
• Load capacity
• Bandwidth
• Delay
• Others as security, customisation, simplicity

24
52
11
Quality of Service.

• Requested QoSfor telecom applications
• Availability
• Load capacity
• Bandwidth
• Delay
• Others as security, customisation, simplicity

100000000000
12
Quality of Service.

• Requested QoSfor telecom applications
• Availability
• Load capacity
• Bandwidth
• Delay
• Others as security, customisation, simplicity

13
Quality of Service.

• Requested QoSfor telecom applications
• Availability
• Load capacity
• Bandwidth
• Delay
• Others as security,customisation, simplicity

14
Quality of Service.

• How to achieve QoSfor telecom applications
• Availability ? redundancy
• Load capacity
• Bandwidth
• Delay
• Others as security,customisation, simplicity

Telecom Service X2
Telecom Service X1
CORBA Middleware Platform
15
Quality of Service.

• How to achieve QoSfor telecom applications
• Redundancy
• Load capacity ? scalability
• Bandwidth
• Delay
• Others as security,customisation, simplicity

CORBA Middleware Platform
16
Quality of Service.

• How to achieve QoSfor telecom applications
• Redundancy
• Scalability
• Bandwidth ? transport QoS
• Delay
• Others as security,customisation, simplicity

Telecom Service
Telecom Service
CORBA Middleware Platform
Heterogeneous Transport
17
Quality of Service.

• How to achieve QoSfor telecom applications
• Redundancy
• Scalability
• Transport QoS
• Delay ? co-location
• Others as security,customisation, simplicity

Telecom Service
Telecom Service
CORBA Middleware Platform
Heterogeneous Transport
18
Quality of Service.

• How to achieve QoSfor telecom applications
• Redundancy
• Scalability
• Transport QoS
• Co-location
• Others as security,customisation, simplicity

Telecom Service
Telecom Service
CORBA Middleware Platform
Platform Services
19
Quality of Service.

• How to achieve QoSfor telecom applications
• Redundancy
• Scalability
• Transport QoS
• Co-location
• Others as security,customisation, simplicity

Telecom Service
Telecom Service
CORBA Middleware Platform
Platform Services
20
Quality of Service.

• How to achieve QoSfor telecom applications
• Vision of a deployment service

Telecom Service
Telecom Service
CORBA Middleware Platform
Deployment Services
21
Distribution.
CORBA Middleware Platform
22
Static vs. Dynamic Distribution.

• Distinction
• Static DistributionDistribution and
  Configuration during start-up-time
• vs.
• Dynamic Distribution Redistribution and
  Reconfiguration while life-time

CORBA Middleware Platform
23
QoS for Distributed Services.

• Static and dynamic distribution effects QoS
• Co-locationminimised communication, minimised
  delay

CORBA Middleware Platform
24
QoS for Distributed Services.

• Static and dynamic distribution effects QoS
• Co-location
• Assignment to resourcesoptimal service
  performance,optimal usage of resources

CORBA Middleware Platform
25
QoS for Distributed Services.

• Static and dynamic distribution effects QoS
• Co-location
• Assignment to resources
• Duplication of objectredundancy,
  scalability,dependability

CORBA Middleware Platform
26
QoS for Distributed Services.

• Static and dynamic distribution effects QoS
• Co-location
• Assignment to resources
• Duplication of object
• Migrationunequal service load,agent
  technology,insertion of nodes,user mobility

CORBA Middleware Platform
27
Deployment.

• How to deploy the service?
• Service/component design
• Decide on an appropriate distribution pattern
• Upload
• Installation configuration
• Execution
• Monitoring and Redistribution (migration)

28
Deployment.

• ...and in which way is it done?
• Until todayBy hand
• Introduced by the projectAutomatically

29
Not to be shown.
30
Deployment.
Deployment Specification
Deployment Tools
Deployment Activities
31
Deployment Specification.
DCL SyntaxStork
UML
Other Notations
Deployment Tools
Deployment Activities
32
Deployment Tools.
Deployment Specification
DCL Translator
other Translator
UML Translator
Deployment XML
XML Tool
Deployment Activities
33
Deployment Activities.
Deployment Specification
Deployment Tools
InstallationScripts
InstallationMap
Run-TimeConstraints
34
Template Page.

• Argumentation
• Bullets

35
Deployment.

• Deployment and Configuration Syntax
• Description of serviceproperties and constraints
• Description of environment properties and
  constraints
• InterfacesTextual, human readablegraphical (?)

DCL SyntaxStork
UML
Other Notations
other Translator
UML Translator
DCL Translator
Deployment XML
XML Tool
InstallationMap
InstallationScriptx
Run-TimeConstraints
36
Deployment.

• Extended Deployment XML
• XML packaging description
• Deployment XML includes CCM and DCL adaptation
• Extended Deployment XMLincludes description of
  target environment

DCL SyntaxStork
UML
Other Notations
other Translator
UML Translator
DCL Translator
Deployment XML
XML Tool
InstallationMap
InstallationScripts
Run-TimeConstraints
37
Installation Map.

• How to find an installation map
• NP-completeness?
• Heuristic approach?
• Backtracking algorithm?
• Optimal solution out of scope

DCL SyntaxStork
UML
Other Notations
other Translator
UML Translator
DCL Translator
Deployment XML
XML Tool
InstallationMap
InstallationScripts
Run-TimeConstraints
38
Installation Scripts.

• Installations Scripts
• Phyton based prototypical implementation

DCL SyntaxStork
UML
Other Notations
other Translator
UML Translator
DCL Translator
Deployment XML
XML Tool
InstallationMap
InstallationScripts
Run-TimeConstraints
39
Deployment.

• Run-Time Constraints
• Constraints ofcomponents, services and
  environment
• Constraints violation may cause migration
• Migrated systemis partial/iterative optimal
• Meet a system invariant

DCL SyntaxStork
UML
Other Notations
other Translator
UML Translator
DCL Translator
Deployment XML
XML Tool
InstallationMap
InstallationScript
Run-TimeConstraints
40
Conclusions and Prospects.

• Conclusions
• Specification and implementation of deployment
  support is possible
• Prototypical implementation
• Evaluation with a typical telecom service

DCL SyntaxStork
UML
Other Notations
other Translator
DCL Translator
UML Translator
Deployment XML
XML Tool
InstallationMap
InstallationScripts
Run-TimeConstraints
41
Conclusions and Prospects.

• Conclusions
• Specification and implementation of deployment
  support is possible
• Influencing standardisation bodies
• ITU-T Stork notation
• OMG Extended Deployment XML

42
Distribution and Configuration Support for PNO
Applications.

• Thomas Unterschütz, Veit Vogel
• T-Nova
• Deutsche Telekom Innovationsgesellschaft mbH
• Next Generation Services Architectures and
  Platforms
• Email Thomas.Unterschuetz_at_Telekom.de
• Phone [phone]
• Fax [phone]