- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -1,19 +1,17 @@
Migrated from http://devel.opensaf.org/ticket/2101
-Rationale
----------
+This ticket and subsequent ticket
https://sourceforge.net/p/opensaf/tickets/1170/ is to support
+the following two use scenarios
+a) flexible deployment based on special hardware needs for more than one
system controllers
+b) multiple nodes failing simultaneously
-Instead of having specialized system controller nodes, the idea is that all
nodes are born equal and they all have the potential of taking on the system
controller role. This makes sense in (but its usefulness is not limited to) a
cloud deployment, where OpenSAF runs on a collection of compute nodes, and from
an outside perspective no particular node is any different from the other nodes.
+The following is the scope of this ticket:
-Expectations
----------
-
-* It will be possible to configure more than two nodes as system controllers.
-* The cluster can start and restart as long as any non-empty subset of the
configured system controller nodes is present (i.e. there are no dedicated
controller nodes that are required to be present in order to start the system)
+* It will be possible to configure nodes termed as spares (to the system
controller group of nodes).
* If one of the system controller nodes dies, another "spare" system contoller
node (if there is any available) will be get an assignment (active / standby).
This assignment happens without requiring the spare system controller node to
reboot.
-
-
We can add support for configuring more than two system controllers. One node
will get an active assignment, another node will get a standby assignment, and
the rest of the system controller nodes will have no assignment for their
OpenSAF 2N SUs (they will be "spares").
For locking/unlocking the middleware 2N SU, refer the patch floated for
http://devel.opensaf.org/ticket/2023
+
+Ticket #1170 will be supported subsequent to this ticket.
~~~~
---
** [tickets:#79] Dynamically changing the opensaf node type
(controller/payload)**
**Status:** accepted
**Milestone:** 5.0.FC
**Created:** Mon May 13, 2013 04:33 AM UTC by Nagendra Kumar
**Last Updated:** Fri Nov 20, 2015 05:38 PM UTC
**Owner:** Anders Widell
**Attachments:**
-
[spare_sc.diff](https://sourceforge.net/p/opensaf/tickets/79/attachment/spare_sc.diff)
(116.6 kB; text/x-patch)
-
[spare_sc_uml_test.diff](https://sourceforge.net/p/opensaf/tickets/79/attachment/spare_sc_uml_test.diff)
(2.6 kB; text/x-patch)
Migrated from http://devel.opensaf.org/ticket/2101
This ticket and subsequent ticket
https://sourceforge.net/p/opensaf/tickets/1170/ is to support
the following two use scenarios
a) flexible deployment based on special hardware needs for more than one system
controllers
b) multiple nodes failing simultaneously
The following is the scope of this ticket:
* It will be possible to configure nodes termed as spares (to the system
controller group of nodes).
* If one of the system controller nodes dies, another "spare" system contoller
node (if there is any available) will be get an assignment (active / standby).
This assignment happens without requiring the spare system controller node to
reboot.
We can add support for configuring more than two system controllers. One node
will get an active assignment, another node will get a standby assignment, and
the rest of the system controller nodes will have no assignment for their
OpenSAF 2N SUs (they will be "spares").
For locking/unlocking the middleware 2N SU, refer the patch floated for
http://devel.opensaf.org/ticket/2023
Ticket #1170 will be supported subsequent to this ticket.
---
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
