date:20170227

[tickets] [opensaf:tickets] #2326 log : fix all cpp check issues

2017-02-27 Thread A V Mahesh (AVM)

- Description has changed:

Diff:



--- old
+++ new
@@ -1,67 +1,74 @@
-2017-02-24 10:18:04 INFO: *** List of cppcheck errors added by patch ***
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::amfSelectionObject' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::amf_hdl' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::amf_invocation_id' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::async_upd_cnt' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::ckpt_state' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::clmSelectionObject' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::clm_hdl' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::clm_init_sel_obj' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::comp_name' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::edu_hdl' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::fully_initialized' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::ha_state' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::immOiHandle' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::immSelectionObject' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::is_quiesced_set' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::last_client_id' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::lga_down_list_head' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::lga_down_list_tail' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::log_version' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::mbcsv_ckpt_hdl' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::mbcsv_hdl' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::mbcsv_peer_version' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::mbcsv_sel_obj' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::mds_hdl' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::mds_role' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::nid_started' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::scAbsenceAllowed' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_cb.h:106]: (warning) Member 
variable 'lgs_cb::vaddr' is not initialized in the constructor.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_clm.cc:137]: (style) The 
scope of the variable 'clm_node' can be reduced.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_clm.cc:213]: (style) The 
scope of the variable 'rec' can be reduced.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_clm.cc:220]: (performance) 
Prefer prefix ++/-- operators for non-primitive types.
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_evt.cc:1493]: (style) 
Condition '0' is always false
-2017-02-24 10:18:04 INFO: ***[src/log/logd/lgs_evt.cc:163]: (error) 
Mismatching

[tickets] [opensaf:tickets] Re: #2316 amfnd: amfnd is stuck in removing assignment in shutting down phase

2017-02-27 Thread Minh Hon Chau

Hi Praveen,

Since this problem has occured at our application's side, so I decided to send 
it for review first and we can look at the patch on devel mail then.

Thanks,
Minh


---

** [tickets:#2316] amfnd: amfnd is stuck in removing assignment in shutting 
down phase**

**Status:** review
**Milestone:** 5.0.2
**Created:** Wed Feb 22, 2017 01:00 AM UTC by Minh Hon Chau
**Last Updated:** Tue Feb 28, 2017 02:54 AM UTC
**Owner:** Minh Hon Chau
**Attachments:**

- 
[app3_twon2su1si.xml](https://sourceforge.net/p/opensaf/tickets/2316/attachment/app3_twon2su1si.xml)
 (9.2 kB; text/xml)
- [log.tgz](https://sourceforge.net/p/opensaf/tickets/2316/attachment/log.tgz) 
(696.0 kB; application/x-compressed)


- Configuration: Using attached model
- Steps:
. Loading application in attached model
. SU5 in PL5 has standby assignment
. kill amf_demo in PL5 which is component of SU5
. amd_demo will be instantiated and reassigned assignment
. Delay csi set callback for standby assignment in amf_demo component
. stop opensafd: /opensafd stop
. Release csi set callback in amf_demo component
- Observation: amfnd is stucked in removing assignment until it's killed by 
opensafd

> 2017-02-21 23:04:54 PL-5 amf_demo[543]: exiting (caught term signal)
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' component restart probation 
> timer started (timeout: 300 ns)
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO Restarting a component of 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' (comp restart count: 1)
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO 
> 'safComp=AmfDemo,safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' faulted due to 
> 'avaDown' : Recovery is 'componentRestart'
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' Presence State INSTANTIATED => 
> RESTARTING
> 2017-02-21 23:04:54 PL-5 amf_demo[605]: 
> 'safComp=AmfDemo,safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' started
> 2017-02-21 23:04:54 PL-5 amf_demo_script: 
> safComp=AmfDemo,safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3
> 2017-02-21 23:04:54 PL-5 amf_demo_script: Starting 
> /srv/osaftest/amf_demo/amf_demo succeeded, rc:0
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' Presence State RESTARTING => 
> INSTANTIATED
> 2017-02-21 23:04:54 PL-5 amf_demo[605]: Registered with AMF and HC started
> 2017-02-21 23:04:54 PL-5 amf_demo[605]: CSI Set - add 
> 'safCsi=AmfDemo3,safSi=AmfDemo3,safApp=AmfDemo3' HAState Standby
> 2017-02-21 23:04:54 PL-5 amf_demo[605]: debug delay 2 secs
> 2017-02-21 23:04:57 PL-5 opensafd: Stopping OpenSAF Services
> 2017-02-21 23:04:57 PL-5 osafamfnd[412]: NO Shutdown initiated
> 2017-02-21 23:04:57 PL-5 osafamfnd[412]: NO Removing assignments from AMF 
> components
> 2017-02-21 23:05:00 PL-5 amf_demo[605]: message repeated 3 times: [ debug 
> delay 2 secs]
> 2017-02-21 23:05:02 PL-5 amf_demo[605]: Health check 1
> 2017-02-21 23:05:24 PL-5 osafamfnd[412]: NO 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' Component or SU restart 
> probation timer expired
> 2017-02-21 23:05:57 PL-5 opensafd: amfnd has not yet exited, killing it 
> forcibly.
> 2017-02-21 23:05:57 PL-5 amf_demo[605]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 amf_demo[605]: exiting (caught term signal)
> 2017-02-21 23:05:57 PL-5 osafclmna[404]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 osafimmnd[395]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 osafckptnd[431]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 osafsmfnd[453]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 osafamfwd[422]: Rebooting OpenSAF NodeId = 0 EE Name 
> = No EE Mapped, Reason: AMF unexpectedly crashed, OwnNodeId = 132367, 
> SupervisionTime = 60
> 
log/trace is attached



---

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 ( Standbys in same su case).

2017-02-27 Thread Praveen

- **status**: review --> fixed
- **Comment**:

changeset:   8627:8e56871d5619
tag: tip
user:Praveen Malviya 
date:Tue Feb 28 10:49:16 2017 +0530
summary: amfd: support si-swap admin op for NplusM model when standbys are 
in same SU. [#2259]





---

** [tickets:#2259] amf: support for si-swap admin op for N+M model ( Standbys 
in same su case).**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Wed Jan 11, 2017 06:13 AM UTC by Praveen
**Last Updated:** Mon Feb 27, 2017 07:28 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 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..


---

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] #2316 amfnd: amfnd is stuck in removing assignment in shutting down phase

2017-02-27 Thread Minh Hon Chau

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



---

** [tickets:#2316] amfnd: amfnd is stuck in removing assignment in shutting 
down phase**

**Status:** review
**Milestone:** 5.0.2
**Created:** Wed Feb 22, 2017 01:00 AM UTC by Minh Hon Chau
**Last Updated:** Mon Feb 27, 2017 04:31 AM UTC
**Owner:** Minh Hon Chau
**Attachments:**

- 
[app3_twon2su1si.xml](https://sourceforge.net/p/opensaf/tickets/2316/attachment/app3_twon2su1si.xml)
 (9.2 kB; text/xml)
- [log.tgz](https://sourceforge.net/p/opensaf/tickets/2316/attachment/log.tgz) 
(696.0 kB; application/x-compressed)


- Configuration: Using attached model
- Steps:
. Loading application in attached model
. SU5 in PL5 has standby assignment
. kill amf_demo in PL5 which is component of SU5
. amd_demo will be instantiated and reassigned assignment
. Delay csi set callback for standby assignment in amf_demo component
. stop opensafd: /opensafd stop
. Release csi set callback in amf_demo component
- Observation: amfnd is stucked in removing assignment until it's killed by 
opensafd

> 2017-02-21 23:04:54 PL-5 amf_demo[543]: exiting (caught term signal)
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' component restart probation 
> timer started (timeout: 300 ns)
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO Restarting a component of 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' (comp restart count: 1)
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO 
> 'safComp=AmfDemo,safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' faulted due to 
> 'avaDown' : Recovery is 'componentRestart'
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' Presence State INSTANTIATED => 
> RESTARTING
> 2017-02-21 23:04:54 PL-5 amf_demo[605]: 
> 'safComp=AmfDemo,safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' started
> 2017-02-21 23:04:54 PL-5 amf_demo_script: 
> safComp=AmfDemo,safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3
> 2017-02-21 23:04:54 PL-5 amf_demo_script: Starting 
> /srv/osaftest/amf_demo/amf_demo succeeded, rc:0
> 2017-02-21 23:04:54 PL-5 osafamfnd[412]: NO 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' Presence State RESTARTING => 
> INSTANTIATED
> 2017-02-21 23:04:54 PL-5 amf_demo[605]: Registered with AMF and HC started
> 2017-02-21 23:04:54 PL-5 amf_demo[605]: CSI Set - add 
> 'safCsi=AmfDemo3,safSi=AmfDemo3,safApp=AmfDemo3' HAState Standby
> 2017-02-21 23:04:54 PL-5 amf_demo[605]: debug delay 2 secs
> 2017-02-21 23:04:57 PL-5 opensafd: Stopping OpenSAF Services
> 2017-02-21 23:04:57 PL-5 osafamfnd[412]: NO Shutdown initiated
> 2017-02-21 23:04:57 PL-5 osafamfnd[412]: NO Removing assignments from AMF 
> components
> 2017-02-21 23:05:00 PL-5 amf_demo[605]: message repeated 3 times: [ debug 
> delay 2 secs]
> 2017-02-21 23:05:02 PL-5 amf_demo[605]: Health check 1
> 2017-02-21 23:05:24 PL-5 osafamfnd[412]: NO 
> 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemo3' Component or SU restart 
> probation timer expired
> 2017-02-21 23:05:57 PL-5 opensafd: amfnd has not yet exited, killing it 
> forcibly.
> 2017-02-21 23:05:57 PL-5 amf_demo[605]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 amf_demo[605]: exiting (caught term signal)
> 2017-02-21 23:05:57 PL-5 osafclmna[404]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 osafimmnd[395]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 osafckptnd[431]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 osafsmfnd[453]: AL AMF Node Director is down, 
> terminate this process
> 2017-02-21 23:05:57 PL-5 osafamfwd[422]: Rebooting OpenSAF NodeId = 0 EE Name 
> = No EE Mapped, Reason: AMF unexpectedly crashed, OwnNodeId = 132367, 
> SupervisionTime = 60
> 
log/trace is attached



---

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] #1640 Integrate IMM service with CLM

2017-02-27 Thread Neelakanta Reddy

- **Comment**:

changeset:   8626:c5eee2837fcd
tag: tip
user:Neelakanta Reddy 
date:Tue Feb 28 06:35:03 2017 +0530
summary: imm:Adding immnd_clm file for  IMM service with CLM [#1640]




---

** [tickets:#1640] Integrate IMM service with CLM**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Tue Dec 15, 2015 08:32 AM UTC by Mathi Naickan
**Last Updated:** Tue Feb 28, 2017 01:49 AM UTC
**Owner:** Neelakanta Reddy


IMM Behavior of CLM integration:
1.  section 3.3 of IMM Spec (A.02.01).
2.  SA_AIS_ERR_UNAVAILABLE return code for APIs in IMM Spec.

IMMA:
New IMMA version A.2.18 wil be introduced for the CLMS integration with IMMA.
SA_AIS_ERR_UNAVAILABLE will be returned when the CLMS service is not available,
as per the IMM specification.

IMMND:
Register for CLM Track callback. From the callback, CLM status information
will be sent to IMMA.

IMMD:
Register for CLM Track callback. When the CLM node leaves the cluster, the 
IMMND is 
removed from the IMMD internal database. IMMND node down is broadcasted to 
remaining 
IMMNDs in the cluster.


---

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] #1640 Integrate IMM service with CLM

2017-02-27 Thread Neelakanta Reddy

- **status**: review --> fixed
- **Comment**:

changeset:   8625:e5ff49d5052d
tag: tip
user:Neelakanta Reddy 
date:Tue Feb 28 06:22:42 2017 +0530
summary: imm:Integration of IMM service with CLM [#1640]




---

** [tickets:#1640] Integrate IMM service with CLM**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Tue Dec 15, 2015 08:32 AM UTC by Mathi Naickan
**Last Updated:** Tue Feb 21, 2017 06:05 AM UTC
**Owner:** Neelakanta Reddy


IMM Behavior of CLM integration:
1.  section 3.3 of IMM Spec (A.02.01).
2.  SA_AIS_ERR_UNAVAILABLE return code for APIs in IMM Spec.

IMMA:
New IMMA version A.2.18 wil be introduced for the CLMS integration with IMMA.
SA_AIS_ERR_UNAVAILABLE will be returned when the CLMS service is not available,
as per the IMM specification.

IMMND:
Register for CLM Track callback. From the callback, CLM status information
will be sent to IMMA.

IMMD:
Register for CLM Track callback. When the CLM node leaves the cluster, the 
IMMND is 
removed from the IMMD internal database. IMMND node down is broadcasted to 
remaining 
IMMNDs in the cluster.


---

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] #2065 amf: support for SA_AMF_CLUSTER_RESET recommended recovery

2017-02-27 Thread Praveen

- **status**: review --> fixed
- **Comment**:

changeset:   8624:05a15c96f745
tag: tip
user:Praveen Malviya 
date:Mon Feb 27 17:15:09 2017 +0530
files:   src/amf/amfd/comp.cc src/amf/amfd/comptype.cc 
src/amf/amfd/sgproc.cc src/amf/amfd/util.cc src/amf/amfd/util.h 
src/amf/amfnd/cpm.cc src/amf/amfnd/err.cc
description:
amfd: support for cluster reset recovery[#2065]

[staging:05a15c]





---

** [tickets:#2065] amf: support for SA_AMF_CLUSTER_RESET recommended recovery**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Fri Sep 23, 2016 11:54 AM UTC by Mathi Naickan
**Last Updated:** Wed Feb 15, 2017 08:42 AM UTC
**Owner:** Praveen


Support for the SA_AMF_CLUSTER_RESET = 7, Recommended recovery - both as 
configuration and for error reporting via saAmfComponentErrorReport.




---

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] #2267 base: Add a support function for reading the FQDN

2017-02-27 Thread Anders Widell

- **status**: review --> fixed
- **Comment**:

changeset:   8622:47c9ad41321e
user:Anders Widell 
date:Mon Feb 27 12:08:32 2017 +0100
summary: base: Add methods for reading the FQDN, host name and node name 
[#2267]

changeset:   8623:c4ebd14028c9
user:Anders Widell 
date:Mon Feb 27 12:08:32 2017 +0100
summary: mds: Use the new base class Conf for reading the FQDN [#2267]

[staging:47c9ad]
[staging:c4ebd1]



---

** [tickets:#2267] base: Add a support function for reading the FQDN**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Tue Jan 17, 2017 02:43 PM UTC by Anders Widell
**Last Updated:** Fri Feb 17, 2017 09:34 AM UTC
**Owner:** Anders Widell


The FQDN (fully qualified domain name) is needed when generating MDS log 
records in the RFC 5424 format. This ticket tracks the implementation of a 
support function for retrieving the FQDN of the current node.


---

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] #2322 Amf: Amfd crashed during cold sync

2017-02-27 Thread Nagendra Kumar

- **status**: review --> fixed
- **Comment**:

changeset:   8619:addb5d754d71
branch:  opensaf-5.0.x
parent:  8607:adc96bde4277
user:Nagendra Kumar
date:Mon Feb 27 13:49:09 2017 +0530
files:   osaf/services/saf/amf/amfd/sutcomptype.cc
description:
amfd: fix null ptr accessing issue [#2322]


changeset:   8620:5be5a71b5069
branch:  opensaf-5.1.x
parent:  8617:37f663fdfaaa
user:Nagendra Kumar
date:Mon Feb 27 13:49:44 2017 +0530
files:   osaf/services/saf/amf/amfd/sutcomptype.cc
description:
amfd: fix null ptr accessing issue [#2322]


changeset:   8621:7e68a07b0742
tag: tip
parent:  8618:2e299171c00e
user:Nagendra Kumar
date:Mon Feb 27 13:50:04 2017 +0530
files:   src/amf/amfd/sutcomptype.cc
description:
amfd: fix null ptr accessing issue [#2322]


[staging:addb5d]
[staging:5be5a7]
[staging:7e68a0]



---

** [tickets:#2322] Amf: Amfd crashed during cold sync**

**Status:** fixed
**Milestone:** 5.0.2
**Created:** Thu Feb 23, 2017 11:33 AM UTC by Nagendra Kumar
**Last Updated:** Thu Feb 23, 2017 12:36 PM UTC
**Owner:** Nagendra Kumar


Steps to reproduce
1. Start SC-1, upload a demo app.
2. Keep 5 seconds delay at the following code:
diff --git a/src/amf/amfd/imm.cc b/src/amf/amfd/imm.cc
--- a/src/amf/amfd/imm.cc
+++ b/src/amf/amfd/imm.cc
@@ -1602,6 +1602,10 @@ unsigned int avd_imm_config_get(void)
if (avd_comptype_config_get() != SA_AIS_OK)
goto done;

+   LOG_ER("1.  Before sleep ");
+   sleep(5);
+   LOG_ER("2.  After sleep");
+
/* SaAmfSUType needed by SaAmfSGType */
if (avd_sutype_config_get() != SA_AIS_OK)
goto done;
3. Start SC-2, when it print "Before sleep". Then run the below command on SC-1:
immcfg -d 
"safMemberCompType=safVersion=1\,safCompType=AmfDemo1,safVersion=1,safSuType=AmfDemo1"

Observed behaviour
--

When SC-2 comes up after sleep, it crashes at:
Core was generated by `/usr/local/lib/opensaf/osafamfd --tracemask=0x'.
Program terminated with signal 11, Segmentation fault.
#0  sutcomptype_ccb_completed_cb(CcbUtilOperationData*) () at 
src/amf/amfd/sutcomptype.cc:131
131 if (sutcomptype->curr_num_components == 0) {
(gdb) bt
#0  sutcomptype_ccb_completed_cb(CcbUtilOperationData*) () at 
src/amf/amfd/sutcomptype.cc:131
#1  0x7f64bc2d9757 in ccb_completed_cb(unsigned long long, unsigned long 
long) () at src/amf/amfd/imm.cc:1065
#2  0x7f64bb81dd64 in imma_process_callback_info(imma_cb*, 
imma_client_node*, imma_callback_info*, unsigned long long) ()
at src/imm/agent/imma_proc.cc:2174
#3  0x7f64bb81f739 in imma_hdl_callbk_dispatch_all(imma_cb*, unsigned long 
long) () at src/imm/agent/imma_proc.cc:1732
#4  0x7f64bb81659a in saImmOiDispatch () at src/imm/agent/imma_oi_api.cc:609
#5  0x7f64bc296ab8 in main () at src/amf/amfd/main.cc:729




---

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] #2326 log : fix all cpp check issues

[tickets] [opensaf:tickets] Re: #2316 amfnd: amfnd is stuck in removing assignment in shutting down phase

[tickets] [opensaf:tickets] #2259 amf: support for si-swap admin op for N+M model ( Standbys in same su case).

[tickets] [opensaf:tickets] #2316 amfnd: amfnd is stuck in removing assignment in shutting down phase

[tickets] [opensaf:tickets] #1640 Integrate IMM service with CLM

[tickets] [opensaf:tickets] #1640 Integrate IMM service with CLM

[tickets] [opensaf:tickets] #2065 amf: support for SA_AMF_CLUSTER_RESET recommended recovery

[tickets] [opensaf:tickets] #2267 base: Add a support function for reading the FQDN

[tickets] [opensaf:tickets] #2322 Amf: Amfd crashed during cold sync

9 matches

Site Navigation

Mail list logo

Footer information