Summary: imm: synchronize applier set on all nodes [#1504]
Review request for Trac Ticket(s): 1504
Peer Reviewer(s): Neelakanta, Anders, Hung
Pull request to: Zoran
Affected branch(es): opensaf-4.5.x, opensaf-4.6.x, default(4.7)
Development branch: default(4.7)
--------------------------------
Impacted area Impact y/n
--------------------------------
Docs n
Build system n
RPM/packaging n
Configuration files n
Startup scripts n
SAF services y
OpenSAF services n
Core libraries n
Samples n
Tests n
Other n
Comments (indicate scope for each "y" above):
---------------------------------------------
changeset 729bbefd27e12662828825e50b0df14cab5419c5
Author: Zoran Milinkovic <zoran.milinko...@ericsson.com>
Date: Tue, 06 Oct 2015 16:15:39 +0200
imm: synchronize applier set on all nodes [#1504]
In the first request of OiImplementerSet, from library to IMMND, a
pre-check
is added for checking if the applier can be set on a class or an
object. The
pre-check will improve response and skip sending the message over fevs,
if
the applier cannot be set to the class or the object.
If the pre-check is successful, then it might be a short time frame that
applier set can still fail until the message sent over fevs reach all
nodes.
If applier set fails at this point, discard implementer message will be
sent
to all nodes.
Complete diffstat:
------------------
osaf/services/saf/immsv/immnd/ImmModel.cc | 44
++++++++++++++++++++++++++++++++++++++++++++
osaf/services/saf/immsv/immnd/immnd_evt.c | 7 +++++--
2 files changed, 49 insertions(+), 2 deletions(-)
Testing Commands:
-----------------
Testing, Expected Results:
--------------------------
Test the case explained in the ticket
Conditions of Submission:
-------------------------
Ack from Neelakanta, Hung, Anders
Arch Built Started Linux distro
-------------------------------------------
mips n n
mips64 n n
x86 n n
x86_64 n n
powerpc n n
powerpc64 n n
Reviewer Checklist:
-------------------
[Submitters: make sure that your review doesn't trigger any checkmarks!]
Your checkin has not passed review because (see checked entries):
___ Your RR template is generally incomplete; it has too many blank entries
that need proper data filled in.
___ You have failed to nominate the proper persons for review and push.
___ Your patches do not have proper short+long header
___ You have grammar/spelling in your header that is unacceptable.
___ You have exceeded a sensible line length in your headers/comments/text.
___ You have failed to put in a proper Trac Ticket # into your commits.
___ You have incorrectly put/left internal data in your comments/files
(i.e. internal bug tracking tool IDs, product names etc)
___ You have not given any evidence of testing beyond basic build tests.
Demonstrate some level of runtime or other sanity testing.
___ You have ^M present in some of your files. These have to be removed.
___ You have needlessly changed whitespace or added whitespace crimes
like trailing spaces, or spaces before tabs.
___ You have mixed real technical changes with whitespace and other
cosmetic code cleanup changes. These have to be separate commits.
___ You need to refactor your submission into logical chunks; there is
too much content into a single commit.
___ You have extraneous garbage in your review (merge commits etc)
___ You have giant attachments which should never have been sent;
Instead you should place your content in a public tree to be pulled.
___ You have too many commits attached to an e-mail; resend as threaded
commits, or place in a public tree for a pull.
___ You have resent this content multiple times without a clear indication
of what has changed between each re-send.
___ You have failed to adequately and individually address all of the
comments and change requests that were proposed in the initial review.
___ You have a misconfigured ~/.hgrc file (i.e. username, email etc)
___ Your computer have a badly configured date and time; confusing the
the threaded patch review.
___ Your changes affect IPC mechanism, and you don't present any results
for in-service upgradability test.
___ Your changes affect user manual and documentation, your patch series
do not contain the patch that updates the Doxygen manual.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
