Summary: fm: Add support for STONITH fencing
Review request for Trac Ticket(s): #1859
Peer Reviewer(s): Praveen, Ramesh, Mathi, AndersW
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 n
OpenSAF services n
Core libraries y
Samples n
Tests n
Other n
Comments (indicate scope for each "y" above):
---------------------------------------------
Support for self-fencing and remote-fencing added.
changeset 9091e8629b45911cb2d7797dea7de4d6d14abd5b
Author: Anders Widell <anders.wid...@ericsson.com>
Date: Tue, 21 Jun 2016 09:49:23 +0200
fm: Add support for self-fencing [#1859]
In situations where remote fencing is not possible, this patch adds
support
for self-fencing.
changeset 70016ded77ee636f4e406dadfc4ea431cd81f1bd
Author: Hans Nordeback <hans.nordeb...@ericsson.com>
Date: Tue, 21 Jun 2016 09:40:03 +0200
fm: Add support for remote fencing using STONITH [#1859]
Complete diffstat:
------------------
00-README.conf | 47 ++++++++
osaf/services/infrastructure/fm/config/fmd.conf | 9 +-
osaf/services/infrastructure/fm/fms/Makefile.am | 3 +-
osaf/services/infrastructure/fm/fms/fm_cb.h | 14 ++
osaf/services/infrastructure/fm/fms/fm_main.c | 132 +++++++++++++++++++++++-
osaf/services/infrastructure/fm/fms/fm_mds.c | 51 +++++++++
scripts/opensaf_reboot | 47 ++++++--
7 files changed, 284 insertions(+), 19 deletions(-)
Testing Commands:
-----------------
Configure the system according to 00-README.conf file. E.g tipc-config -bd
eth:eth0 on
the Standby controller should trigger a remote fencing, if configured.
More test commands will be added.
Testing, Expected Results:
--------------------------
Split-brains should be handled with either self-fencing or remote-fencing.
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.
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
