The usecase for point 5) is that it must be possible to upgrade a running
system with an earlier sw version to a version with these new features. This
means that “networkName” must be possible to set/upgrade in runtime.
The log service must know if the attribute “neworkName” is changed also if it
is a “SaClmCluster” class attribute.
1) A “simple” solution:
Make the Log service an IMM applier for the “SaClmCluster” object.
2) The complicated but perhaps more correct?? Solution:
Create a new callback for CLM that can be used by the log service to be alerted
when the attribute is changed.
---
** [tickets:#1480] LOG: Extend information about origin of log record**
**Status:** accepted
**Milestone:** 5.0
**Created:** Tue Sep 15, 2015 12:50 PM UTC by elunlen
**Last Updated:** Thu Sep 24, 2015 10:02 AM UTC
**Owner:** elunlen
Add the possibility to show network name and CLM node name or node id as an
extension of the already existing way of showing the origin of a log record.
For a detailed description of what to implement see the attached .odt document.
To show/document how this can be implemented the ticket will be complimented
with a series of prototype patches that will be attached when ready
---
Sent from sourceforge.net because [email protected] 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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
