Summary: pyosaf: (updated) Add parameter to Ccb constructor to set exact CCB
flags [#1417]
Review request for Trac Ticket(s): #1417
Peer Reviewer(s): hans.nordeb...@ericsson.com,
anders.bjornerst...@ericsson.com, mathi.naic...@oracle.com,
hung.d.ngu...@dektech.com.au, srikanth.revan...@oracle.com
Pull request to: anders.bjornerst...@ericsson.com
Affected branch(es): 4.7.x
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 n
OpenSAF services n
Core libraries n
Samples n
Tests n
Other y
Comments (indicate scope for each "y" above):
---------------------------------------------
Updated version that adds the SA_IMM_CCB_ALLOW_NULL_OI based on Hung Nguyen's
recommendation.
changeset 2ce5fae6bf8d0c5abaa602595384b9ac90720ee0
Author: Johan Mårtensson <johan.o.martens...@ericsson.com>
Date: Thu, 16 Jul 2015 14:25:08 +0200
pyosaf: (updated) Add parameter to Ccb constructor to set exact CCB
flags
[#1417]
Add a flags parameter that lets the user override the default flags for
the
Ccb flags. The default SA_IMM_CCB_REGISTERED_OI is still kept.
Also step the imm om version to A.2.15 to enable the
SA_IMM_CCB_ALLOW_NULL_OI flag and add it in saImm.py.
Verify like this:
- Kill an OI
- Delete one of the OI's instances:
from pyosaf.utils.immom.ccb import Ccb
cb = Ccb(flags=None)
ccb.delete(<instance-dn>)
ccb.apply()
Complete diffstat:
------------------
python/pyosaf/saImm.py | 1 +
python/pyosaf/utils/immom/__init__.py | 2 +-
python/pyosaf/utils/immom/ccb.py | 9 ++++++---
3 files changed, 8 insertions(+), 4 deletions(-)
Testing Commands:
-----------------
Follow the steps in the commit message to verify.
Testing, Expected Results:
--------------------------
<<PASTE COMMAND OUTPUTS / TEST RESULTS>>
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 n n
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.
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
