- **summary**: Support for multiple hot-standby controllers elected to run in
different availability zones --> Support for multiple hot-standby controllers
- **Milestone**: 5.1.FC --> 5.2.FC
---
** [tickets:#1170] Support for multiple hot-standby controllers**
**Status:** accepted
**Milestone:** 5.2.FC
**Labels:** 5.0 #439 #79 raft
**Created:** Wed Oct 15, 2014 08:37 AM UTC by Mathi Naickan
**Last Updated:** Mon Apr 11, 2016 10:15 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 ACTIVE SC election and to
perform fencing and arbitration actions
(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.
More details to come.
A prototyping of multiple-standbys is available at
https://sourceforge.net/u/praveenmalviya/5.0_prototypes/ci/default/tree/
---
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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
