Summary:amfd: support si-swap admin op for NplusM model [#2259]
Review request for Trac Ticket(s): #2259
Peer Reviewer(s): AMF devs
Pull request to: <<LIST THE PERSON WITH PUSH ACCESS HERE>>
Affected branch(es): ALL
Development branch: <<IF ANY GIVE THE REPO URL>>
--------------------------------
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 5fa5af5649bc85f45c9ba4e21b105002085a12e4
Author: Praveen Malviya <praveen.malv...@oracle.com>
Date: Tue, 21 Feb 2017 16:21:19 +0530
amfd: support si-swap admin op for NplusM model [#2259]
This version works for the case when all SIs which are active in the
designated SU (where SI to be swaped is active) have their standbys on
same
SU including the designated SI.
TODO: consider the case when active SIs of designated SU have their
standbys
on different SUs.
Complete diffstat:
------------------
src/amf/amfd/sg.cc | 12 ++++++-
src/amf/amfd/sg.h | 4 ++
src/amf/amfd/sg_npm_fsm.cc | 145
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------------
src/amf/amfd/su.cc | 11 ++++++
src/amf/amfd/su.h | 2 +
5 files changed, 144 insertions(+), 30 deletions(-)
Testing Commands:
-----------------
Tested in configuration attached in the ticket (test_conf.xml):
1)si-swap of without fault.
faults when si-swap is going on during HA state transition:
2)compfailover related su (timeout in callback):
-quiesced: PASS
-active: PAssed.
-standby: sg unstable (This needs tobe fixed).
3)compfailover non-related su (comp was killed):
-active faults: PASSED
-standby faults: PASSED
-quieced faults : PASSED
4)sufailover in non related SU (kill comp):
-quiesced: PASS
-active: PASS
-standby: PASS
5)sufailover in related su (kill comp):
-quiesced: PASS
-active: PASSED.
-standby: PASSED
Testing, Expected Results:
--------------------------
In case 2) minor fix is needed when standby comp faults with
comp-failover recovery in realign state. This could be a problem of FSM.
Need to check if some ticket already exists
All other cases passed.
Conditions of Submission:
-------------------------
Ack from reviewers.
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.
------------------------------------------------------------------------------
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
