- **labels**: 5.0 --> 5.0, #439, #79
- **summary**: Support for multiple standby controllers elected to run in 
different availability zones --> Support for multiple hot-standby controllers 
elected to run in different availability zones
- Description has changed:

Diff:

~~~~

--- old
+++ new
@@ -1,12 +1,13 @@
-The ticket is to track/enable support for multiple hot standby controllers 
that would be running(by configuration or election) on different 'availability 
zones'(for eg:- 5 of them) in cloud deployments.
+The ticket is an extension of https://sourceforge.net/p/opensaf/tickets/79/
 
-To be able to support multiple usecases around enhanced cluster management and 
cloud deployments that might require to be able to handle double faults on 
controller nodes.
+To be able to support usecases involving 
+a) flexible deployment based on special hardware requirements to deploy for 
more than two system controllers
+b) multiple nodes failing simultaneously in virtualized environments (cattles)
 
-- First and foremost would be  to check (and or prototype) the status of MBCSv 
to synchup with multiple standbys. (it should work by default!)
-
-- clustering changes
-
-- packaging changes, ... more.
-
-This is a place holder ticket
+ The scope of this ticket is to 
+ (a) support multiple hot-standby system controllers
+ (b) use RAFT adaptation layer(refer #439) for leader election and fencing and 
arbitration
+ (c) harden the checkpointing mechanism for maintaining hot standbys - 
possibly use RAFT for maintaining hot standbys!
  
+ With tickets #79, #439 in place, this ticket would enable opensaf to be 
flexibly deployed with spares and or multiple standby system controllers.
+ 

~~~~




---

** [tickets:#1170] Support for multiple hot-standby controllers elected to run 
in different availability zones**

**Status:** assigned
**Milestone:** 5.0.FC
**Labels:** 5.0 #439 #79 
**Created:** Wed Oct 15, 2014 08:37 AM UTC by Mathi Naickan
**Last Updated:** Sun Nov 01, 2015 09:36 PM UTC
**Owner:** Mathi Naickan


The ticket is an extension of https://sourceforge.net/p/opensaf/tickets/79/

To be able to support usecases involving 
a) flexible deployment based on special hardware requirements to deploy for 
more than two system controllers
b) multiple nodes failing simultaneously in virtualized environments (cattles)

 The scope of this ticket is to 
 (a) support multiple hot-standby system controllers
 (b) use RAFT adaptation layer(refer #439) for leader election and fencing and 
arbitration
 (c) harden the checkpointing mechanism for maintaining hot standbys - possibly 
use RAFT for maintaining hot standbys!
 
 With tickets #79, #439 in place, this ticket would enable opensaf to be 
flexibly deployed with spares and or multiple standby system controllers.
 


---

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.
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to