- **summary**: IMM: Support the saImmOiTimeout config attribute in the
SaImmMngt class --> IMM: Configigurable OI callback server-side timeout per
OI-handle.
- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -1,23 +1,36 @@
-There is a need for configurable timeout for IMMND OI upcalls, i.e.
-the timeout for how long the imm-service will wait for a reply on
-an OI upcall. Currently there is a hardwired timer of 6 seconds.
+There is a need for configurable timeout for IMMND OI callbacks,
+i.e. the timeout for how long the imm-service will wait for a reply on
+an OI callback. Currently there is a hardwired timer of 6 seconds.
Version A.03.01 of the SAF IMM standard does in fact define such
an attribute 'saImmOiTimeout', which is one reason that A.03.01 is
-actually not backwards compatible with A.02.01 (schema upgrades
-are not supported in A.03.01).
+actually not backwards compatible with A.02.01 (Schema upgrades
+are not supported in the official A.03.01 standard. Schema upgrades
+are however supported by the OpenSAF IMM).
-Actually the 'saImmOiTimeout' is already present in the definition
-of the SaImmMngt? class used by the OpenSAF IMM in 4.1. This despite
+The 'saImmOiTimeout' is already present in the definition
+of the SaImmMngt class since OpenSAF 4.1. This despite
that the OpenSAF IMM does not support the A.03.01 version.
-But the imm service ignores this attribute currently.
+The imm service ignores this attribute currently.
-This enhancement proposes that the imm service shall respect the
-setting of this attribute.
+But the concept of having *one* config attribute controlling the timeout
+for *all* OIs in the system, has severe problems. See comments below.
-This enhancement is related to the more general issue of providing
-an OI for the imm service itself.
-http://devel.opensaf.org/ticket/503
+Because of this, we alter the proposed solution to the problem.
+Instead of using this single config attribute, we will use an environment
+variable recognized by the IMMA library. This will follow the same pattern
+as the existing IMMA_SYNCR_TIMEOUT that configures the timeout for
+blocking downcalls (in both the OM and OI libraries).
+
+A new environment variable IMMA_OI_CALLBACK_TIMEOUT will be recognized by
+the OI library. Just as for the existing IMMA_SYNCR_TIMEOUT, this environment
+variable is sampled by the SaImmOiInitialize function for initializing an
+oi-handle. The handle will have that timeout associated with it for the rest
+of its lifetime. Different OI handles can have different timeouts by changing
+the value of IMMA_OI_CALLBACK_TIMEOUT prior to each saImmOiIntitialize.
+
+The library will send the handles callback timeout-value down to the server
+as an added part to the message used by saImmOiImplementerSet
Migrated from:
http://devel.opensaf.org/ticket/2021
~~~~
---
** [tickets:#16] IMM: Configigurable OI callback server-side timeout per
OI-handle.**
**Status:** unassigned
**Milestone:** future
**Created:** Tue May 07, 2013 08:28 AM UTC by Anders Bjornerstedt
**Last Updated:** Tue Oct 29, 2013 12:09 PM UTC
**Owner:** Anders Bjornerstedt
There is a need for configurable timeout for IMMND OI callbacks,
i.e. the timeout for how long the imm-service will wait for a reply on
an OI callback. Currently there is a hardwired timer of 6 seconds.
Version A.03.01 of the SAF IMM standard does in fact define such
an attribute 'saImmOiTimeout', which is one reason that A.03.01 is
actually not backwards compatible with A.02.01 (Schema upgrades
are not supported in the official A.03.01 standard. Schema upgrades
are however supported by the OpenSAF IMM).
The 'saImmOiTimeout' is already present in the definition
of the SaImmMngt class since OpenSAF 4.1. This despite
that the OpenSAF IMM does not support the A.03.01 version.
The imm service ignores this attribute currently.
But the concept of having *one* config attribute controlling the timeout
for *all* OIs in the system, has severe problems. See comments below.
Because of this, we alter the proposed solution to the problem.
Instead of using this single config attribute, we will use an environment
variable recognized by the IMMA library. This will follow the same pattern
as the existing IMMA_SYNCR_TIMEOUT that configures the timeout for
blocking downcalls (in both the OM and OI libraries).
A new environment variable IMMA_OI_CALLBACK_TIMEOUT will be recognized by
the OI library. Just as for the existing IMMA_SYNCR_TIMEOUT, this environment
variable is sampled by the SaImmOiInitialize function for initializing an
oi-handle. The handle will have that timeout associated with it for the rest
of its lifetime. Different OI handles can have different timeouts by changing
the value of IMMA_OI_CALLBACK_TIMEOUT prior to each saImmOiIntitialize.
The library will send the handles callback timeout-value down to the server
as an added part to the message used by saImmOiImplementerSet
Migrated from:
http://devel.opensaf.org/ticket/2021
---
Sent from sourceforge.net because [email protected] 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.
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
