ack, perhaps adding reference to other services, e.g. IMM for configuring headless etc. can be added./Thanks HansN
On 01/05/2016 02:33 PM, Minh Hon Chau wrote: > osaf/services/saf/amf/README-HEADLESS | 62 > +++++++++++++++++++++++++++++++++++ > 1 files changed, 62 insertions(+), 0 deletions(-) > > > diff --git a/osaf/services/saf/amf/README-HEADLESS > b/osaf/services/saf/amf/README-HEADLESS > new file mode 100644 > --- /dev/null > +++ b/osaf/services/saf/amf/README-HEADLESS > @@ -0,0 +1,62 @@ > +# > +# -*- OpenSAF -*- > +# > +# (C) Copyright 2016 The OpenSAF Foundation > +# > +# This program is distributed in the hope that it will be useful, but > +# WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY > +# or FITNESS FOR A PARTICULAR PURPOSE. This file and program are licensed > +# under the GNU Lesser General Public License Version 2.1, February 1999. > +# The complete license can be accessed from the following location: > +# http://opensource.org/licenses/lgpl-license.php > +# See the Copying file included with the OpenSAF distribution for full > +# licensing terms. > +# > +# Author(s): Ericsson AB > +# > + > +GENERAL > +------- > + > +This is a description of how the AMF service handles being headless (SC down) > +and recovery (SC up). > + > +CONFIGURATION > +------------- > + > +AMF reads the "scAbsenceAllowed" attribute to determine if headless mode is > +supported. A positive integer indicates the number of seconds AMF will > tolerate > +being headless. > + > +Normally, the AMF Node Director restarts a node if there is no active AMF > +Director. If headless support is enabled, the Node Director will delay the > +restart for the duration specified in "scAbsenceAllowed". If a SC recovers > +during the period, the restart is aborted. > + > +IMPLEMENTATION DETAILS > +---------------------- > + > +While headless, state information such as component and SU restart counts > +cannot be synced to the Director. The Node Director will send these values to > +the Director once a SC recovers. > + > +LIMITATIONS > +----------- > + > +Recovery actions are limited while headless. > + > +Supported: > +* component and SU restart > + > +Limited support: > +* component and SU failover. Failover is delayed until SC recovery. > +For 2N Service Group, a standby assignment will transition > +to active directly if required. For other Service Group types, standby > +assignments are first removed, and reassigned as appropriate for the SG. > + > +Not supported: > +* node switchover and failover will result in node restart. > + > + > +SI/CSI dependencies will not be honoured while headless. > + ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
