OpenSAF / Tickets / #1535 imm: class and object applier set should be only on local immnd

#1535 imm: class and object applier set should be only on local immnd

Milestone: 5.0.FC

Status: fixed

Owner: Zoran Milinkovic

Labels: None

Type: enhancement

Component: imm

Part: -

Version:

Priority: major

Blocker:

Updated: 2016-01-25

Created: 2015-10-09

Creator: Zoran Milinkovic

Private: No

Information where applier is set (on classes or objects) should be only stored on the originating node where the applier is set.

Today, object and class applier set, using saImmOiObjectImplementerSet() and saImmOiClassImplementerSet(), is done over fevs, and this information is stored on all nodes. Newly synced node does not have information where the applier is set.
Detaching the applier from the originating node and attaching to the new node may have different attached objects and classes then attaching the applier again to the originating node or some veteran node.
This means that if the applier is set to a new object or class, it may get different callbacks on veteran nodes (including the originating node) and new nodes.

Appliers are weak, and applications must set applier again to objects and classes after applier is set by saImmOiImplementerSet().

Applier bindings are only of interest on the local node. Object and class applier bindings are not of interest for remote nodes.

This patch should make object and class applier set info consistent per node.
This means that applier set (saImmOiImplementerSet() ) will bind objects and classes that have alredy been bound on the local node by the same applier name.

Applier set (using saImmOiImplementerSet() ) will work as it works today. Applier name and applier id will be stored on all nodes.
Object and class applier set (using saImmOiObjectImplementerSet() and saImmOiClassImplementerSet() ) will only be done on local immnd, and will not be sent to all nodes like it works today.

Description has changed:

Diff:

--- old
+++ new
@@ -1,8 +1,15 @@
-Information where applier is set (classes or objects) should be only stored on the originating node where the applier is set.
+Information where applier is set (on classes or objects) should be only stored on the originating node where the applier is set.

-Today, object and class applier set is done over fevs, and this information is stored on all nodes. Newly synced node does not have information where the applier is set.
-Detaching the applier from the originating node and attaching to the new node may have have different behavior then attaching the applier again to the originating node or some veteran node.
+Today, object and class applier set, using saImmOiObjectImplementerSet() and saImmOiClassImplementerSet(), is done over fevs, and this information is stored on all nodes. Newly synced node does not have information where the applier is set.
+Detaching the applier from the originating node and attaching to the new node may have different attached objects and classes then attaching the applier again to the originating node or some veteran node.
 This means that if the applier is set to a new object or class, it may get different callbacks on veteran nodes (including the originating node) and new nodes.

-Appliers are only of interest on the local node. Where applier is set (object or class) is not of interest for remote nodes. 
-Object/class applier set should be stored locally.
+Appliers are weak, and applications must set applier again to objects and classes after applier is set by saImmOiImplementerSet().
+
+Applier bindings are only of interest on the local node. Object and class applier bindings are not of interest for remote nodes. 
+
+This patch should make object and class applier set info consistent per node.
+This means that applier set (saImmOiImplementerSet() ) will bind objects and classes that have alredy been bound on the local node by the same applier name.
+
+Applier set (using saImmOiImplementerSet() ) will work as it works today. Applier name and applier id will be stored on all nodes.
+Object and class applier set (using saImmOiObjectImplementerSet() and saImmOiClassImplementerSet() ) will only be done on local immnd, and will not be sent to all nodes like it works today.

status: unassigned --> accepted
assigned_to: Zoran Milinkovic

Zoran Milinkovic - 2015-11-04

https://sourceforge.net/p/opensaf/mailman/message/34593252/

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Zoran Milinkovic - 2015-11-04

status: accepted --> review
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Zoran Milinkovic - 2015-12-08

status: review --> accepted
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Zoran Milinkovic - 2016-01-11

status: accepted --> review
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Zoran Milinkovic - 2016-01-11

https://sourceforge.net/p/opensaf/mailman/message/34756489/

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Zoran Milinkovic - 2016-01-25

status: review --> fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Zoran Milinkovic - 2016-01-25

default(5.0):

changeset: 7260:ac528ebb3340
tag: tip
parent: 7258:bc2ef6906c3e
user: Zoran Milinkovic zoran.milinkovic@ericsson.com
date: Mon Jan 11 16:30:03 2016 +0100
summary: imm: save class and object applier bindings only on local node [#1535]

Related

Tickets: ~~#1535~~

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

imm: class and object applier set should be only on local immnd

Milestone

Searches

Help

#1535 imm: class and object applier set should be only on local immnd

Related

Discussion

Related