Summary: AMF: Use IMM applier in the AMF node director V2 [#819] Review request for Trac Ticket(s): #819 Peer Reviewer(s): HansF, Nagu, Praveen Pull request to: Affected branch(es): default Development branch: default
-------------------------------- 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): --------------------------------------------- <<EXPLAIN/COMMENT THE PATCH SERIES HERE>> changeset f4c25e906973af428a4b3d70be65ce717f84bd54 Author: Hans Nordeback <[email protected]> Date: Thu, 22 May 2014 14:55:40 +0200 AMF: Use IMM applier in the AMF node director V2 [#819] This first patch adds support for changing attributes in class SaAmfHealthcheckType Added Files: ------------ osaf/services/saf/amf/amfnd/imm.cc osaf/services/saf/amf/amfnd/include/avnd_imm.h Complete diffstat: ------------------ osaf/libs/common/amf/include/amf_defs.h | 6 + osaf/services/saf/amf/amfnd/Makefile.am | 1 + osaf/services/saf/amf/amfnd/evt.cc | 7 + osaf/services/saf/amf/amfnd/hcdb.cc | 159 +++++++++++++++++++ osaf/services/saf/amf/amfnd/imm.cc | 765 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ osaf/services/saf/amf/amfnd/include/Makefile.am | 1 + osaf/services/saf/amf/amfnd/include/avnd.h | 1 + osaf/services/saf/amf/amfnd/include/avnd_evt.h | 8 + osaf/services/saf/amf/amfnd/include/avnd_hc.h | 1 + osaf/services/saf/amf/amfnd/include/avnd_imm.h | 136 ++++++++++++++++ osaf/services/saf/amf/amfnd/main.cc | 10 +- 11 files changed, 1094 insertions(+), 1 deletions(-) Testing Commands: ----------------- Run AmfDemo app and: amf-adm unlock-in safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 amf-adm unlock-in safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 amf-adm unlock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 amf-adm unlock safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 immcfg -a saAmfHctDefPeriod=20000000000 safHealthcheckKey=AmfDemo,safVersion=1,safCompType=AmfDemo1 and health check period is changed to 20 seconds: May 22 14:49:06 SC-1 user.debug amf_demo[639]: Health check 4 May 22 14:49:26 SC-1 user.debug amf_demo[639]: Health check 5 verify imm with: immlist safHealthcheckKey=AmfDemo,safVersion=1,safCompType=AmfDemo1 Testing, Expected Results: -------------------------- see above. 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. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
