[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-09-12 Thread Mathi Naickan
changeset: 187:ce165392b313 tag: tip user:mathi.naic...@oracle.com date:Mon Sep 12 15:47:47 2016 +0530 summary: clm: doc update for long RDN support in 5.1 [#1906] --- ** [tickets:#1906] clm: add support for long DN** **Status:** fixed **Milestone:** 5.1.FC

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-08-30 Thread A V Mahesh (AVM)
changeset: 7989:4d6caf6903cd tag: tip user:A V Mahesh date:Tue Aug 30 11:05:31 2016 +0530 summary: clm: test code build fix [#1906] --- ** [tickets:#1906] clm: add support for long DN** **Status:** fixed **Milestone:** 5.1.FC **Created:**

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-08-29 Thread Mathi Naickan
- **status**: review --> fixed --- ** [tickets:#1906] clm: add support for long DN** **Status:** fixed **Milestone:** 5.1.FC **Created:** Mon Jul 04, 2016 01:10 PM UTC by Zoran Milinkovic **Last Updated:** Mon Aug 29, 2016 02:38 PM UTC **Owner:** Zoran Milinkovic Ticket [#191] introduces

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-08-26 Thread Zoran Milinkovic
Hi Ritu, Can you check your test case that executionEnvironment is using value longer than 255 characters ? I'm asking you this because before the patch, CLM allowed to use SaNameT value up to 256 characters. But in this case CLM removed the last 256th character and set \0. So SaNameT value

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-08-26 Thread Ritu Raj
Hi Zoran, We did't added any clm node or changes any configuration, the default one is used. Also, the test case are not related to longDn. --- ** [tickets:#1906] clm: add support for long DN** **Status:** review **Milestone:** 5.1.FC **Created:** Mon Jul 04, 2016 01:10 PM UTC by

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-08-24 Thread Zoran Milinkovic
Hi Ritu, It seems that executionEnvironment in SaClmClusterNotificationBufferT_4 struct has a value length longer than 255 characters. Can you check how long is executionEnvironment ? --- ** [tickets:#1906] clm: add support for long DN** **Status:** review **Milestone:** 5.1.FC **Created:**

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-08-16 Thread Zoran Milinkovic
changeset: 7859:722ce031a07b user:Zoran Milinkovic date:Tue Aug 16 09:57:11 2016 +0200 summary: clm: fix decoding for SaNameT type [#1906] changeset: 7860:59d114fc4636 tag: tip user:Zoran Milinkovic

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-08-14 Thread Mathi Naickan
- **Comment**: Pushed the first stab of the patch changeset: 7855:bc669776cf7f tag: tip user:Zoran Milinkovic date:Mon Aug 15 09:38:00 2016 +0530 summary: clm: add support for long RDN [#1906] Keeping the ticket open, pending the

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-07-15 Thread Zoran Milinkovic
- **status**: accepted --> review - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/35223817/ --- ** [tickets:#1906] clm: add support for long DN** **Status:** review **Milestone:** 5.1.FC **Created:** Mon Jul 04, 2016 01:10 PM UTC by Zoran Milinkovic **Last Updated:** Fri Jul

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-07-15 Thread Zoran Milinkovic
- Description has changed: Diff: --- old +++ new @@ -1,2 +1,11 @@ Ticket [#191] introduces support for long DN. -This ticket adds the support for long DN to CLM. +This ticket adds the support for long RDN to CLM. + +Today, there is no any reason for the support for long DN in CLM. +The

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-07-06 Thread Hans Nordebäck
you can refactor clmsv to: 1) compile with c++ 2) replace SaNameT with std::string 3) replace Patricia tree with stl::map or reuse AmfDb /Thanks Hans --- ** [tickets:#1906] clm: add support for long DN** **Status:** accepted **Milestone:** 5.1.FC **Created:** Mon Jul 04, 2016 01:10 PM UTC by

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-07-04 Thread Mathi Naickan
Hi Zoran, I think this has now become the 'usually' asked question on this topic of long DN. It is amusing to me that we are supporting long DNs for anything else other than AMF, LOG, NTF, SMF, IMM. So, perhaps you could share the motivation/usecase behind configuring node names of such

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-07-04 Thread Zoran Milinkovic
- **status**: unassigned --> accepted --- ** [tickets:#1906] clm: add support for long DN** **Status:** accepted **Milestone:** 5.1.FC **Created:** Mon Jul 04, 2016 01:10 PM UTC by Zoran Milinkovic **Last Updated:** Mon Jul 04, 2016 01:10 PM UTC **Owner:** Zoran Milinkovic Ticket [#191]

[tickets] [opensaf:tickets] #1906 clm: add support for long DN

2016-07-04 Thread Zoran Milinkovic
--- ** [tickets:#1906] clm: add support for long DN** **Status:** unassigned **Milestone:** 5.1.FC **Created:** Mon Jul 04, 2016 01:10 PM UTC by Zoran Milinkovic **Last Updated:** Mon Jul 04, 2016 01:10 PM UTC **Owner:** Zoran Milinkovic Ticket [#191] introduces support for long DN. This