- **summary**: opensaf shall support temporary unavailbility of both
controllers --> opensaf shall support indefinite unavailbility of both
controllers
- **Comment**:
Replacing the word 'temporary' with 'indefinite' since.
a) Times on the order of 10-15 minutes are an order of magnitude
larger
- Description has changed:
Diff:
--- old
+++ new
@@ -1,6 +1,14 @@
-The opensaf cluster shall survive that both system controllers are temporarily
down (no cluster reboot as today)
+The opensaf cluster shall survive that both system controllers are
indefinitely unavaliable i.e. down (no cl
- Description has changed:
Diff:
--- old
+++ new
@@ -10,6 +10,12 @@
It is important that *everyone* understands this.
There is no magic being done here.
-Use case: opensaf cloud deployment
+Use case: opensaf cloud deployment. In a cloud deployment, the risk for
multiple simultaneous no
- **summary**: opensaf shall support indefinite unavailbility of both
controllers --> opensaf shall support indefinite unavailbility of both
controllers (Hydra V1)
- **Comment**:
The point of this feature is of course not that OpenSAF should be in the
"headless" state indefinitely. The point is
