• Nem Talált Eredményt

Deploying Services in

N/A
N/A
Protected

Academic year: 2023

Ossza meg "Deploying Services in "

Copied!
19
0
0

Teljes szövegt

(1)

Deploying Services in DoCoMo’s Testbed

Deploying Services in

Deploying Services in DoCoMo’s DoCoMo’s Testbed

Testbed

K K ároly ároly Farkas Farkas

Computer Engineering and Networks Computer Engineering and Networks

Laboratory Laboratory

ETH Zürich, Switzerland

ETH Zürich, Switzerland

(2)

Outline Outline

• Service Deployment in General

• Overview of the Prototype Scenario from the Service Deployment’s Viewpoint

• Network Level Service Deployment

• Node Level Service Deployment (Chameleon)

• Implementation Summary

• To Do List

(3)

Service Deployment on Two Levels Service Deployment on Two Levels

• Network level service deployment [Matthias’ ANTA paper, 2003]

– Identification of appropriate nodes to run service components – Allocation of network resources

• Node level service deployment [Matthias’ Smartnet paper, 2002]

– Identification of appropriate service components

- Depending on node environment

– Installation and Binding of these service components

(4)

Prototype Scenario Prototype Scenario

Handover Manager Service Deployment

Server

Provider’s Fix Network

Mobile Node 1.

2.

(5)

Network Level Service Deployment I.

Network Level Service Deployment I.

Service Deployment Manager

Code Server

Service Deployment Server

Management Execution Environment

Service Server Local Service

Creation Engine Management Execution

Environment

1. Services to install

Handover Manager’s Chameleon (Node level Service

2. Downloading Service Descriptors

3. Downloading Module Codes 4. Confirmation

Execution Environments

HSM EE Module

Installation

(6)

Network Level Service Deployment II.

Network Level Service Deployment II.

Service Deployment Manager

Code Server

Service Deployment Server

(Service Creation Framework) Management Execution

Environment

Service Server Local Service

Creation Engine Management Execution

Environment

Mobile Node’s Chameleon (Node level Service Creation Framework)

2. Downloading Service Descriptors

3. Downloading Module Codes 1.Request the List of

Available Services

Execution Environments

HSM EE

PromethOS EE

Module Installation Service

Selection

(7)

Node Level Service Deployment Node Level Service Deployment

• Service model

– Component based

– Support for transport/control plane separation

• Node level service deployment mechanism

– Resolution of the node independent service specification to a node specific service implementation (this resolution controlled by the node)

– Installation of the resulted implementations into the required Execution Environments

• Chameleon is our prototype implementation of node level service

deployment

(8)

Active Node Model Active Node Model

• NodeOS

– Demultiplexing, resource control

• Management EE

– Manages service EEs – Configures nodeOS

– Runs Service Creation Engine (SCE)

• Service EE

– Runs service components

– Provides a particular programming model (user space / CORBA, kernel / C, etc.)

SCE Management

Execution Environment

NodeOS

Service Execution Kernel Environment

Service Execution Corba Environment

Active Node

Hardware

Demux

(9)

Service Description: Service Tree Service Description: Service Tree

• Dependency resolution of the service specification

• Tree nodes represent compositions of service components

• Leaves represent implementations (code modules or built-in service components)

• Tree is a management structure in the management EE

• Tree depends on node environment/capabilities

(10)

Service Description: Implementation Maps Service Description: Implementation Maps

• EE specific implementation maps

• Grey components are the leaves from the service tree

• Components are mapped to code modules for different EEs

• Adapters allow inter-EE communications

WaveVideo Classifier Controller Java EE

Packet Classifier/

Dropper 1 Java EE

Adapter

Adapter

Adapter Queue 3

Kernel EE Adapter

Java EE Kernel EE

(11)

Local Service Creation Engine Local Service Creation Engine

Mobile Node

(12)

Node Property Description Node Property Description

Notation:

• Elements ─> surrounded by ellipses

• Attributes ─> encircled by a hexagon

• Doubly surrounded Elements ─> may appear more than once

• Mandatory nodes ─> solid arrows; Optional nodes ─> dashed arrows

(13)

XML Node Descriptor for the Prototype Services XML Node Descriptor for the Prototype Services

<?xml version="1.0" encoding="UTF-8"?>

<NODE_DESCRIPTION xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:noNamespaceSchemaLocation="C:\Chameleon\XML\chameleon.xsd">

<xsi:OS xsi:name="Linux" xsi:version="2.4.20"/>

<xsi:EE xsi:name="HSMEE" xsi:configurator="hsmee" xsi:version="1">

<xsi:PORT xsi:type="push_in"/>

<xsi:PORT xsi:type="push_out"/>

</xsi:EE>

<xsi:EE xsi:name="PROMETHOS" xsi:configurator="promethos" xsi:version="1">

<xsi:PORT xsi:type="push_in"/>

<xsi:PORT xsi:type="push_out"/>

<xsi:PORT xsi:type="procfs_in" xsi:flag="optional"/>

<xsi:PORT xsi:type="procfs_out" xsi:flag="optional"/>

</xsi:EE>

<xsi:EE_CONNECTIONS xsi:fromEE="PROMETHOS" xsi:toEE="HSMEE">

<xsi:CONNECTION xsi:fromPort="procfs_out" xsi:toPort="push_in"/>

</xsi:EE_CONNECTIONS>

<xsi:EE_CONNECTIONS xsi:fromEE="HSMEE" xsi:toEE="PROMETHOS">

<xsi:CONNECTION xsi:fromPort="push_out" xsi:toPort="procfs_in"/>

</xsi:EE_CONNECTIONS>

<xsi:EE_CONNECTIONS xsi:fromEE="PROMETHOS" xsi:toEE="PROMETHOS">

<xsi:CONNECTION xsi:fromPort="push_out" xsi:toPort="push_in"/>

</xsi:EE_CONNECTIONS>

<xsi:EE_CONNECTIONS xsi:fromEE="HSMEE" xsi:toEE="HSMEE">

<xsi:CONNECTION xsi:fromPort="push_out" xsi:toPort="pull_in"/>

</xsi:EE_CONNECTIONS>

(14)

Service Description Service Description

Notation:

• As previously

(15)

XML Service Descriptor: Context Aware Handover XML Service Descriptor: Context Aware Handover

Service on Mobile Node Service on Mobile Node

<?xml version="1.0" encoding="UTF-8"?>

<SERVICE_LIST xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:noNamespaceSchemaLocation="C:\My Documents\Projects\Chameleon\XML\chameleon.xsd">

<SERVICE xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:noNamespaceSchemaLocation="C:\My Documents\Projects\Chameleon\XML\chameleon.xsd"

xsi:type="SPECIFICATION">

<DESCRIPTION xsi:servicename="ContextAwareHandover-MN" xsi:option="normal">

<PROVIDER>DoCoMo</PROVIDER>

<VERSION>0.1</VERSION>

</DESCRIPTION>

<PORTS>

<IN_PORT xsi:type="push_in"/>

<OUT_PORT xsi:type="push_out"/>

</PORTS>

<SUB_SERVICE xsi:name="HDM" xsi:instance_name="hdm"/>

<SUB_SERVICE xsi:name="HSMforMN" xsi:instance_name="hsm_for_mn"/>

<TRANSPORT_CONNECTION>

<SRC_PORT xsi:service_instance="this" xsi:type="push_in"/>

<DEST_PORT xsi:service_instance="hdm" xsi:type="push_in"/>

</TRANSPORT_CONNECTION>

<TRANSPORT_CONNECTION>

<SRC_PORT xsi:service_instance="hsm_for_mn" xsi:type="push_out"/>

<DEST_PORT xsi:service_instance="this" xsi:type="push_out"/>

</TRANSPORT_CONNECTION>

(16)

XML Service Module Descriptor: Modules of Context XML Service Module Descriptor: Modules of Context

Aware Handover Service on Mobile Node Aware Handover Service on Mobile Node

<?xml version="1.0" encoding="UTF-8"?>

<SERVICE_LIST xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:noNamespaceSchemaLocation="C:\Chameleon\XML\chameleon.xsd">

<SERVICE xsi:type="IMPLEMENTATION">

<DESCRIPTION xsi:servicename="HDM" xsi:option="normal">

<PROVIDER>DoCoMo</PROVIDER>

<VERSION>0.1</VERSION>

</DESCRIPTION>

<ENVIRONMENT>

<OS>

<NAME>Linux</NAME>

<VERSION>2.4.20</VERSION>

</OS>

<EE>

<NAME>PROMETHOS</NAME>

<VERSION>1</VERSION>

</EE>

</ENVIRONMENT>

<PORTS>

<IN_PORT xsi:type="push_in"/>

<OUT_PORT xsi:type="push_out"/>

</PORTS>

<CODE_LOCATION>handover.o</CODE_LOCATION>

</SERVICE><SERVICE xsi:type="IMPLEMENTATION">

...

(17)

Java Implementation Summary I.

Java Implementation Summary I.

• Previously given code

– Chameleon (local Service Creation Framework)

• Modified or rewritten modules in Chameleon

– Local Service Creation Engine module – Specification Processor module

– Specification Parser module – Local Service Registry module – Code Fetcher module

– Deployment Engine module

– Some little modifications in several other modules…

(18)

Java Implementation Summary II.

Java Implementation Summary II.

• Newly implemented

– Service Deployment Server

- Service Deployment Manager module - Code Server module

- Service Server module

– Some new Chameleon modules

- HSM Execution Environment Configurator module

- PromethOS Execution Environment Configurator Server module - PromethOS Execution Environment Configurator Client module

– Several XML files to describe the services

– Several shellscripts to let the Service Creation Framework run in an easy and convenient way

• Total summary

– More than 30 modules

– Several thousands lines of Java code with exhaustive error handling

(19)

To Do List To Do List

• Finishing the integration of the implemented service modules into the Service Framework

– almost done with the simple Context Aware Handover modules

• Testing

• Accomplishing the code documentation

• Present the demo as soon as possible ☺

Hivatkozások

KAPCSOLÓDÓ DOKUMENTUMOK

To derive the approximation, we assume that the ranking method is independent of the base node, that is, all nodes rank a given set of node descriptors the same way.. The rational

A  Magyar Nemzeti Banknak intéz- kedéseket kell tenni a szektorspecifikus kockázatok (bank, biztosító, befektetési szolgáltató) értékelése érdekében, hogy a

We need the following theorem from the theory of lower bounds on linear forms in logarithms of algebraic numbers... The

Bus: This material type node represents the available bus fleet, the assigned parameter is the number of buses, i.e. Driver: This material type node represents the

–  VoIP and Brussels: push the anycast node to Russia, push Brussels. Node segment to Brussels Node segment

Fm calculating the node potentials of the model a topological formula can be given, so it is possible to use a purely topological method to determine the node

Node degree. The neighborhood structure N can be quantified. This gives the defi- nition of node degree, which is the number of edges adjacent to a node. In our case, this measures

BACKGROUND Focal atrial tachycardia (FAT) demonstrating earliest activation around the atrioventricular (AV) node during right atrial (RA) mapping has been eliminated by ablation at