#228 Populate saClmNodeAddress and saClmNodeAddressFamily in NodeInfo when TCP is the transport

[Mathi Naickan]

Placeholder for unsupported attributes.
Background:
The current CLM(4.**) was uplifted from B.01.01 and was separated from the AMFD process(during OpenSAF 3.0). The scope was primarily to provide cluster membership services and relies on MDS -tipc/tcp for cluster management.

Some attributes are not supported during the contribution in 4.0.

Now that MDS/TCP supports IPV6 and IPv4 and relatively more stable, CLM could provide support for attributes like

saClmNodeAddressFamily
saClmNodeCurrAddressFamily
saClmNodeAddress
saClmNodeCurrAddress

and any other unsupported attribute.

It will be an interesting task to pass on user configured saClmNodeAddress
saClmNodeCurrAddress attributes down to the MDS and to the OS and vice-versa.

[Mathi Naickan]

The scope of this ticket is to support the saClmNodeAddress and saClmNodeAddressFamily. There is already code to encode/decode these two attributes, only that the value has to be filled in the callbacks. These two attributes should reflect the user configured address and addressfamily on each node.
There is no plan to possibility yet to support runtime modification to these two config attributes.

[Mathi Naickan]

Patch has been floated to support saClmNodeAddress and saClmNodeAddressFamily as configured by the user (when starting OpenSAF). It will be upto the user to ensure they use the same ip in imm.xml and in dtmd.conf.

https://sourceforge.net/p/opensaf/mailman/opensaf-devel/thread/patchbomb.1388385189%40opensaf-VirtualBox/#msg31794093
https://sourceforge.net/p/opensaf/mailman/opensaf-devel/thread/e9c169e0b9904348f77b.1388385190%40opensaf-VirtualBox/#msg31794094

[Mathi Naickan]

[staging:d43fd2]

changeset: 4775:d43fd2ea1cea
user: Mathivanan N.P.mathi.naickan@oracle.com
date: Thu Jan 02 22:14:35 2014 +0530
summary: clm: fill saClmNodeAddress and saClmNodeAddressFamily with ip info [#228]