osaf/services/saf/immsv/config/immd.conf | 31 +++++++++++++++++++++++++++++-- osaf/services/saf/immsv/config/immnd.conf | 7 +++++++ 2 files changed, 36 insertions(+), 2 deletions(-)
The patch contains new system variables in immd.conf and immnd.conf that are needed to support cloud resilience feature. diff --git a/osaf/services/saf/immsv/config/immd.conf b/osaf/services/saf/immsv/config/immd.conf --- a/osaf/services/saf/immsv/config/immd.conf +++ b/osaf/services/saf/immsv/config/immd.conf @@ -7,6 +7,12 @@ # Uncomment the next line to enable trace #args="--tracemask=0xffffffff" +# Uncomment the next line to enable info level logging +#args="--loglevel=info" + +# Uncomment the next line to enable trace AND info level logging +#args="--tracemask=0xffffffff --loglevel=info" + # Healthcheck keys export IMMSV_ENV_HEALTHCHECK_KEY="Default" @@ -27,5 +33,26 @@ export IMMSV_ENV_HEALTHCHECK_KEY="Defaul #export IMMSV_2PBE_PEER_SC_MAX_WAIT=30 -# Uncomment the next line to enable info level logging -#args="--loglevel=info" +# If the immsv is to allow absence of the IMMD service-id (indefinitely) +# then the config parameter below is to be commented in. Absent IMMD is +# part of the OpenSAF feature "Hydra" which has the goal of increasing +# OpenSAFs resilience in the face of both active and standby SC going down. +# Both SCs being absent implies that all OpenSAF director services are absent +# indefinitely, until an SC is re-established. Prior to the Hydra enhancement, +# departure of both SCs always resulted in a cluster restart. With the Hydra +# enhancement, payloads continue to provide reduced and limited service untill +# an SC-active is re-established. For the IMM service, Hydra is configured by +# commenting in the environment variable below. +# Support for absent IMMD is incompatible with 2PBE. If both are configured +# then 2PBE will win and the absence of IMMD feature will be ignored. An error +# message is printed in this case to the syslog at startup. +# Allowing absent immd is a configuration choice impacting all OpenSAF +# services, not just the immsv. If it is to be allowed then it is not +# sufficient to only configure the immsv for absent immd. +# The level of service that is provided during absent SC depends on the +# particular service. In the case of the IMM service, the service provided +# during IMMD absence is in essence only the reading of config data. +#export IMMSV_SC_ABSENCE_ALLOWED=900 + + + diff --git a/osaf/services/saf/immsv/config/immnd.conf b/osaf/services/saf/immsv/config/immnd.conf --- a/osaf/services/saf/immsv/config/immnd.conf +++ b/osaf/services/saf/immsv/config/immnd.conf @@ -69,5 +69,12 @@ export IMMSV_MAX_WAIT=3 # Healthcheck keys export IMMSV_ENV_HEALTHCHECK_KEY="Default" +# If IMMSV_USE_SHARED_FS is set to zero or is not set, PBE will perform object +# checks when PBE starts. This is not necessary when PBE is stored on external +# shared file system, where only one PBE exists. +# This variable is ignored if IMMSV_SC_ABSENCE_ALLOWED is not set or is set to +# zero value. +#export IMMSV_USE_SHARED_FS=1 + # Uncomment the next line to enable info level logging #args="--loglevel=info" ------------------------------------------------------------------------------ _______________________________________________ Opensaf-devel mailing list Opensaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-devel
