Summary: smfd: add support for detection of asynchronous failures of AMF
entities
Review request for Trac Ticket(s): 2145
Peer Reviewer(s): Neel, Lennart, Rafael
Pull request to:
Affected branch(es): default
Development branch:
--------------------------------
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):
---------------------------------------------
This patch supersedes the previous one, and contains refactored NTF
notification code.
changeset efb3cf9f38697da1a4ed4871d31990caeda0732c
Author: Alex Jones <ajo...@genband.com>
Date: Fri, 11 Nov 2016 14:42:52 -0500
smfd: add support for asynchronous detection of failed AMF entities
[#2145]
This patch adds support for section 4.2.1.3 of SMF A.01.02 spec.
Complete diffstat:
------------------
osaf/services/saf/smfsv/smfd/SmfCampaignThread.cc | 235 +++++++++++++++++++++-
osaf/services/saf/smfsv/smfd/SmfCampaignThread.hh | 15 +
osaf/services/saf/smfsv/smfd/SmfStepTypes.cc | 32 +-
3 files changed, 263 insertions(+), 19 deletions(-)
Testing Commands:
-----------------
1) run a campaign
2) after one of the SUs has been upgraded, kill a component in that SU
Testing, Expected Results:
--------------------------
1) campaign should go to "suspended by error detected" state, and failed SU
should be listed in saSmfCmpgError
Conditions of Submission:
-------------------------
<<HOW MANY DAYS BEFORE PUSHING, CONSENSUS ETC>>
Arch Built Started Linux distro
-------------------------------------------
mips n n
mips64 n n
x86 n n
x86_64 y y
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.
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
