- **status**: fixed --> unassigned
---
** [tickets:#232] MDS/TCP should be the default once TIPC management is moved
out**
**Status:** unassigned
**Created:** Wed May 15, 2013 11:10 AM UTC by Mathi Naickan
**Last Updated:** Fri Oct 18, 2013 03:11 AM UTC
**Owner:** A V Mahesh (AVM)
Changed 10 months ago by mahesh
owner changed from murthy to mahesh
Hans , following are my thoughts to make TCP as the default transport please
provide your inputs.
Option 1 : Binaries built with both TIPC and TCP footprint
./configure builds the opensaf rpms where the binaries have support for both
TCP or TIPC binaries.But, the "default configuration" will be generated for TCP.
For TIPC transport the nid_tipc will be provided as a sample file.
If wishes to run with TIPC transport need to do the necessary configuration
changes.
configuration in nid.conf
change the nodeinit.conf if he wishes to use the nid_tipc sample script by
adding and entry to the nodeinit.conf file and comment out the entry related to
TCP.
OR
change the soft link of nodeinit.conf form nodeinit.conf.controller to
nodeinit.conf.controller.tipc if ok to go with new
nodeinit.conf.controller.tipc configuration file ?
follow-up: ↓ 4 Changed 10 months ago by hafe
Here's what I think:
In #2512 I say that opensaf should provide under samples (for example) a tipc
init script for those who wish to use tipc. The old nid_tipc script should be
removed (or renamed since it contains the mds log rotation)
nodeinit.conf should contain a single osaf-mds entry that in the MDS/TCP case
calls "osaf-dtm start" and then does mds log monitoring. In the MDS/TIPC case
it just skips the "osaf-dtm start" call. Then there is an end to the sed-ding
of nodeinit.conf from the opensafd start script (which is crazy...). I have
mentioned this before. The sed has been the source for problems.
Then dh_monitoring should be renamed "osaf-dh-monitor" so that all daemons in
the system uses the osaf prefix.
in reply to: ↑ 3 Changed 9 months ago by mathi
Replying to hafe:
Here's what I think:
In #2512 I say that opensaf should provide under samples (for example) a tipc
init script for those who wish to use tipc. The old nid_tipc script should be
removed (or renamed since it contains the mds log rotation)
nodeinit.conf should contain a single osaf-mds entry that in the MDS/TCP case
calls "osaf-dtm start" and then does mds log monitoring. In the MDS/TIPC case
it just skips the "osaf-dtm start" call. Then there is an end to the sed-ding
of nodeinit.conf from the opensafd start script (which is crazy...). I have
mentioned this before. The sed has been the source for problems.
Then dh_monitoring should be renamed "osaf-dh-monitor" so that all daemons in
the system uses the osaf prefix.
w.r.t moving the nid_tipc into the samples area, actually we dont have to that.
i.e. As suggestged here, when a single/common script is used in the
nodeinit.conf, lets call it as 'osaf-transport' (not really 'osaf-mds' because
its not entirely mds that's getting started here), then this script can inturn
invoke the startup of tcp(default) or tipc accordingly based on what the user
configured in the nid.conf
Changed 6 months ago by mahesh
patch_waiting changed from no to yes
Changed 3 months ago by hafe
milestone changed from 4.3.GA to future_releases
TLC decision/preparation for 4.3 release
Changed 7 weeks ago by mathi
milestone changed from future_releases to 4.4.GA
Changed 5 weeks ago by hafe
Some quality issues that should be fixed before making MDS/TCP the default
http://devel.opensaf.org/ticket/3113
http://devel.opensaf.org/ticket/2707
http://devel.opensaf.org/ticket/3097
3097 could be due to one of the valgrind reported errors in 3113
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
