On 05/26/2011 03:50 PM, Steven Dake wrote:
> Hi,
> 
> It seems clear from the overwhelming amount of complaining regarding
> redundant ring that this is something we need to take up in development
> and support more actively upstream sooner rather then later.
> 
> Jan Friesse (Honza) will be leading an effort to do the following:
> 1. validate rollovers of the token sequence id and message ids work
> properly in a redundant ring setup.
> 2. finish the patch for automatic ring recovery I started with Jiaju's help.
> 3. add that feature to our automated test cases.
> 
> I can't offer specifics about dates, since the work is somewhat
> undefined, but I'm hopeful this completes in the next 8-12 weeks and
> results in a new y stream (1.5) with this specific feature.
> 
> As for 1.4 (major feature is snmp), Honza is in process of running
> Coverity against the tree to sort out any remaining nitpicks picked up
> by the scanner.  Once that is done, the corosync project will release 1.4.
> 
> Regards
> -steve

I'll be happy to test this when the time comes. I'd love to see this
feature implemented.

-- 
Digimer
E-Mail: digi...@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org
"I feel confined, only free to expand myself within boundaries."
_______________________________________________
Openais mailing list
Openais@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/openais

Reply via email to