[tickets] [opensaf:tickets] #2602 pyosaf: improvement of high level python interfaces

2017-10-27 Thread Zoran Milinkovic via Opensaf-tickets 
- **status**: review --> fixed
- **Comment**:

Pushed patches on behalf of Nguyen Luu

-

commit c10f21f5fd65b99d71dbe28b6345e65f4b8e518f
Author: Zoran Milinkovic 
Date:   Fri Oct 27 18:00:01 2017 +0200

pyosaf: High level python interfaces for IMM [#2602]

commit 426b7ae52778f24fc9cb1e9bdd0fca932b7cff70
Author: Zoran Milinkovic 
Date:   Fri Oct 27 18:00:01 2017 +0200

pyosaf: High level python interfaces for NTF [#2602]

Improve the implementation of NTF pyosaf utils

commit 5dde9242d5294f34af79c439308e0858bd17642c
Author: Zoran Milinkovic 
Date:   Fri Oct 27 18:00:01 2017 +0200

pyosaf: High level python interfaces for LOG [#2602]

Improved implementation of LOG pyosaf utils

commit b4612aff258fb3aa5cb876e3442e7c83dc2691a4
Author: Zoran Milinkovic 
Date:   Fri Oct 27 18:00:01 2017 +0200

pyosaf: High level python interfaces for CLM [#2602]

- Add more error handling
- Refactor clm code
- Keep raising exceptions for existing python methods
- Add __version__ attribute to utils




---

** [tickets:#2602] pyosaf: improvement of high level python interfaces**

**Status:** fixed
**Milestone:** 5.17.10
**Created:** Fri Sep 29, 2017 03:56 AM UTC by Long H Buu Nguyen
**Last Updated:** Mon Oct 23, 2017 12:14 PM UTC
**Owner:** Long H Buu Nguyen


There are high level python interfaces for some OpenSaf services (clm, imm, 
log, ntf) existing in pyosaf/utils. They already provides high level 
functionality. However, they are still simple and need to be improved for some 
aspects:
1) Error handling: decorate() function currently handles SA_AIS_ERR_TRY_AGAIN 
only. More error codes should be handled as well.
2) Versioning: add versioning so users can easily know which a version is 
better to use.
3) Support Python 3: Python 2.7 is mandatory, but 3.x must be considered. The 
compability should be kept.
4) Documentation: should have at least an instruction how to use the high level 
python interfaces.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2649 clm: add new admin operations to CLM

2017-10-27 Thread Zoran Milinkovic via Opensaf-tickets 
commit d8de354eb803664c7ad9389071f7be624b237aa9
Author: Zoran Milinkovic 
Date:   Fri Oct 27 17:25:59 2017 +0200

clm: fix for test.sh problem caused by patch for #2649 [#2649]


---

** [tickets:#2649] clm: add new admin operations to CLM**

**Status:** fixed
**Milestone:** 5.17.10
**Created:** Fri Oct 20, 2017 03:24 PM UTC by Zoran Milinkovic
**Last Updated:** Fri Oct 27, 2017 02:44 PM UTC
**Owner:** Zoran Milinkovic


Due to hard handling of executing scripts on remote nodes when user and 
password are required, CLM can be used for remote executing of scripts.

The admin operation "immadm -o 4 ..." will be extended in the way that when CLM 
node DN is targeted object, the CLM node will be rebooted.
In example if SC-2 needs to be rebooted:
immadm -o 4 safNode=SC-2,safCluster=myClmCluster

Another admin operation "immadm -o 5 ..." will be a more generic admin 
operation and it will execute scripts stored in "scripts/clm" directory. The 
scripts will be prefixed with osafclm_ word.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2649 clm: add new admin operations to CLM

2017-10-27 Thread Zoran Milinkovic via Opensaf-tickets 
- **status**: review --> fixed
- **Comment**:

commit 864c0da8d303f420cdb86e3390f239d20ab9801c
Author: Zoran Milinkovic 
Date:   Fri Oct 27 16:41:21 2017 +0200

clm: add new admin operations [#2649]

Add two new admin operations to CLM.
1. Node reboot will use the same openation id as cluster reboot, but the DN 
will contain CLM node

   Example for rebooting SC2:
 immadm -o 4 safNode=SC-2,safCluster=myClmCluster

2. Execute action on remote nodei(s) with operation id 5.
   Action is a script stored in /usr/lib/opensaf/clm-scripts directory 
started with prefix "osafclm_"
   The action name needs to be provided by saClmAction parameter, which is 
type of SaStringT.
   If the targeted DN is CLM node, the action will be done on the node.
   If the targeted DN is CLM cluster DN, the action will be done on all 
nodes in the cluster.

   Example for executing clm-scripts/osafclm_stop script on SC-2:
 immadm -o 5 -p saClmAction:SA_STRING_T:stop 
safNode=SC-2,safCluster=myClmCluster

   Example for executing clm-scripts/osafclm_stop script on all nodes:
 immadm -o 5 -p saClmAction:SA_STRING_T:stop safCluster=myClmCluster




---

** [tickets:#2649] clm: add new admin operations to CLM**

**Status:** fixed
**Milestone:** 5.17.10
**Created:** Fri Oct 20, 2017 03:24 PM UTC by Zoran Milinkovic
**Last Updated:** Mon Oct 23, 2017 02:47 PM UTC
**Owner:** Zoran Milinkovic


Due to hard handling of executing scripts on remote nodes when user and 
password are required, CLM can be used for remote executing of scripts.

The admin operation "immadm -o 4 ..." will be extended in the way that when CLM 
node DN is targeted object, the CLM node will be rebooted.
In example if SC-2 needs to be rebooted:
immadm -o 4 safNode=SC-2,safCluster=myClmCluster

Another admin operation "immadm -o 5 ..." will be a more generic admin 
operation and it will execute scripts stored in "scripts/clm" directory. The 
scripts will be prefixed with osafclm_ word.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2658 amfnd: segv in ncs_tmr_stop

2017-10-27 Thread Hans Nordebäck via Opensaf-tickets 



---

** [tickets:#2658] amfnd: segv in ncs_tmr_stop**

**Status:** review
**Milestone:** 5.17.10
**Created:** Fri Oct 27, 2017 02:40 PM UTC by Hans Nordebäck
**Last Updated:** Fri Oct 27, 2017 02:40 PM UTC
**Owner:** Hans Nordebäck


amfnd segv in ncs_tmr_stop called from avnd_di_msg_ack_process() due to that 
the dnd_list vector is updated during iteration in the context of calling 
function avnd_last_step_clean(). A patch is sent out that uses a local copy of 
the dnd_list during iteration, but the patch do not handle the modification to 
dnd_list in the context of of calling function avnd_last_step_clean(), these 
updates will be lost and this problem has to be investigated in a separate 
ticket. 


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2655 msg: APIs do not return UNAVAILABLE after node has left and rejoined

2017-10-27 Thread Alex Jones via Opensaf-tickets 
- **status**: assigned --> review



---

** [tickets:#2655] msg: APIs do not return UNAVAILABLE after node has left and 
rejoined**

**Status:** review
**Milestone:** 5.17.10
**Created:** Wed Oct 25, 2017 03:15 PM UTC by Alex Jones
**Last Updated:** Wed Oct 25, 2017 03:15 PM UTC
**Owner:** Alex Jones


According to Section 3.2.1 of the MSG B.03.01 spec, the API calls must still 
return UNAVAILABLE for handles which were obtained before the node left the 
cluster, even after the node rejoins.

The implementation currently only returns UNAVAILABLE during the time the node 
is not a member.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2638 dtm: Use multiple backup files when rotating log files

2017-10-27 Thread Anders Widell via Opensaf-tickets 
- **status**: review --> fixed
- **Comment**:

commit 2a7a20bafa7f189fca79bd73e6d678c58fda64dd (HEAD -> ticket-2638)
Author: Anders Widell 
Date:   Thu Oct 26 16:58:50 2017 +0200

dtm: Use multiple backup files when rotating trace log files [#2638]

To increase the amount of trace data that is kept on disk, OpenSAF trace 
files
now have nine backup files, named .1 to .9, instead of just one single 
backup
file. The MDS log still has one single backup file, as before.




---

** [tickets:#2638] dtm: Use multiple backup files when rotating log files**

**Status:** fixed
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 10:15 AM UTC by Anders Widell
**Last Updated:** Thu Oct 26, 2017 03:17 PM UTC
**Owner:** Anders Widell


Currently, only one backup file is used when rotating log files. This may be 
insufficient when the internal log server is used for trace, and the suggestion 
is to use multiple backup files (.1, .2, .3 ... .9)


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2590 CLM: Add user data in CLMSV_CLUSTER_JOIN_REQ message

2017-10-27 Thread Hans Nordebäck 
- **status**: review --> fixed
- **Comment**:

commit 1c80cb072946a64964ba613ca3def35bbe911625
Author: Hans Nordeback 
Date:   Wed Oct 11 08:57:26 2017 +0200

clm: Add user data in CLMSV_CLUSTER_JOIN_REQ message V2 [#2590]




---

** [tickets:#2590] CLM: Add user data in CLMSV_CLUSTER_JOIN_REQ message**

**Status:** fixed
**Milestone:** 5.17.10
**Created:** Fri Sep 22, 2017 11:40 AM UTC by Hans Nordebäck
**Last Updated:** Mon Sep 25, 2017 02:33 PM UTC
**Owner:** Hans Nordebäck


To join the clm cluster a CLMSV_CLUSTER_JOIN_REQ message is sent to clms. The 
message contains a node name read from file "node_name". The node name is e.g. 
passed on to the opensaf_scale_out script. To also send user data to the 
opensaf_scale_out script an additional file "user_data" is created and data can 
be added. The use case for this is e.g. sending software package version data, 
etc. for additional validation in the opensaf_scale_out script.  


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2599 imm: remove cascading delete for runtime objects

2017-10-27 Thread Zoran Milinkovic via Opensaf-tickets 
- **summary**: smf: remove cascading delete for runtime objects --> imm: remove 
cascading delete for runtime objects
- **status**: unassigned --> accepted
- **assigned_to**: Rafael Odzakow --> Zoran Milinkovic
- **Type**: discussion --> enhancement
- **Component**: smf --> imm
- **Part**: d --> -
- **Priority**: minor --> major
- **Milestone**: 5.17.10 --> future
- **Comment**:

Due to a short time for testing, the new soultion for handling large amount of 
cascade delete in IMM will be postponed to the next release.



---

** [tickets:#2599] imm: remove cascading delete for runtime objects**

**Status:** accepted
**Milestone:** future
**Created:** Wed Sep 27, 2017 12:01 PM UTC by Rafael Odzakow
**Last Updated:** Wed Sep 27, 2017 12:03 PM UTC
**Owner:** Zoran Milinkovic


Investigation needed. There is a lot of log spam on large installations when 
deleting these objects. It could be caused by SMF deleting individual elements 
instead of a parent root.

Posted by Zoran from IMM:

> The problem comes with cascade delete of SMF objects which contain many 
> thousand objects.
> When cascade delete is invoked, it shouldn't be deleted more than 1 
> objects at once.
> 
> All this is explained in IMM PR document, chapter 3.4, point 6.
> https://sourceforge.net/p/opensaf/documentation/ci/default/tree/OpenSAF_IMMSv_PR.odt
> 
> Adding Rafael Odzakow


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets