Ack, We could also update the README w.r.t the steps to generation of imm.xml By giving an example of how to configure for more than 2 SCs.
Thanks, Mathi. > -----Original Message----- > From: Anders Widell [mailto:anders.wid...@ericsson.com] > Sent: Tuesday, April 12, 2016 7:52 PM > To: Mathivanan Naickan Palanivelu > Cc: opensaf-devel@lists.sourceforge.net > Subject: [PATCH 1 of 1] osaf: Update README files for supporting more than > two system controllers [#79] > > 00-README.conf | 32 ++++++++++++++++++++++++++++++++ > README | 22 ++++++++++++---------- > 2 files changed, 44 insertions(+), 10 deletions(-) > > > Update the README files to reflect the fact that the number of system > controller nodes in the cluster is no longer limited to two. Also mention the > new options OSAF_AMF_MIN_CLUSTER_SIZE and > CLMNA_ELECTION_DELAY_TIME in amfd.conf and clmna.conf, respectively. > > diff --git a/00-README.conf b/00-README.conf > --- a/00-README.conf > +++ b/00-README.conf > @@ -35,6 +35,38 @@ 10) chgrp -R opensaf /var/log/opensaf Following is the > brief description of each such configuration file. > > > ********************************************************** > ********************* > +amfd.conf > + > +This file contains configuration options for the AMF director. This > +file has to be modified in the following cases: > + > +OSAF_AMF_MIN_CLUSTER_SIZE should be set to the minimum number of > nodes > +with system controller capability that you wish to have in the system. > +AMF will reject attempts to delete a node from the IMM configuration if > +the total number of such nodes would fall below this configured limit. > + > + > +********************************************************* > ************** > +******** > +clmna.conf > + > +This file contains configuration options for the CLM node agent. This > +file has to be modified in the following cases: > + > +CLMNA_ELECTION_DELAY_TIME should be set to the time in milliseconds > +without any active or standby system controller node that OpenSAF will > +wait before starting an election for a new active system controller. > +CLMNA will detect the presence of active and standby system controllers > +in the cluster. If no active or standby system controller has been seen > +during the configured time period, CLMNA will initate an election with > +the own node as a candidate for a new active system controller. Note > +that lowering this value will increase the risk for split-brain. Values > +lower than 5000 are not recommended for clusters with more than two > +system controllers. For legacy installations with only two system > +controller nodes, the default delay of 200 ms should be sufficient. For > +systems with a very large number of configured system controller nodes > and/or with unreliable network connections, values larger than 5000 may be > needed. > + > + > +********************************************************* > ************** > +******** > dtmd.conf > > This file contains MDS/TCP configuration parameters. > diff --git a/README b/README > --- a/README > +++ b/README > @@ -26,10 +26,11 @@ related to your operating system. > `OpenSAF' Architecture Overview > =============================== > > -`OpenSAF' software is distributed in nature. There is a Controller node, > which is -the central entity in the cluster which will control all the other > Payload nodes -in the HA cluster. In the HA cluster there are two System > Controllers running in -Active/Standby mode. > +`OpenSAF' software is distributed in nature. In the HA cluster there > +are two types of nodes: System Controllers and Payloads. One system > +controller will be running in Active mode, another system controller > +will be running in Standby mode, and the rest of the system controllers > +(if any) will be spares that are ready to take over as Active or Standby in > case of a fault. > > The `OpenSAF' software is divided in to following classes of Modules: > > @@ -833,12 +834,13 @@ Admin Operations on OpenSAF SUs From OpenSAF > release 4.4 onwards, the AMF admin operations lock, lock-in, unlock, unlock- > in is allowed to be performed on the OpenSAF SUs (i.e. > safSu=<nodename>,safSg=2N,safApp=OpenSAF > -safSu=<nodename>,safSg=NoRed,safApp=OpenSAF) > -However, these commands should be restrictively used, like running them - > from a SMF campaign. When running this from an SMF campaign, -OpenSAF > shall support the behaviour only when used under -the supported usecases > of OpenSAF. At this point of time, -there is no evident usecase to support > this. > +safSu=<nodename>,safSg=NoRed,safApp=OpenSAF) However, these > commands > +should be restrictively used, like running them from a SMF campaign. > +When running this from an SMF campaign, OpenSAF shall support the > +behaviour only when used under the supported usecases of OpenSAF. At > +this point of time, there is no evident usecase to support this. Also > +note that locking of the 2N SU is currently not supported when the > +system is configured with more than two system controller nodes. > > Linux Distro-Specific Notes > =========================== ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Opensaf-devel mailing list Opensaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-devel
