Hi!

Have you had time to look at this yet?

regards,
Anders Widell

On 03/18/2016 05:14 PM, Anders Widell wrote:
>   00-README.conf |  14 ++++++++++----
>   README         |  17 +++++++++--------
>   2 files changed, 19 insertions(+), 12 deletions(-)
>
>
> diff --git a/00-README.conf b/00-README.conf
> --- a/00-README.conf
> +++ b/00-README.conf
> @@ -112,7 +112,9 @@ Notes:
>       In the case of 'make install', do the steps listed in
>       'Steps to configure opensaf user' above.
>   
> -(e) Use of MDS subslot ID needs to be enabled, add TIPC_USE_SUBSLOT_ID=YES
> +(e) If use of MDS subslot ID needs to be enabled, add TIPC_USE_SUBSLOT_ID=YES
> +    Note that the use of subslot ID is deprecated and should not be enabled
> +    in new installations.
>   
>   (f) Time supervision of local node reboot should be disabled or changed.  
> Change
>     OPENSAF_REBOOT_TIMEOUT to the desired number of seconds before a reboot is
> @@ -167,12 +169,16 @@ a new/second node in the cluster, this m
>   value - for e.g. a value of 2 as below:
>       % echo 2 > $pkgsysconfdir/slot_id
>   
> +Starting with OpenSAF version 5.0, the maximum supported value for slot_id is
> +4095 when using the flat addressing scheme (i.e. when the use of subslot ID 
> is
> +disabled). Prior to OpenSAF 5.0, the maximum supported value for slot_id was
> +255.
> +
>   
> *******************************************************************************
>   subslot_id
>   
> -The subslot_id shall specify a unique value that represents a physical 
> sub-slot
> -identifier for the node in a chassis environment. It is normally never 
> changed
> -from what's installed.
> +The use of subslot ID is disabled by default. When disabled, subslot_id must 
> be
> +set to 15 (which is the default value) on all nodes in the cluster.
>   
>   
> *******************************************************************************
>   chassis_id
> diff --git a/README b/README
> --- a/README
> +++ b/README
> @@ -284,21 +284,22 @@ Building `OpenSAF'
>   Some features needs to be configured at build time but don't have configure
>   support, these are explained here.
>   
> -1) Configure a non flat MDS addressing scheme (optional) when TIPC is chosen
> -as the transport
> +1) Configure a non flat MDS addressing scheme (deprecated)
>   
> -In the default (from 4.3) addressing scheme, TIPC node addresses looks like
> -1.1.1, 1.1.2 etc.
> +In the default (from OpenSAF 4.3 onwards) addressing scheme, TIPC node 
> addresses
> +looks like 1.1.1, 1.1.2 etc, and the slot_id can be in the range from 1 and 
> up
> +to 4095 (though note that prior to OpenSAF 5.0, the maximum supported slot_id
> +was 255).
>   
> -To re-enable the old (pre 4.3) non flat addressing, configure the constant
> -MDS_USE_SUBSLOT_ID=1 at configure time as in:
> +To re-enable the old (pre OpenSAF 4.3) non flat addressing, configure the
> +constant MDS_USE_SUBSLOT_ID=1 at configure time as in:
>   
>       % ./configure CPPFLAGS="-DMDS_USE_SUBSLOT_ID=1 ..."
>   
>   In the non flat scheme, the slot ID is shifted up 4 bits and subslot ID is
>   added in the 4 LSB. The consequence of this is reduced number of
> -addressable TIPC nodes in the cluster. This scheme is more likely to be used
> -in xTCA type of systems and produces node addresses like 1.1.31, 1.1.47 etc.
> +addressable nodes in the cluster. This scheme is more likely to be used
> +in xTCA type of systems and produces TIPC addresses like 1.1.31, 1.1.47 etc.
>   
>   More configuration is needed, see nid.conf in 00-README.conf
>   
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
> _______________________________________________
> Opensaf-devel mailing list
> Opensaf-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/opensaf-devel
>


------------------------------------------------------------------------------
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

Reply via email to