- **Type**: defect --> discussion
---
** [tickets:#2151] osaf: system in not in correct state during Act controller
comming up**
**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Mon Oct 31, 2016 10:54 AM UTC by Nagendra Kumar
**Last Updated:** Mon Oct 31, 2016 10:56 AM UTC
- **Milestone**: 5.2.FC --> never
---
** [tickets:#1558] amf: use nullptr instead of NULL macros**
**Status:** invalid
**Milestone:** never
**Created:** Fri Oct 23, 2015 04:28 AM UTC by Long HB Nguyen
**Last Updated:** Tue Aug 30, 2016 03:25 AM UTC
**Owner:** Long HB Nguyen
Using nullptr
- **status**: unassigned --> review
- **assigned_to**: Nagendra Kumar
---
** [tickets:#2078] amfd: remove db_template.h**
**Status:** review
**Milestone:** 5.2.FC
**Created:** Wed Sep 28, 2016 07:24 AM UTC by Gary Lee
**Last Updated:** Wed Sep 28, 2016 07:24 AM UTC
**Owner:** Nagendra Kumar
I think, the discussion got deviated by the usage of PL string in nodes.cfg.
On the fist node in the opensaf cluster, the following info is filled up in
opensaf cfg files.
cat /usr/share/opensaf/immxml/nodes.cfg
SC node-1 node-1
SC node-2 node-2
PL node-3 node-3
PL node-4 node-4
PL node-5
Hi Srikanth,
Immxml tool is used for creating the first basic IMM xml database for starting
OpenSAF.
As I remember, according to the first column SC/PL, immxml tools use a template
for SC or PL to create imm.xml file.
>From my point of view, if a node is misconfigured, the node reboot is
Zoran,
Node reboot recovery is to be followed, when the system cannot recover from
the observed fault. For a fault like amfd crashing, node reboot can be
followed. But in the current scenario, upon reboot same configuration exists
and node shall go for reboot as opensafd is enabled in the
- **Milestone**: 5.2.FC --> never
---
** [tickets:#1571] AMF: Use std::maps instead of Patricia trees**
**Status:** invalid
**Milestone:** never
**Created:** Wed Oct 28, 2015 02:39 AM UTC by Long HB Nguyen
**Last Updated:** Tue Aug 30, 2016 03:28 AM UTC
**Owner:** Long HB Nguyen
Use
- **status**: unassigned --> review
- **assigned_to**: Nagendra Kumar
---
** [tickets:#1918] AMF: Informative logging**
**Status:** review
**Milestone:** 5.2.FC
**Created:** Fri Jul 15, 2016 11:30 AM UTC by Minh Hon Chau
**Last Updated:** Mon Aug 29, 2016 08:09 PM UTC
**Owner:** Nagendra
Hi Srikanth, Thanks for your comments. That means when we are creating
headless situation, it should be fault based and not 'opensafd stop'. Then
definetely, this situation will not arise.
@Others: Any suggestion/comment ?
---
** [tickets:#2151] osaf: system in not in correct state during
- **status**: assigned --> invalid
---
** [tickets:#2154] smf: non backward compatible name change for ExecCtrlCopy**
**Status:** invalid
**Milestone:** 5.1.1
**Created:** Mon Oct 31, 2016 03:18 PM UTC by Rafael
**Last Updated:** Mon Oct 31, 2016 03:34 PM UTC
**Owner:** Rafael
there was a
There are three issues in the ticket raised.
1) As per the ticket #2094 comments, "/etc/init.d/opensafd stop" is not a
proper way to bring down opensaf. It is suggested that to bring down a faulty
node, CLM lock on the node can be performed and later reboot command can be
invoked manually.
---
** [tickets:#2156] build: Remove the dtlog directory**
**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Tue Nov 01, 2016 01:47 PM UTC by Anders Widell
**Last Updated:** Tue Nov 01, 2016 01:47 PM UTC
**Owner:** nobody
The directory /var/log/opensaf/dtlog is not used and should
---
** [tickets:#2155] base: Use timerfd and ppoll libc functions when available**
**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Tue Nov 01, 2016 01:45 PM UTC by Anders Widell
**Last Updated:** Tue Nov 01, 2016 01:45 PM UTC
**Owner:** nobody
The timerfd and ppoll functions are
---
** [tickets:#2157] mds: Decouple Node ID from TIPC address**
**Status:** unassigned
**Milestone:** future
**Created:** Tue Nov 01, 2016 03:10 PM UTC by Anders Widell
**Last Updated:** Tue Nov 01, 2016 03:10 PM UTC
**Owner:** nobody
Currently there is a connection between the OpenSAF
- Description has changed:
Diff:
--- old
+++ new
@@ -2,7 +2,7 @@
When standby cold sync occurs, there may have a chance that
node creation information is missed in standby node. Active node sending
node information to standby node (checkpointing) will lead to a standby amfd
---
** [tickets:#2158] AMF: IMMND dies at Opensaf start up phase causes AMFD
heartbeat timeout**
**Status:** unassigned
**Milestone:** 5.0.2
**Created:** Wed Nov 02, 2016 05:20 AM UTC by Minh Hon Chau
**Last Updated:** Wed Nov 02, 2016 05:20 AM UTC
**Owner:** nobody
**Attachments:**
-
16 matches
Mail list logo
