Hi Gary,
Replacement of m_CMP_HORDER_SANAMET() with std::compare() in AMFD alters the
way SI populates list_of_csi. Because of this old AMFD and new AMFD creates
different COMPCSI.
Both AMFD creates assignment without violating any AMF criteria. But it can
lead to problem from upgrade perspective.
I have attached traces and configuration from both new and old AMFD.
Steps to reproduce:
1)immcfg -f compare.xml.
2)Then immcfg -f csi_add.xml to add a new CSI in the same SI. At this point of
time, SI in both AMFDs will have list_of_csi with different order.
3)When application was brought up both AMFDs prepared compcsis differenlty
because of different ordering:
old_amfd:
Aug 8 12:26:52.156079 osafamfd [10702:csi.cc:1124] >> avd_compcsi_create:
Comp'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' and
Csi'safCsi=Norm1,safSi=AmfDemo,safApp=AmfDemo1'
Aug 8 12:26:52.156114 osafamfd [10702:csi.cc:1124] >> avd_compcsi_create:
Comp'safComp=AmfDemo1,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' and
Csi'safCsi=Norm3,safSi=AmfDemo,safApp=AmfDemo1'
Aug 8 12:26:52.156137 osafamfd [10702:csi.cc:1124] >> avd_compcsi_create:
Comp'safComp=AmfDemo2,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' and
Csi'safCsi=Norm11,safSi=AmfDemo,safApp=AmfDemo1'
new amfd:
fDemo,safApp=AmfDemo1' and Csi'safCsi=Norm1,safSi=AmfDemo,safApp=AmfDemo1'
Aug 8 12:26:51.974686 osafamfd [18560:csi.cc:1154] >> avd_compcsi_create:
Comp'safComp=AmfDemo1,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' and
Csi'safCsi=Norm11,safSi=AmfDemo,safApp=AmfDemo1'
Aug 8 12:26:51.974736 osafamfd [18560:csi.cc:1154] >> avd_compcsi_create:
Comp'safComp=AmfDemo2,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' and
Csi'safCsi=Norm3,safSi=AmfDemo,safApp=AmfDemo1'
In the Attachment find more information with extra traces.
This need to be checked at other places also wherever there is any such
replacement in AMFD, AMFND and AMFA.
Thanks,
Praveen
Attachments:
-
[compcsi.tgz](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/90f84e2d/88c4/attachment/compcsi.tgz)
(169.7 kB; application/x-compressed)
---
** [tickets:#1642] AMF: Support DNs longer than 255 bytes**
**Status:** review
**Milestone:** 5.1.FC
**Created:** Tue Dec 15, 2015 09:52 AM UTC by Long HB Nguyen
**Last Updated:** Fri Aug 05, 2016 06:30 AM UTC
**Owner:** Long HB Nguyen
Ticket [#191] introduced generic support in OpenSAF for DNs longer than 255
bytes. Each individual OpenSAF service will also have to be adapted to support
long DNs. This ticket is for AMF to support this feature.
Moreover, this ticket also contains some enhancements:
1) Refactor internal SaNameT to std::string in amfd, amfnd.
2) Refactor PATRICIA trees to std::map in amfnd.
---
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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
