Hi William R Elliot, On 3/14/2017 6:18 PM, William R Elliott wrote:
> How difficult would it be to bring in all the TCP fixes you mentioned in the > later releases in to 4.4.0? Opensaf 4.4.0 deprecated version, so no more supported in Opensaf community . -AVM On 3/14/2017 6:18 PM, William R Elliott wrote: > Hi, > Thanks for the quick response. > > I have a follow up question please. How difficult would it be to bring in > all the TCP fixes you mentioned in the later releases in to 4.4.0? > > > thanks > > ------------------- > William Elliott, Senior Analyst, R&D > Netcracker Technology > > +1 (407) 708-5059 | ext. 3859 | office > +1 (407) 603-3039 | home > > -----Original Message----- > From: A V Mahesh [mailto:[email protected]] > Sent: Monday, March 13, 2017 11:59 PM > To: William R Elliott; [email protected] > Subject: Re: [users] Multicast Recommendation > > Hi William R Elliot, > > We improved/fixed considerable issue in TCP transport since 4.4, so we > suggest to use latest release, even it will be easy to support you with > latest code, if you facing any issues. > > -AVM > > On 3/14/2017 3:30 AM, William R Elliott wrote: >> Hello All, >> I am currently using opensaf 4.4.0 with TCP as the transport mechanism. I'm >> investigating the best way to use the multicast feature of opensaf since I >> need to run an opensaf cluster broadcasting across two different subnets in >> a production environment. So what would be really helpful is which of the >> following approaches would the experienced members of this forum recommend >> and why: >> 1) Use the existing opensaf 4.4.0 multicast functionality because it is >> robust and works very well so there’s no need going through an upgrade >> effort and all that it involves. >> >> 2) Update to the latest version of opensaf because it is more reliable than >> version 4.4.0's multicast functionality and would be worth the trouble of >> going through the regression testing and upgrade effort that would be >> required. >> >> >> thanks! >> >> >> >> ------------------- >> William Elliott, Senior Analyst, R&D >> Netcracker Technology >> >> +1 (407) 708-5059 | ext. 3859 | office >> +1 (407) 603-3039 | home >> >> [https://www.netcracker.com/assets/img/netcracker-social-final.png] ƕ >> >> >> >> ________________________________ >> The information transmitted herein is intended only for the person or entity >> to which it is addressed and may contain confidential, proprietary and/or >> privileged material. Any review, retransmission, dissemination or other use >> of, or taking of any action in reliance upon, this information by persons or >> entities other than the intended recipient is prohibited. If you received >> this in error, please contact the sender and delete the material from any >> computer. >> ---------------------------------------------------------------------- >> -------- Check out the vibrant tech community on one of the world's >> most engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Opensaf-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/opensaf-users > > > ________________________________ > The information transmitted herein is intended only for the person or entity > to which it is addressed and may contain confidential, proprietary and/or > privileged material. Any review, retransmission, dissemination or other use > of, or taking of any action in reliance upon, this information by persons or > entities other than the intended recipient is prohibited. If you received > this in error, please contact the sender and delete the material from any > computer. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
