Summary: plm: terminate child EEs when parent is terminated [#2572]
Review request for Ticket(s): 2572
Peer Reviewer(s): Mathi, Ravi
Pull request to:
Affected branch(es): develop
Development branch: ticket-2572
Base revision: bbb87e83e39c56f08f0b9fb7c5f8ad20dbf9a11a
Personal repository: git://git.code.sf.net/u/trguitar/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
Comments (indicate scope for each "y" above):
---------------------------------------------
revision 082672553bbb4aee4be18b25e12a867f2008e3ed
Author: Alex Jones <alex.jo...@genband.com>
Date: Fri, 10 Nov 2017 09:18:04 -0500
plm: terminate child EEs when parent is terminated [#2572]
If the hypervisor EE is terminated by shutting down plmcd on the host,
the child EEs (VMs) are not terminated and put into Uninstantiated
state. Then when plmcd is restarted on the host, the child VMs are not
started or restarted because PLM thinks they are instantiated.
Logic is wrong in plms_plmc_tcp_disconnect_process when checking for
child EEs.
Terminate child EEs when the host is terminated.
Complete diffstat:
------------------
src/plm/common/plms_utils.h | 2 +-
src/plm/plmd/plms_plmc.c | 6 ++----
src/plm/plmd/plms_utils.c | 4 ++--
3 files changed, 5 insertions(+), 7 deletions(-)
Testing Commands:
-----------------
1) Create a host EE and some child EEs.
2) shutdown plmcd on the host
Testing, Expected Results:
--------------------------
child EEs should go to Uninstantiated state
Conditions of Submission:
-------------------------
Nov 17, or ack from developer
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
