[tickets] [opensaf:tickets] #2524 pyosaf: decorate function does not handle version struct in initialize functions

- **status**: unassigned --> accepted - **assigned_to**: Hieu Nguyen - **Comment**: In progress --- ** [tickets:#2524] pyosaf: decorate function does not handle version struct in initialize functions** **Status:** accepted **Milestone:** 5.17.10 **Created:** Thu Jul 06, 2017 01:44 PM UTC by

[tickets] [opensaf:tickets] #2524 pyosaf: decorate function does not handle version struct in initialize functions

- **status**: accepted --> review - **Comment**: Solution: + Backup current version in ERR_TRY_AGAIN case, and re-initialize with current version + Use initialize_decorate() function apply for all services in pyosaf utils --- ** [tickets:#2524] pyosaf: decorate function does not handle

[tickets] [opensaf:tickets] #1410 pyosaf: Invalid exception used in ImmObject (object.py)

- **status**: accepted --> review - **Comment**: Solution fix: + ImmObject use exceptions raise without NoneType --- ** [tickets:#1410] pyosaf: Invalid exception used in ImmObject (object.py)** **Status:** review **Milestone:** future **Created:** Fri Jul 10, 2015 10:11 AM UTC by Johan

[tickets] [opensaf:tickets] #1410 pyosaf: Invalid exception used in ImmObject (object.py)

- **Milestone**: future --> 5.17.10 --- ** [tickets:#1410] pyosaf: Invalid exception used in ImmObject (object.py)** **Status:** review **Milestone:** 5.17.10 **Created:** Fri Jul 10, 2015 10:11 AM UTC by Johan Mårtensson **Last Updated:** Tue Oct 03, 2017 03:58 AM UTC **Owner:** Hieu Nguyen

[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE

Another ticket #2602 related to support handle ERR_BAD_HANDLE case. It's propose support more error codes should be handled as well, NOT only ERR_BAD_HANDLE. It's not "This should be done automatically in the retry loop". Please contact who handle this ticket get more detail.

[tickets] [opensaf:tickets] #1410 pyosaf: Invalid exception used in ImmObject (object.py)

- **Type**: defect --> enhancement --- ** [tickets:#1410] pyosaf: Invalid exception used in ImmObject (object.py)** **Status:** review **Milestone:** 5.17.10 **Created:** Fri Jul 10, 2015 10:11 AM UTC by Johan Mårtensson **Last Updated:** Tue Oct 03, 2017 04:07 AM UTC **Owner:** Hieu Nguyen

[tickets] [opensaf:tickets] #1410 pyosaf: Invalid exception used in ImmObject (object.py)

- **Type**: enhancement --> defect --- ** [tickets:#1410] pyosaf: Invalid exception used in ImmObject (object.py)** **Status:** review **Milestone:** 5.17.10 **Created:** Fri Jul 10, 2015 10:11 AM UTC by Johan Mårtensson **Last Updated:** Tue Oct 17, 2017 02:16 AM UTC **Owner:** Hieu Nguyen

[tickets] [opensaf:tickets] #2533 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules

- **status**: assigned --> accepted --- ** [tickets:#2533] pyosaf: Make pyosaf:::immom::initialize() consistent with other modules** **Status:** accepted **Milestone:** 5.17.10 **Created:** Fri Jul 21, 2017 01:09 PM UTC by Anders Widell **Last Updated:** Mon Oct 02, 2017 06:30 AM UTC

[tickets] [opensaf:tickets] #2533 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules

- **status**: unassigned --> assigned - **assigned_to**: Hieu Nguyen - **Comment**: In progress --- ** [tickets:#2533] pyosaf: Make pyosaf:::immom::initialize() consistent with other modules** **Status:** assigned **Milestone:** 5.17.10 **Created:** Fri Jul 21, 2017 01:09 PM UTC by Anders

[tickets] [opensaf:tickets] #2533 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules

- **status**: accepted --> review - **Comment**: Solution fix: - Remove a preceding underscore character of the initialize method in immom - Does not automatically called initialize() when the module is implemented --- ** [tickets:#2533] pyosaf: Make pyosaf:::immom::initialize() consistent

[tickets] [opensaf:tickets] #1410 pyosaf: Invalid exception used in ImmObject (object.py)

- **status**: unassigned --> accepted - **assigned_to**: Hieu Nguyen - **Blocker**: --> False - **Comment**: In progress --- ** [tickets:#1410] pyosaf: Invalid exception used in ImmObject (object.py)** **Status:** accepted **Milestone:** future **Created:** Fri Jul 10, 2015 10:11 AM UTC by

[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE

- **status**: unassigned --> accepted - **assigned_to**: Hieu Nguyen - **Blocker**: --> False - **Milestone**: future --> 5.17.10 - **Comment**: In progress --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** accepted **Milestone:** 5.17.10

[tickets] [opensaf:tickets] #2523 pyosaf: IMM OM module initialized with ERR_BAD_HANDLE

Hi Zoran ! All functions in pyosaf utils decorate by decorate() function in pyosaf/utils/__init__.py. You can see in __init__.py of clm/immoi/immom/log/ntf same as below: saImmOmInitialize = decorate(saImmOm.saImmOmInitialize) saImmOmSelectionObjectGet =

[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE

Hi, According to Johan's idea: "This should be done automatically in the retry loop". I want make clearly about this: In BAD\_HANDLE case difference with TRY\_AGAIN case + TRY\_AGAIN is a simple case that's mean try to call current function agian. + BAD\_HANDLE have many complex cases. Example

[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE

- **status**: accepted --> wontfix - **Comment**: I set this ticket to "wontfix". If you have any comments, let me know ? --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** wontfix **Milestone:** 5.17.10 **Created:** Sun Dec 18, 2016 01:21 PM

[tickets] [opensaf:tickets] #2533 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules

- **status**: review --> fixed - **Comment**: commit dfb0d550adb44e148001beb5237559b3e472fd9c Author: Hieu Nguyen Date: Wed Oct 4 11:12:43 2017 +0700 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules [#2533] + Remove a preceding

[tickets] [opensaf:tickets] #2523 pyosaf: IMM OM module initialized with ERR_BAD_HANDLE

- **status**: accepted --> wontfix - **Comment**: I have been discuss with Zoran and set 'wontfix' to this ticket: - Hi Hieu, Just talked with a girl who was involved in raising this ticket, and she said that it's ok. So, you have ack from me on this. Thanks, Zoran - ---

[tickets] [opensaf:tickets] #2681 pyosaf: refactor IMM samples to use new pyosaf utils version 1.0.0

--- ** [tickets:#2681] pyosaf: refactor IMM samples to use new pyosaf utils version 1.0.0** **Status:** accepted **Milestone:** 5.18.01 **Created:** Wed Nov 15, 2017 03:27 AM UTC by Hieu Nguyen **Last Updated:** Wed Nov 15, 2017 03:27 AM UTC **Owner:** Hieu Nguyen 1/ Ticket

[tickets] [opensaf:tickets] #2683 pyosaf: refactor IMM utils

- **summary**: pyosaf: improve OI utils use a separate instance OM agent --> pyosaf: refactor IMM utils - Description has changed: Diff: --- old +++ new @@ -1 +1,2 @@ -Update the oi agent/implementer/applier to use a separate instance of om agent/accessor instead of using the immom and

[tickets] [opensaf:tickets] #2683 pyosaf: refactor IMM utils

- **status**: accepted --> review --- ** [tickets:#2683] pyosaf: refactor IMM utils** **Status:** review **Milestone:** 5.18.01 **Created:** Thu Nov 16, 2017 08:24 AM UTC by Hieu Nguyen **Last Updated:** Fri Dec 01, 2017 02:04 AM UTC **Owner:** Hieu Nguyen + Improve OI utils use a separate

[tickets] [opensaf:tickets] #2683 pyosaf: refactor IMM utils

- **status**: review --> fixed - **Comment**: commit 842cf55fc3d443998a30181ae944720201f98cec Author: Hieu Nguyen Date: Wed Nov 22 11:40:20 2017 +0700 pyosaf: refactor IMM utils [#2683] + improve OI utils use a separate instance OM agent + refactor