TLC_F2F_Phoenix_Ericsson - OpenSAF

scacchicgardenΛογισμικό & κατασκευή λογ/κού

13 Δεκ 2013 (πριν από 3 χρόνια και 7 μήνες)

116 εμφανίσεις













Slide title

In CAPITALS

50 pt




Slide subtitle

32 pt



TLC F2F Helsinki

Ericsson Status

Top right
corner for
field
-
mark,
customer or
partner logotypes.
See Best practice
for example.


Slide title

40 pt


Slide subtitle

24 pt



Text


24 pt

Bullets level 2
-
5

20 pt

Ericsson Confidential

TLC_F2F_Phoenix_Ericsson

2008
-
02
-
29

2

IMM Status


Targeting A.02.01 version for Release 3


Ported from OpenAIS to OpenSAF architecture


IMM working branch is published on devel server


All the CCB related APIs are now implemented.


Nearly all of the runtime APIs (object implementer) are now
implemented.


Some “major” remaining items:


Add continutiation support for admin operations


Startup& bootstrap (start before AMF)


Replicate IMMD using MBCSv


Garbage collect of continuations, connections etc.


Implement full CCB level persistence using SQLite


Testing of the existing IMM API


Top right
corner for
field
-
mark,
customer or
partner logotypes.
See Best practice
for example.


Slide title

40 pt


Slide subtitle

24 pt



Text


24 pt

Bullets level 2
-
5

20 pt

Ericsson Confidential

TLC_F2F_Phoenix_Ericsson

2008
-
02
-
29

3

IMM Overview


IMMSv designed as "Service Director" type service i.e. “3
-
tier”
architecture


The IMM "data base" containing the config data (and persistent or
cached runtime data) resides in the IMM Node Director (IMMND)
process and is replicated to every node. This optimizes for reads, at the
expense of writes (CCBs).


This structure also offloads the IMM Director (at the active controller)
from having to keep track of all the local agent connections (Object
management access and Object Implementers).


Any message that needs to go to all replicas, (IMMND), will have
following flow: IMMA
-
>IMMND
-
>IMMD
-
(mds broadcast)
-
>IMMND
-
(reply to origin)
-
>IMMA. An example would be any CCB related
operation.


A read/iteration of config data would simply be local: IMMA
-
>IMMND
-
>IMMA.


The central data model, that resides on the server side (in the IMMND)
is implemented in C++.


The IMMA and IMMD are pure C.

Top right
corner for
field
-
mark,
customer or
partner logotypes.
See Best practice
for example.


Slide title

40 pt


Slide subtitle

24 pt



Text


24 pt

Bullets level 2
-
5

20 pt

Ericsson Confidential

TLC_F2F_Phoenix_Ericsson

2008
-
02
-
29

4

IMM overview

Payload

2

Client

lib

Payload

3

Client

lib

MDS

Controller master

Controller

Standby

MBCSv

IMMND

IMMND

IMMD

IMMD

Payload

1

Client

lib

IMMND

Top right
corner for
field
-
mark,
customer or
partner logotypes.
See Best practice
for example.


Slide title

40 pt


Slide subtitle

24 pt



Text


24 pt

Bullets level 2
-
5

20 pt

Ericsson Confidential

TLC_F2F_Phoenix_Ericsson

2008
-
02
-
29

5

IMM questions


Any hints on anticipated characteristics requirements
could be important. The AMF IMM
-
model as defined by
the AMF standard apparently has a lot of cached
runtime attributes. These as well as regular config data
will be relatively expensive to update, since the imm
total replicates such data. Any guesses on volume of
data ? (number of records, avg size of record).

Top right
corner for
field
-
mark,
customer or
partner logotypes.
See Best practice
for example.


Slide title

40 pt


Slide subtitle

24 pt



Text


24 pt

Bullets level 2
-
5

20 pt

Ericsson Confidential

TLC_F2F_Phoenix_Ericsson

2008
-
02
-
29

6

NTF status


Existing A.01.01 implementation on OpenAIS


Admin part is implemented in C++


Porting work not started yet


Proposed 2
-
tier architecture (same as for Log and Eds service)


Version to be implemented A.02.02


Payload
1
Client
lib
Payload
2
Client
lib
MDS
Controller master
Controller
Standby
NTF
standby
NTF
master
MBCSv
admin
com
admin
com
Top right
corner for
field
-
mark,
customer or
partner logotypes.
See Best practice
for example.


Slide title

40 pt


Slide subtitle

24 pt



Text


24 pt

Bullets level 2
-
5

20 pt

Ericsson Confidential

TLC_F2F_Phoenix_Ericsson

2008
-
02
-
29

7

NTF, Questions


2
-
tier vs. 3
-
tier architecture. What are the pros and
cons based on experiances with current services?


Spec interpretation semantics: “If an implementation of
the Notification Service has one or more instances of
separate server processes, and one of them fails while
it is forwarding a notification to subscribers, the process
of forwarding is completed when this server process
has been either restarted or failed over to another
instance of the server process. Put in other words, the
notification will be forwarded to all subscribers even
though a server process fails in the middle of
forwarding the notification.“

Q: How transparent this needs to be to application?

Top right
corner for
field
-
mark,
customer or
partner logotypes.
See Best practice
for example.


Slide title

40 pt


Slide subtitle

24 pt



Text


24 pt

Bullets level 2
-
5

20 pt

Ericsson Confidential

TLC_F2F_Phoenix_Ericsson

2008
-
02
-
29

8