Déplacement slide interactive

slides.md

@@ -170,7 +170,7 @@ Paxos domine le marché depuis ~25 ans (Leslie Lamport, 1989)
 2. Réplication des logs (fonctionnement normal)
    - Le leader accepte les commandes des clients et les ajoute à son journal
    - Le leader réplique son journal aux autres serveurs (écrase les incohérences)
-3. Sécurité
+3. Sûreté
    - Maintenir la cohérence des journaux
    - Seuls les serveurs dont les journaux sont à jour peuvent devenir des leaders
 
@@ -265,7 +265,7 @@ RPC = Remote Procedure Call
 
 </header>
 
-- Sécurité: autoriser au maximum un gagnant par mandat
+- Sûreté: autoriser au maximum un gagnant par mandat
   - Chaque serveur ne donne qu'un seul vote par mandat (persistant sur disque)
   - Majorité requise pour gagner l'élection
   ![](figs/election-correctness.png)
@@ -281,42 +281,6 @@ RPC = Remote Procedure Call
 
 <header>
 
-# Démo interactive
-
-</header>
-
-<iframe
-  src="https://raft.github.io/raftscope/index.html"
-  frameborder="0"
-  scrolling="no"
-  height=100%
-  width=100%
-></iframe>
-
-<!--
-
-Normal Operation:
-
-- Client sends command to leader
-- Leader appends command to its log
-- Leader sends AppendEntries RPCs to all followers
-- Once new entry committed:
-  - Leader executes command in its state machine, returns result to client
-  - Leader notifies followers of committed entries in subsequent AppendEntries RPCs
-  - Followers execute committed commands in their state machines
-- Crashed/slow followers?
-  -Leader retries AppendEntries RPCs until they succeed
-- Optimal performance in common case:
-  - One successful RPC to any majority of servers
-
--->
-
-<!-- Laurent & Clément -->
-
----
-
-<header>
-
 # Structure des journaux
 
 </header>
@@ -408,6 +372,42 @@ AppendEntries RPCs include <index, term> of entry preceding new one(s)
 
 <header>
 
+# Démo interactive
+
+</header>
+
+<iframe
+  src="https://raft.github.io/raftscope/index.html"
+  frameborder="0"
+  scrolling="no"
+  height=100%
+  width=100%
+></iframe>
+
+<!--
+
+Normal Operation:
+
+- Client sends command to leader
+- Leader appends command to its log
+- Leader sends AppendEntries RPCs to all followers
+- Once new entry committed:
+  - Leader executes command in its state machine, returns result to client
+  - Leader notifies followers of committed entries in subsequent AppendEntries RPCs
+  - Followers execute committed commands in their state machines
+- Crashed/slow followers?
+  -Leader retries AppendEntries RPCs until they succeed
+- Optimal performance in common case:
+  - One successful RPC to any majority of servers
+
+-->
+
+<!-- Laurent & Clément -->
+
+---
+
+<header>
+
 # Changement de composition du cluster
 
 </header>