Build System: Elimination of IFSv service in OpenSAF

[marioa]

IFSv service is changed to use IMM service instead of MASv.
Work includes:

• removing IFSv dependency to MASv (code removal)
• creating IFSv class model in imm.xml schema
• Adapting IFSv to use IMM interface (OI & OM) for reading configuration data and providing runtime information (same classes as IFSv supports today via MASv)

[murthy]

Changed the ticket summary

In a move to discourage offering of proprietary services to users, OpenSAF project is going to deprecat IFSv service. Following is the impact

- Elimination of IFSv service from the OpenSAF build system
- Removal of ifsv_papi.h from include folder
- Elimination of IFSv related scripts (vip_installer)

[jfournier]

Work in progress:

 http://planck.opensaf.org/~jfournier/hg/opensaf-modularity/rev/41ace1db28fd

[jfournier]

http://devel.opensaf.org/hg/opensaf-staging/rev/4b21c0cceba8

[murthy]

Fixed in OpenSAF4.0 Beta1

[jfournier]

For those who were wondering what to use to replace some functionalities of IFSv, the keepalived project provides facility to the Linux Virtual Server project.

Within the keepalive project, there's an independent VRRPv2 stack which is the standard protocol to manage virtual ip master/slave and way more.

It's possible to configure keepalived to only expose the VRRP stack in userspace and not using the other HA functionalities it offers.

 http://www.keepalived.org/

[anonymous]

Replying to jfournier:

For those who were wondering what to use to replace some functionalities of IFSv, the keepalived project provides facility to the Linux Virtual Server project.

[...]

Hello, thanks for a valuable pointer. Does that mean that one would run keepalived outside of opensaf framework entirely?