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

[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 is not the same before and after sending to CLM.
After applying the patch, it's allowed to use SaNameT values up to 255 
characters like in IMM. Frankly, I have no idea how CLM stored this values in 
IMM earlier.


---

** [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 Aug 26, 2016 09:33 AM UTC
**Owner:** Zoran Milinkovic


Ticket [#191] introduces support for long DN.
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 main reason for adding support for long DN is to support long RDN. In 
SaClmNode class, safNode attribute may have a hostname which can be up to 63 
bytes. Together with prefix "safNode=", RDN exceedes RDN limitation of 64 bytes.

Limit of 255 bytes for DN will still remain after applying the patch. Only long 
RDN will be supported.

The same limitation applies to PLM entities in CLM.





---

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

[tickets] [opensaf:tickets] #1934 amf: amfd fail-overs su to failed node during node-switchover recovery.

[Praveen]

- **status**: accepted --> review



---

** [tickets:#1934] amf: amfd fail-overs su to failed node during 
node-switchover recovery. **

**Status:** review
**Milestone:** 4.7.2
**Created:** Thu Aug 04, 2016 11:46 AM UTC by Praveen
**Last Updated:** Thu Aug 04, 2016 11:54 AM UTC
**Owner:** Praveen
**Attachments:**

- 
[nodeswitch.xml](https://sourceforge.net/p/opensaf/tickets/1934/attachment/nodeswitch.xml)
 (11.1 kB; text/xml)


Conf: 
Two SUs hosted on standby controller with 2N model. Recovery is 
node-switchover with su-failover flag enabled for SU1.

Steps to reproduce:
1)Bring attached configuration up. 
2) kill comp in SU1(active SU).

When AMFD gets recovery request for standby SC, it failovers SU1 and gives 
active to SU2 as a part of SU1 recovery. For SU2 recovery, it then sends 
quiesced assignment. This is a wrong sequence. Since SU2 is hosted on failed 
node, AMFD should not failover SU1 to SU2,

>From code perpective: AMFD marks all SUs of failed node OOS only in INIT_DONE 
>state. In APP_STATE this needs to be done by respective reocovery funtion. In 
>case of node-failvoer recovery avd_node_down_appl_susi_failover() is marking 
>SUs OOS before performing failover. But perform_nodeswitchover_recovery() is 
>not marking all the SUs OOS before performing failover/switchover of any SU.



---

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

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

[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 Zoran Milinkovic
**Last Updated:** Wed Aug 24, 2016 01:36 PM UTC
**Owner:** Zoran Milinkovic


Ticket [#191] introduces support for long DN.
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 main reason for adding support for long DN is to support long RDN. In 
SaClmNode class, safNode attribute may have a hostname which can be up to 63 
bytes. Together with prefix "safNode=", RDN exceedes RDN limitation of 64 bytes.

Limit of 255 bytes for DN will still remain after applying the patch. Only long 
RDN will be supported.

The same limitation applies to PLM entities in CLM.





---

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

[tickets] [opensaf:tickets] #1973 imm: IMM test returns zero even when it fails

[Hung Nguyen]

---

** [tickets:#1973] imm: IMM test returns zero even when it fails**

**Status:** accepted
**Milestone:** 4.7.2
**Created:** Fri Aug 26, 2016 08:15 AM UTC by Hung Nguyen
**Last Updated:** Fri Aug 26, 2016 08:15 AM UTC
**Owner:** Hung Nguyen


Snippet from main() in immtest.c

~~~
int main(int argc, char **argv) 
{
...

/* Added pthread_exit() to remove dlopen@@GLIBC leak from valgrind */
pthread_exit(NULL);

return rc;
}
~~~

pthread_exit() should be removed because it makes the test exit before 'return 
rc'.
I tried to run valgrind without pthread_exit(), it didn't complain anything 
about dlopen.





---

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

[tickets] [opensaf:tickets] #1585 NTF: Refactor logging long dn notification

[Vu Minh Nguyen]

README just updated/pushed according to this ticket.

@  changeset:   7959:a54d158c5051
|  tag: tip
|  user:Vu Minh Nguyen 
|  date:Fri Aug 26 12:57:53 2016 +0700
|  summary: ntf: update README file for long DN support [#1585]



---

** [tickets:#1585] NTF: Refactor logging long dn notification**

**Status:** fixed
**Milestone:** 5.1.FC
**Created:** Thu Nov 05, 2015 12:51 AM UTC by Minh Hon Chau
**Last Updated:** Tue Aug 23, 2016 06:08 AM UTC
**Owner:** nobody


If NTF logs a notification containing long dn and LOG service doesn't support 
long dn, the sanamet long dn will be stripped-down
Once LOG service supports long dn (#1315), NTF won't have to truncate long DN, 
only full long dn will be logged. This ticket is about refactoring, to remove 
the part of code that truncates the long DN


---

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