Summary: amfd: allow deletion of locked-in nodegroup [#1533]
Review request for Trac Ticket(s): #1533
Peer Reviewer(s): AMF contributors
Pull request to: <<LIST THE PERSON WITH PUSH ACCESS HERE>>
Affected branch(es): Default
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 6c0c194888c28f024147ccf0b46c0a9d5699bc26
Author: praveen.malv...@oracle.com
Date: Wed, 20 Jan 2016 15:22:52 +0530
amfd: allow deletion of locked-in nodegroup [#1533]
At present AMFD supports deletion of nodegroup in locked and unlocked
state.
This enhancement allows deletion of nodegroup in locked-in state with
other
criteria remaininig intact.
changeset 32d05ac6fa7d993d2538ab31d1e3edeca9b9952a
Author: praveen.malv...@oracle.com
Date: Wed, 20 Jan 2016 15:23:05 +0530
amfd: remove duplicate node_sus_termstate_set() and make it member
[#1533]
Complete diffstat:
------------------
osaf/services/saf/amf/amfd/include/node.h | 4 ++
osaf/services/saf/amf/amfd/node.cc | 8 ++--
osaf/services/saf/amf/amfd/nodegroup.cc | 111
+++++++++++++++++++++++++++++++++++++--------------------------
3 files changed, 73 insertions(+), 50 deletions(-)
Testing Commands:
-----------------
case a)
1)Bring amf_demo up.
2)Configure a nodegroup with SC-1 and SC-2 in nodelist.
3)lock and lock-in on nodegroup.
4)Delete nodegroup.
caseb)
In above case a), after step 3) unlock and unlock-in SC-2 and then delete ng.
Testing, Expected Results:
--------------------------
case a) deletion will be allowed and nodes will remain in lock-in state.
case b) deletion will be allowed and amf_demo will be instantiated and assigned
on SC-2.
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 ~/.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.
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
