A final decision is made based on the following discussion.
Discussed topic:
We have discussed this sufficiently. I guess we have to choose between two
choices.
Option1) Reading the network name via CSI attribute – AMF will make this
feature configurable and to start with the feature will be
applicable only to middleware services. So, no issue with backward
compatibility. Least code changes. Fits well into the SAF architecture.
Versus
Option 2) Introduce a new global OpenSAF class with nobody as the OI. LOG
service will be the applier for this global class.
Decisions taken:
Where and how the “network name” should be read:
Prior to the meeting Mathi provided with two options from where and how to read
the “network name”.
It was agreed that the information about the network name should not be a part
of CLM but instead a global class can be introduced in OpenSAF (Option 2) to
handle this information.
(in the future this global class might be merged into CLM, but for now it will
be kept separate )
Use cases for "network name":
Multiple use-cases for having the network name were discussed, according to
Lennart it is a name assigned to the cluster it may not be of any value to the
OpenSAF itself but it will help the users of OpenSAF to identify from which
cluster the log records are coming from.
Runtime configurable :
It was previously proposed that the "network name" should be run time
configurable, there was discussion around why should it be run time
configurable, there were some concerns from Mathi but eventually it is agreed
to make this attribute runtime configurable.
Name for the global class :
This global class proposed in Option 2 should be named with consideration
because it will not be feasible to change the name in the future, the name is
not decided yet.
---
** [tickets:#1480] LOG: Extend information about origin of log record**
**Status:** accepted
**Milestone:** 5.0.FC
**Created:** Tue Sep 15, 2015 12:50 PM UTC by elunlen
**Last Updated:** Tue Nov 10, 2015 01:02 PM 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.
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
