[tickets] [opensaf:tickets] #2255 amf: change saAmfCompCmdEnv attribute to writable

2017-02-07 Thread Nguyen TK Luu 
- **status**: review --> fixed
- **Comment**:

default:[staging:4c033e]
changeset:   8562:4c033ee752e6
user:Nguyen Luu 
date:Wed Feb 08 17:43:09 2017 +1100
summary: amf: change saAmfCompCmdEnv attribute to writable [#2255]



---

** [tickets:#2255] amf: change saAmfCompCmdEnv attribute to writable**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Mon Jan 09, 2017 10:29 AM UTC by Long HB Nguyen
**Last Updated:** Thu Jan 19, 2017 08:09 AM UTC
**Owner:** Nguyen TK Luu


Description:
Current OpenSAF implementation defines the attribute saAmfCompCmdEnv in the 
SaAmfComp object as non-writable according to last AMF specification. This 
restriction doesn’t allow to upgrade environment attributes defined at 
component instance and, to remove it, the attribute was made writable in an 
errata to the model. OpenSAF should comply to this definition in the errata 
(www.saforum.org/HOA/assn16627/images/SAI-IM-XMI-A.04.02.errata.xml.zip) of the 
AMF specification to enable the upgrade of environment attributes defined at 
component instance level.


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2293 base: UnixSocket, multiple issues

2017-02-07 Thread Anders Widell 



---

** [tickets:#2293] base: UnixSocket, multiple issues**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Tue Feb 07, 2017 03:19 PM UTC by Anders Widell
**Last Updated:** Tue Feb 07, 2017 03:19 PM UTC
**Owner:** Anders Widell


Multiple issues have been identified in the UnixSocket class:

* The UnixServerSocket fails if the named already exists in the file system.
* The UnixSocket uses a mutex to protect Open() and Close(), but this is not 
enough to make it thread safe. The suggestion is to remove the mutex and let 
users protect the instance if needd
* The fd() method is not so useful since it requires a message to be sent or 
received before it returns a valid file descriptor. It is probably better if 
the fd() method opens the socket if it is not already open.
* The UnixClientSocket implements a wait-loop in case connect() returns 
EINPROGRESS. It would be better to us a blocking call to connect().


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2292 mds: The meta sequenceId field should be used for log message sequence numbers

2017-02-07 Thread Anders Widell 



---

** [tickets:#2292] mds: The meta sequenceId field should be used for log 
message sequence numbers**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Tue Feb 07, 2017 03:09 PM UTC by Anders Widell
**Last Updated:** Tue Feb 07, 2017 03:09 PM UTC
**Owner:** Anders Widell


The MDS log implementation writes log entry sequence numbers to the MSGID 
field. However, the RFC specifies that the meta sequenceId field is to be used 
for this purpose.


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2291 dtm: MDS log is overwritten after a node restart

2017-02-07 Thread Anders Widell 



---

** [tickets:#2291] dtm: MDS log is overwritten after a node restart**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Tue Feb 07, 2017 03:07 PM UTC by Anders Widell
**Last Updated:** Tue Feb 07, 2017 03:07 PM UTC
**Owner:** Anders Widell


osaftransportd overwrites an existing MDS log file after a node restart. If an 
MDS log file exists, it should be appended.


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2290 mds: (TCP) Libraries cause high CPU load when opensaf service stops

2017-02-07 Thread Hung Nguyen 



---

** [tickets:#2290] mds: (TCP) Libraries cause high CPU load when opensaf 
service stops**

**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Tue Feb 07, 2017 11:03 AM UTC by Hung Nguyen
**Last Updated:** Tue Feb 07, 2017 11:03 AM UTC
**Owner:** nobody


When DBSRsock is closed and it returns from mdtm_process_poll_recv_data_tcp()

~~~
:::c
syslog(LOG_ERR, "MDTM:SOCKET recd_bytes :%zd, conn lost with dh server", 
recd_bytes);
close(tcp_cb->DBSRsock);
return;
~~~

the while() loops rapidly because the poll() returns **1** and pfd[0].revents 
is **32 (POLLNVAL 0x020)**

~~~
:::c
pfd[0].fd = tcp_cb->DBSRsock;
pfd[1].fd = tcp_cb->tmr_fd;

while (1) {
int pollres;

pfd[0].events = POLLIN;
pfd[1].events = POLLIN;

pfd[0].revents = pfd[1].revents = 0;

pollres = poll(pfd, 2, MDTM_TCP_POLL_TIMEOUT);

...
}
~~~



-
Reproduce steps:

* run immcfg
~~~
root@SC-1:~# immcfg
>
~~~
* stop opensaf service
~~~
root@SC-1:~# service opensafd stop
~~~
* check the CPU






---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1749 amf: Incorrect ER in syslog

2017-02-07 Thread Nagendra Kumar 
- **Component**: osaf --> amf
- **Part**: - --> d
- **Comment**:

I will fix relevant error logs in Amf, let other services owners create the 
tickets.



---

** [tickets:#1749] amf: Incorrect ER in syslog**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Tue Apr 12, 2016 12:22 PM UTC by elunlen
**Last Updated:** Mon Aug 29, 2016 08:11 PM UTC
**Owner:** Nagendra Kumar


When requesting AMF to do a SI swap the following message may appear in the 
syslog:
2016-04-11 17:35:37 SC-1 osafamfd[500]: ER safSi=SC-2N,safApp=OpenSAF SWAP 
failed - Cold sync in progress
This is the case also if the response to the operation is SA_AIS_ERR_TRY_AGAIN 
or SA_AIS_ERR_BUSY.
Getting these responses is not error responses and should not result in an ER 
message in the syslog


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2287 uml: build_uml install_testprog fails for amf_demo app

2017-02-07 Thread Hans Nordebäck 
- **status**: review --> fixed
- **Comment**:

changeset:   8560:a8bdf368f9a6
tag: tip
user:Hans Nordeback 
date:Tue Feb 07 10:37:53 2017 +0100
summary: uml: build_uml install_testprog fails for amf_demo app V2 [#2287]




---

** [tickets:#2287] uml: build_uml install_testprog fails for amf_demo app**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Thu Feb 02, 2017 01:05 PM UTC by Hans Nordebäck
**Last Updated:** Thu Feb 02, 2017 01:07 PM UTC
**Owner:** Hans Nordebäck


build_uml install_testprog fails for amf_demo app with the new directory 
structure.


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2207 cpnd: osafckptnd core dump while handling error section_hdr_update_fails

2017-02-07 Thread A V Mahesh (AVM) 
- **status**: review --> fixed



---

** [tickets:#2207] cpnd: osafckptnd core dump while handling error 
section_hdr_update_fails**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Thu Nov 24, 2016 09:45 AM UTC by Vo Minh Hoang
**Last Updated:** Thu Dec 01, 2016 10:32 AM UTC
**Owner:** Vo Minh Hoang
**Attachments:**

- 
[cpsv_shm_2202.c](https://sourceforge.net/p/opensaf/tickets/2207/attachment/cpsv_shm_2202.c)
 (12.7 kB; application/octet-stream)


the steps to add a section is add_db_tree -> update_sec_hdr -> update_ckpt_hdr 
so if an error occur cpsv should handle error in reverse order.
currently, section_hdr_update_fails, cpsv revert ckpt_hdr also that possibly 
cause the problem

Coredump:
~~~
Core was generated by `/usr/lib64/opensaf/osafckptnd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f1846da1109 in __memcpy_sse2_unaligned () from /lib64/libc.so.6
Missing separate debuginfos, use: zypper install 
opensaf-ckpt-nodedirector-debuginfo-5.1.0-99.0.686bc00.sle12.x86_64
(gdb) bt
#0  0x7f1846da1109 in __memcpy_sse2_unaligned () from /lib64/libc.so.6
#1  0x7f1847f26f25 in memcpy (__len=, __src=, 
__dest=)
at /usr/include/x86_64-linux-gnu/bits/string3.h:53
#2  ncs_os_posix_shm (req=req@entry=0x7ffd24f978f0) at os_defs.c:859
#3  0x0041561d in cpnd_ckpt_hdr_update (cp_node=cp_node@entry=0xa708e0) 
at cpnd_proc.c:1833
#4  0x0041b016 in cpnd_ckpt_sec_del (cp_node=cp_node@entry=0xa708e0, 
id=id@entry=0x7f1840007350)
at cpnd_sec.cc:220
#5  0x00406190 in cpnd_ckpt_sec_add (cp_node=cp_node@entry=0xa708e0, 
id=0x7f1840007350,
exp_time=1479906629297747000, gen_flag=gen_flag@entry=0) at cpnd_db.c:473
#6  0x0040cfe2 in cpnd_evt_proc_ckpt_sect_create (cb=cb@entry=0x8c77f0,
evt=evt@entry=0x7f184000a560, sinfo=sinfo@entry=0x7f184000abb8) at 
cpnd_evt.c:2244
#7  0x0040e7cc in cpnd_process_evt (evt=0x7f184000a550) at 
cpnd_evt.c:227
#8  0x004103bd in cpnd_main_process (cb=cb@entry=0x8c77f0) at 
cpnd_init.c:579
#9  0x00405383 in main (argc=, argv=) at 
cpnd_main.c:79
~~~


consequence of #2202


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2259 amf: support for si-swap admin op for N+M model.

2017-02-07 Thread Praveen 
- Description has changed:

Diff:



--- old
+++ new
@@ -1,4 +1,35 @@
-As per spec, SI_SWAP admin operation is applicable to a SI which is protected 
by SG of 2N, NWAY or NPM model. Current OpenSAF implementation already supports 
2N and N-WAY model.
+As per spec, SI_SWAP admin operation is applicable to a SI which is protected 
by SG of 2N, NWAY or NPM model. Current OpenSAF implementation already supports 
2N and N-WAY model.This enhancements is for supporting the admin operation on 
SI of N+M model SG. 
 
-This enhancements is for supporting the admin operation on SI of N+M model SG. 
Since SI dep within SU is not suported in N+M model, AMF will not honour SI dep 
within SU while assigning Active or Quiesced HA state 
-during the admin operation.
+AMF B.04.01 spec writes about SI_SWAP armin operation for applicable red model 
in the section  "9.4.8 SA_AMF_ADMIN_SI_SWAP" page 386 of B.04.01 spec.  For N+M 
model, spec states that:
+"If the designated SI is protected by a service group whose redundancy model 
is N+M,
+the invocation of this administrative operation results in a complete swap of 
all active
+and standby CSIs belonging to not just the designated SI but also to any other 
SI that
+is assigned active to a service unit to which the designated SI is assigned 
active.
+Application of this operation on an SI may potentially modify the standby 
assignments
+of other SIs that are protected by the same service group, but are not 
assigned to the
+service unit to which the SI in question is assigned active."
+
+**Example configuration N+1 given in spec:**
+In the same paragraph above in section 9.4.8 SA_AMF_ADMIN_SI_SWAP, one example 
is given how SI_SWAP will proceed in N+M model.
+1) Four nodes U, V, W and X hosts S1, S2, S3 and S4 respectively.
+2) There are three SIs SIA, SIB and SIC.
+3) SIA is active in S1, SIB is active in S2 and SIC is active in S3.
+4) All SIs are standby in S4.
+5) SI_SWAP admin operation Flow for above configuration: As per spec , 
+"If the swap operation is applied on SI A, the active assignment
+for SI A shall be moved to Service Unit S4 on Node X, and the standby 
assignments
+for SI A as well as that of SI C and SI B will be moved to Service Unit S1 on
+Node U. The active assignments of SI C and SI B will remain on Service Unit S3 
(on
+Node W) and Service Unit S2 (on Node V), respectively"
+Here SU S1 will become quiesced for all active SIs  (only one SIA in this 
example). At this point of time, SU S4 is standby for SIB and SIC also but SU1 
is not quiesced for these two SIs. Due to this,  SIB and SIC will be removed 
from SU S4 and it will become active for SIA. Now SU S1 will be made standby 
for all quiesced SIs (only one SIA in this example).  Since standby assignments 
from SIB and SIC are getting removed during the course of this operation, SU S1 
will make standby for SIB and SIC by giving fresh assignments.
+So in contrast to 2N redudancy model, flow of SI_SWAP operation in N+M 
model can lead to removal of standby assignments and also fresh assignments. 
+
+**Notes on implementation: **
+1)SI_SWAP operation will not be allowed if SI Equal distribution feature is 
enabled in the SG.
+2)Since SI dep within SU is not suported in N+M model, AMF will not honour SI 
dep within SU while assigning Active or Quiesced HA state  during the admin 
operation.
+3)Since Operation will lead to swap of all SIs assgined to the active SU, 
operation will be rejected if anyone of these SIs does not have standby 
assignments in some SU.
+4) Operation will not be allowed if it will lead to violation of SG 
configuration attrbiutes: saAmfSGMaxActiveSIsperSU, saAmfSGMaxStandbySIsperSU, 
saAmfSGNumPrefActiveSUs and saAmfSGNumPrefStandbySUs.
+
+**Changes in sg_npm_fsm.cc:** Some code related to switch operation is already 
present. The same code will resued and enhanced for implementation. Most of the 
code is under SI_OPER state of SG.
+
+To be updated with more example configuration..



- **Comment**:



  




---

** [tickets:#2259] amf: support for si-swap admin op for N+M model.**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Wed Jan 11, 2017 06:13 AM UTC by Praveen
**Last Updated:** Wed Jan 11, 2017 06:47 AM UTC
**Owner:** Praveen


As per spec, SI_SWAP admin operation is applicable to a SI which is protected 
by SG of 2N, NWAY or NPM model. Current OpenSAF implementation already supports 
2N and N-WAY model.This enhancements is for supporting the admin operation on 
SI of N+M model SG. 

AMF B.04.01 spec writes about SI_SWAP armin operation for applicable red model 
in the section  "9.4.8 SA_AMF_ADMIN_SI_SWAP" page 386 of B.04.01 spec.  For N+M 
model, spec states that:
"If the designated SI is protected by a service group whose redundancy model is 
N+M,
the invocation of this administrative operation results in a complete swap of 
all active
and standby CSIs belonging to not just the designated SI but also to any other 
SI that
is assigned