Summary: plm: fully support SC absence [#3093]
Review request for Ticket(s): 3093
Peer Reviewer(s): Mathi
Pull request to:
Affected branch(es): develop
Development branch: ticket-3093
Base revision: 95228b1a2a53e3b74c9a54f65e8b2345b8603582
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            n
 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):
---------------------------------------------
*** EXPLAIN/COMMENT THE PATCH SERIES HERE ***

revision aaad169319259dd15f03740e735ba228b90faea9
Author:Alex Jones <ajo...@rbbn.com>
Date:Wed, 16 Oct 2019 13:40:07 -0400

plm: fully support SC absence [#3093]

Add support to agent, plmd, and apitests to support SC absence.



Added Files:
------------
 src/plm/apitest/test_saPlmReadinessTrackResponse.cc
 src/plm/common/plms_common.h


Complete diffstat:
------------------
 src/plm/Makefile.am                                |   3 +-
 src/plm/agent/plma.h                               |  38 +-
 src/plm/agent/plma_api.cc                          | 710 +++++++++++++--------
 src/plm/agent/plma_init.cc                         |   7 +-
 src/plm/agent/plma_mds.cc                          | 170 ++++-
 src/plm/apitest/plmtest.c                          | 199 ++++++
 src/plm/apitest/plmtest.h                          |  32 +
 src/plm/apitest/test_saPlmDispatch.c               |  20 +-
 src/plm/apitest/test_saPlmEntityGroupAdd.c         | 126 ++--
 src/plm/apitest/test_saPlmEntityGroupCreate.c      |  26 +-
 src/plm/apitest/test_saPlmEntityGroupDelete.c      |  30 +-
 src/plm/apitest/test_saPlmEntityGroupRemove.c      | 162 ++---
 src/plm/apitest/test_saPlmFinalize.c               |  10 +-
 src/plm/apitest/test_saPlmInitialize.c             |  28 +-
 src/plm/apitest/test_saPlmReadinessTrack.c         | 628 +++++++++---------
 .../apitest/test_saPlmReadinessTrackResponse.cc    | 410 ++++++++++++
 src/plm/apitest/test_saPlmSelectionObjectGet.c     |  12 +-
 src/plm/common/plms.h                              |   7 -
 src/plm/common/plms_common.h                       |  57 ++
 src/plm/common/plms_common_mds.c                   |   2 +-
 src/plm/common/plms_common_utils.c                 |   1 +
 src/plm/common/plms_evt.h                          |   7 +-
 src/plm/plmd/plms_adm_fsm.c                        |   1 +
 src/plm/plmd/plms_mds.c                            |   1 +
 src/plm/plmd/plms_proc.c                           | 210 +++++-
 src/plm/plmd/plms_stdby.c                          |   1 +
 tools/cluster_sim_uml/archive/scripts/40opensaf.rc |  11 +-
 27 files changed, 2077 insertions(+), 832 deletions(-)


Testing Commands:
-----------------
1) setup SC absence
2) run plmtest
3) reboot SCs


Testing, Expected Results:
--------------------------
1) plmtest should pass


Conditions of Submission:
-------------------------
Oct 22, 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.


-----------------------------------------------------------------------------------------------------------------------
Notice: This e-mail together with any attachments may contain information of 
Ribbon Communications Inc. that
is confidential and/or proprietary for the sole use of the intended recipient.  
Any review, disclosure, reliance or
distribution by others or forwarding without express permission is strictly 
prohibited.  If you are not the intended
recipient, please notify the sender immediately and then delete all copies, 
including any attachments.
-----------------------------------------------------------------------------------------------------------------------

_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel

Reply via email to