Summary: amfd: maintain node attributes in imm job queue at standby [#2494]
Review request for Ticket(s): 2494
Peer Reviewer(s): AMF devs
Pull request to: Myself
Affected branch(es): develop
Development branch: ticket-2494
Base revision: da08a820a03d8bf6b3ea35bf318a207eba57356f
Personal repository: git://git.code.sf.net/u/praveenmalviya/review
--------------------------------
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
NOTE: Patch(es) contain lines longer than 80 characers
Comments (indicate scope for each "y" above):
---------------------------------------------
revision 6be13bcf35f383e1f59ef600d10490e1b66ac48b
Author: Praveen <praveen.malv...@oracle.com>
Date: Mon, 19 Jun 2017 14:40:54 +0530
amfd: maintain node attributes in imm job queue at standby [#2494]
In reported problem, active AMFD checkpointed admin state of node to
standby AMFD, but it could not update it to IMM before leaving cluster.
Since standby AMFD does not maintain Node attributes in IMM job queue, it also
does not update it to IMM. Hence user does not see updated admin state of node.
Currently standby AMFD maintains attributes of only SU, SI, CSI and comp in
imm job queue.
With this patch, standby AMFD will now maintain node attributes in imm job
queue at standby. Now in failover situations, standby will update latest states
of node in imm.
Complete diffstat:
------------------
src/amf/amfd/ckpt_dec.cc | 6 ++++++
src/amf/amfd/ckpt_updt.cc | 5 +++++
src/amf/amfd/imm.cc | 31 ++++++++++++++++++++++++++++++-
src/amf/amfd/imm.h | 1 +
4 files changed, 42 insertions(+), 1 deletion(-)
Testing Commands:
-----------------
Testing command given in the comment.
Testing, Expected Results:
--------------------------
After failover correct states are shown.
Conditions of Submission:
-------------------------
Ack from any reviewer.
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 ~/.gitconfig file (i.e. user.name, user.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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
