[tickets] [opensaf:tickets] #2126 smf: balanced upgrade, no activation/deactivation done

[elunlen]

- **status**: assigned --> review



---

** [tickets:#2126] smf: balanced upgrade, no activation/deactivation done**

**Status:** review
**Milestone:** 5.1.1
**Created:** Wed Oct 19, 2016 11:31 AM UTC by Rafael
**Last Updated:** Wed Oct 19, 2016 11:31 AM UTC
**Owner:** Rafael


During balanced upgrade it was observed that a software bundle was unable to be 
deleted from IMM. Looking in the saLog a message saying "admin state is not 
locked instantiaion" shows that no deactivation/activation was not done for the 
node.


---

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.--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1531 LOG: Introduce an dedicated IMM OiHandler handler thread

[elunlen]

- Description has changed:

Diff:



--- old
+++ new
@@ -1,3 +1,7 @@
-Setting up IMM Object Implementer (OI) is not handled in a correct and 
consistent way. There is also a lot of redundant code. In some places (but not 
everywhere)  a thread is used to prevent the main thread from ‘hanging’ a long 
time but this is done in an incorrect way. See also ticket [#1527]
+Setting up IMM Object Implementer (OI) is not handled in a correct and 
consistent way. There is also a lot of redundant code. In some places (but not 
everywhere) a thread is used to prevent the main thread from ‘hanging’ a long 
time but this is done in an incorrect way. See also ticket [#1527]
 
-This ticket is going to introduce an dedicated thread for IMM OiHandler. Any 
other thread wants to perform on the IMM OiHandler, must send requests to this 
dedicated thread. Refer to the ticket [#1609].
+Handle all OI functionality in a separate thread including a poll loop for 
callback handling, recovery of IMM handles etc. Today all of this is done in 
the main thread except recovery of IMM handles.
+Use a mailbox to communicate with other threads (main thread). Encapsulate 
communication in C++ interface. Do not handle client/stream database in the OI 
thread. This includes the runtime objects for streams. If for example a runtime 
attribute value is requested the OI shall ask for the value via the interface. 
Also other changes and settings shall be handled this way.
+Do not handle any check-pointing (msb) in the OI thread
+
+It is recommended that ticket [#2149] log: Create a C++ wrapper for handling 
IMM api is implemented first






---

** [tickets:#1531] LOG: Introduce an dedicated IMM OiHandler handler thread**

**Status:** assigned
**Milestone:** 5.0.FC
**Created:** Thu Oct 08, 2015 11:14 AM UTC by elunlen
**Last Updated:** Thu Jul 14, 2016 03:44 AM UTC
**Owner:** Vu Minh Nguyen


Setting up IMM Object Implementer (OI) is not handled in a correct and 
consistent way. There is also a lot of redundant code. In some places (but not 
everywhere) a thread is used to prevent the main thread from ‘hanging’ a long 
time but this is done in an incorrect way. See also ticket [#1527]

Handle all OI functionality in a separate thread including a poll loop for 
callback handling, recovery of IMM handles etc. Today all of this is done in 
the main thread except recovery of IMM handles.
Use a mailbox to communicate with other threads (main thread). Encapsulate 
communication in C++ interface. Do not handle client/stream database in the OI 
thread. This includes the runtime objects for streams. If for example a runtime 
attribute value is requested the OI shall ask for the value via the interface. 
Also other changes and settings shall be handled this way.
Do not handle any check-pointing (msb) in the OI thread

It is recommended that ticket [#2149] log: Create a C++ wrapper for handling 
IMM api is implemented first


---

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.--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2149 log: Create a C++ wrapper for handling IMM api

[elunlen]

---

** [tickets:#2149] log: Create a C++ wrapper for handling IMM api**

**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Fri Oct 28, 2016 12:25 PM UTC by elunlen
**Last Updated:** Fri Oct 28, 2016 12:25 PM UTC
**Owner:** nobody


Create a wrapper for IMM API handling and replace all usage of current immutil.c
This wrapper must not contain anything that is directly related to the log 
service. The purpose is to simplify handling of IMM APIs e.g. simplify the 
complicated void pointer handling used with the IMM C APIs.
This wrapper can be limited to implement only what’s needed for the log service 
but the design shall make it possible to add more functionality. The goal is to 
create a generic C++ immutil to be used with all services and this log service 
immutil could be the start of that



---

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.--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2148 log: Refactor handling of writing log records

[elunlen]

---

** [tickets:#2148] log: Refactor handling of writing log records**

**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Fri Oct 28, 2016 12:08 PM UTC by elunlen
**Last Updated:** Fri Oct 28, 2016 12:08 PM UTC
**Owner:** nobody


Refactor handling for saving log records
How log records are written is of no interest in the rest of the log service so 
a common api for saving log records could be used. This api only have to 
receive a formatted log record string, the log stream identity and return 
information whether it succeeded or not. A setting api at this level may be 
needed if log records can be written in several ways. The setting could then be 
whether the log records shall be written to file only or to both file and/or 
someplace else etc.
Encapsulate all handling of the actual writing to file. This handling includes 
file rotation, .cfg file handling etc. The existing file I/O thread can be 
removed if this handling is done in a separate thread. This handling is also 
dependent on some settings e.g. path to directory where log file shall be 
written, changes of format string (.cfg file has to be updated). A separate 
settings api for settings must be defined. For writing log records the common 
api shall be used
If other handling for writing log records shall be added also that 
implementation shall be encapsulated in a similar manner.  May also need a 
settings api but for writing log records the common api shall be used.



---

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.--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1923 base: syslog filled with warning messages when running OpenSAF commands

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8266:754bf0dd26ec
branch:  opensaf-5.0.x
parent:  8262:b5ead5296149
user:Neelakanta Reddy 
date:Fri Oct 28 14:35:42 2016 +0530
summary: base: Using TRACE log priority when real-time scheduling policy is 
not supported [#1923]

changeset:   8267:eaf9daa89ce3
branch:  opensaf-5.1.x
parent:  8265:29b424e00fb9
user:Neelakanta Reddy 
date:Fri Oct 28 14:35:42 2016 +0530
summary: base: Using TRACE log priority when real-time scheduling policy is 
not supported [#1923]

changeset:   8268:c6d97cce299e
tag: tip
parent:  8264:288969ac258b
user:Neelakanta Reddy 
date:Fri Oct 28 14:35:42 2016 +0530
summary: base: Using TRACE log priority when real-time scheduling policy is 
not supported [#1923]





---

** [tickets:#1923] base: syslog filled with warning messages when running 
OpenSAF commands**

**Status:** fixed
**Milestone:** 5.0.2
**Created:** Tue Jul 19, 2016 11:41 AM UTC by Anders Widell
**Last Updated:** Tue Oct 25, 2016 09:33 AM UTC
**Owner:** Neelakanta Reddy


On a system where real-time threads are not allowed, the syslog can get filled 
up with messages like these:

Jul 19 12:45:11 node1 immfind: WA pthread_create failed with EPERM, falling 
back to SCHED_OTHER policy for OSAF_MDS
Jul 19 12:45:11 node1 immfind: WA pthread_create failed with EPERM, falling 
back to SCHED_OTHER policy for OSAF_TMR



---

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.--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2146 log: implement SaLogFilterSetCallbackT

[Vu Minh Nguyen]

---

** [tickets:#2146] log: implement SaLogFilterSetCallbackT**

**Status:** assigned
**Milestone:** 5.2.FC
**Created:** Fri Oct 28, 2016 09:01 AM UTC by Vu Minh Nguyen
**Last Updated:** Fri Oct 28, 2016 09:01 AM UTC
**Owner:** Vu Minh Nguyen


This ticket is to implement SaLogFilterSetCallbackT which is mentioned at 
section `3.6.5 SaLogFilterSetCallbackT` @ AIS LOG document.


---

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.--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2120 pyosaf: clm utils are missing dispatch function

[Robert Fekete]

- **status**: assigned --> review
- **Type**: defect --> enhancement
- **Milestone**: 5.0.2 --> 5.2.FC



---

** [tickets:#2120] pyosaf: clm utils are missing dispatch function**

**Status:** review
**Milestone:** 5.2.FC
**Created:** Mon Oct 17, 2016 06:38 AM UTC by Robert Fekete
**Last Updated:** Mon Oct 17, 2016 06:38 AM UTC
**Owner:** Robert Fekete


The clm utils __init__.py file is missing a function to invoke a dispatch.


---

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.--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2135 amf: Use cgroups Unpopulated Notification for passive monitoring

[Hans Nordebäck]

- **status**: unassigned --> assigned
- **assigned_to**: Hans Nordebäck



---

** [tickets:#2135] amf: Use cgroups Unpopulated Notification for passive 
monitoring**

**Status:** assigned
**Milestone:** 5.2.FC
**Created:** Fri Oct 21, 2016 02:12 PM UTC by Anders Widell
**Last Updated:** Fri Oct 21, 2016 02:12 PM UTC
**Owner:** Hans Nordebäck


Instead of using a busy loop with kill(pid, 0) for passive monitoring of 
processes, the cgroups Unpopulated Notification can be used:

[Get notifications on cgroup process 
change](http://stackoverflow.com/questions/35878292/get-notification-on-cgroup-process-change)



---

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.--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets