Hi Neel,
Reviewed the patch.
Ack from me.
BR,
Hung Nguyen - DEK Technologies
--------------------------------------------------------------------------------
From: Neelakanta Reddy reddy.neelaka...@oracle.com
Sent: Wednesday, September 14, 2016 3:46PM
To: Zoran Milinkovic, Hung Nguyen
zoran.milinko...@ericsson.com, hung.d.ngu...@dektech.com.au
Cc: Opensaf-devel
opensaf-devel@lists.sourceforge.net
Subject: [PATCH 1 of 1] imm:updated README for 5.1 [#2034]
osaf/services/saf/immsv/README | 39 +++++++++++++++++++++++++++++++++++++++
1 files changed, 39 insertions(+), 0 deletions(-)
diff --git a/osaf/services/saf/immsv/README b/osaf/services/saf/immsv/README
--- a/osaf/services/saf/immsv/README
+++ b/osaf/services/saf/immsv/README
@@ -2866,6 +2866,45 @@ IMMSV_MAX_CCBS 10000
The user can not configure the values less than the default values.
+Veteran max timeout is made cofigurable in case of sc Absence (5.1)
+===================================================================
+http://sourceforge.net/p/opensaf/tickets/1974/
+
+IMMSV_SC_ABSENCE_VETERAN_MAX_WAIT is the IMMD waits for veteran IMMNDs after
sc absence.
+If IMMD processes the intro messages from new IMMNDs before the intro
+messages from veteran IMMNDs, IMM service will start to load from file
+instead of syncing data from veteran nodes. The
IMMSV_SC_ABSENCE_VETERAN_MAX_WAIT
+will prevent that from happening.
+
+Note that during a fresh cluster startup, IMMD also waits for veteran IMMNDs.
+Setting this value to large will slow down the cluster startup.
+This timeout only used with sc absence enabled. When sc absence is disabled,
+IMMD will not wait for the veteran IMMNDs.
+
+The IMMSV_SC_ABSENCE_VETERAN_MAX_WAIT is present in immd.conf.
+The default value (when the environment variable is not set) is 3 seconds.
+
+export IMMSV_SC_ABSENCE_VETERAN_MAX_WAIT=3
+
+immcfg allows admin-owner in explicit commit mode (5.1)
+===============================================================
+https://sourceforge.net/p/opensaf/tickets/1383/
+
+immcfg in explicit commit mode, will not be able to set adminOwnerName.
+This enhancemnt removes the restriction.
+
+immcfg -o adminOwnerName.
+
+--ccb-apply and --ccb-abort will finalize the admin owner.
+if -o option is not specified default admin-owner is considered.
+
+immadm can explicitly set ReleaseOnFinalize (5.1)
+=======================================================
+https://sourceforge.net/p/opensaf/tickets/1937/
+
+with this enhancement immadm introduces a new flag '-r' for setting ROF
(Release On Finalize) flag.
+The default value for ROF (when -r option is not specified) is SA_FALSE.
+
Notes on upgrading from OpenSAF 5.0 to OpenSAF 5.1
================================================================
OpenSAF5.1 makes the IMM attributes as configurable (#195).
------------------------------------------------------------------------------
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
