Summary: amfd: update SI assignment state when SU is added or removed [#2269] Review request for Ticket(s): 2269 Peer Reviewer(s): AMF devs Pull request to: *** LIST THE PERSON WITH PUSH ACCESS HERE *** Affected branch(es): develop, releae Development branch: ticket-2269 Base revision: 2b65ecdaac6d0b80073149f137b0744aeeb6582b Personal repository: git://git.code.sf.net/u/userid-2226215/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 c89b32698927532beab5f3e71fae3115f31ae3ce Author: Gary Lee <[email protected]> Date: Fri, 1 Sep 2017 13:50:06 +1000 amfd: update SI assignment state when SU is added or removed [#2269] Complete diffstat: ------------------ src/amf/amfd/sg.cc | 5 +++++ src/amf/amfd/su.cc | 6 ++++++ 2 files changed, 11 insertions(+) Testing Commands: ----------------- Modify AppConfig-nwayactive.xml: saAmfSIPrefActiveAssignments=0 saAmfSGNumPrefInserviceSUs=0 saAmfSGNumPrefAssignedSUs=0 Unlock / Unlock-in SUs Delete SU1: amf-adm lock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo2 amf-adm lock-in safSu=SU1,safSg=AmfDemo,safApp=AmfDemo2 immcfg -d safSu=SU1,safSg=AmfDemo,safApp=AmfDemo2 Check assignment state of safSi=AmfDemo,safApp=AmfDemo2 == assigned Add SU1 back Check assignment state of safSi=AmfDemo,safApp=AmfDemo2 == partially assigned Unlock / Unlock-in SU1 Check assignment state of safSi=AmfDemo,safApp=AmfDemo2 == assigned Testing, Expected Results: -------------------------- See above 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 ~/.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 [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
