[DRBD-cvs] r1551 - trunk

svn at svn.drbd.org svn at svn.drbd.org
Wed Sep 22 15:19:38 CEST 2004


Author: phil
Date: 2004-09-22 15:19:33 +0200 (Wed, 22 Sep 2004)
New Revision: 1551

Modified:
   trunk/ROADMAP
Log:
Incooperated LGE's comments.


Modified: trunk/ROADMAP
===================================================================
--- trunk/ROADMAP	2004-09-21 15:37:10 UTC (rev 1550)
+++ trunk/ROADMAP	2004-09-22 13:19:33 UTC (rev 1551)
@@ -13,7 +13,7 @@
 3 Authenticate the peer upon connect by using a shared secret. 
   Config file syntax:  net { auth-secret "secret-word" }
   Using a challenge-response authentication within the new
-  handshake. 
+  handshake.
 
 4 Changes of state and cstate synchronized by mutex and only done by
   the worker thread.
@@ -26,17 +26,22 @@
                   node should drop its net-conf (preferable the
                   node that would become sync-target)
                   DEFAULT.
-   asf-older      Auto sync from is the oder primary (curr.behaviour i.t.s.)
-   asf-younger    Auto sync from is the younger primary
-   asf-furthest   Auto sync from is the node that did more modifications
-   asf-NODENAME   Auto sync from is the named node 
+   discard-younger-primary
+                  Auto sync from is the oder primary (curr.behaviour i.t.s.)
+   discard-older-primary
+                  Auto sync from is the younger primary
+   discard-less-modified
+                  Auto sync from is the node that did more modifications
+   discard-NODENAME 
+                  Auto sync to the named node 
   
-  
   pri-sees-sec-with-higher-gc =
-   disconnect     (current behaviour)
-   asf-primary    Auto sync from is the current primary
-   panic          The current primary panics. The node with the
-                  higher gc should take over.
+   disconnect         (current behaviour)
+   discard-secondary  Auto sync from is the current primary
+   suspend_io          The current primary freezes IO.
+
+  pri-sees-sec-with-higher-gc-cmd "command";
+                      In the same event this command will be executed.
   
   
   Notes:
@@ -49,6 +54,8 @@
      [ The whole algorithm would also work if both would reset their 
        GCs to <0,0,0...> after the decision, but since we also
        use the GC to tag the bitmap it is better the current way ]
+  4) The execution of the pri-sees-sec-with-higher-gc-cmd should
+     be implemented like the kernel can execute modprobe...
 
 6 It is possible that a secondary node crashes a primary by 
   returning invalid block_ids in ACK packets. [This might be 
@@ -72,14 +79,14 @@
   introduce the "Dead" peer state (o_state)
 
   New commands:
-    drbdadm peer-dead r0
-    drbdadm [ considered-dead | die | fence | outdate ] r0 
-      ( What do you like best ? Suggestions ? )
+    drbdadm resume r0
+    drbdadm outdate r0 
+    drbdadm suspend r0
 
-  remove option value: on-disconnect=freeze_io
+  remove option value: on-disconnect=suspend_io
 
   introduce: 
-    peer-state-unknown=freeze_io
+    peer-state-unknown=suspend_io
     peer-state-unknown=continue_io
 
   New meta-data flag: "Outdated"
@@ -100,15 +107,19 @@
                     In the STONITH case: turn off N2.
                     In the "smart" case: 
                     N1 asks N2 to fence itself from the storage via cnet.
-                    HB calls "drbdadm fence r0" on N2.
+                    HB calls "drbdadm outdate r0" on N2.
                     N2 replies to N1 that fencing is done via cnet.
-                    N1 calls "drbdadm peer-dead r0".
+                    N1 calls "drbdadm resume r0".
    P/D - -  S/?     N1 thaws IO
 
-  N2 got the the "Outdated" flag set in its meta-data, by the "fence" 
-  command. I am not sure if it should be called "fence", other ideas:
-  "considered-dead","die","fence","outdate". What do you think ?
+  N2 got the the "Outdated" flag set in its meta-data, by the outdate 
+  command. The suspend command is here to make the interface 
+  complete, and to reach the freezed state without th need to
+  disconnect the peer. It might turn out to be usefull for other
+  tasks as well.
 
+  Eventually introduce on-disconnent-cmd "command";
+
 8 New command drbdmeta
 
   We move the read_gc.pl/write_gc.pl to the user directory. 
@@ -130,6 +141,10 @@
   drbdadm md-get/set-{la-size|consistent|etc...} resources....
   drbdadm md-create r0
 
+  md-create would ask nasty questions about whether you are really 
+  sure and so on, and do some plausibility checks first.
+  md-set would be undocumented and for wizards only.
+
 9 Support shared disk semantics  ( for GFS, OCFS etc... )
 
     All the thoughts in this area, imply that the cluster deals



More information about the drbd-cvs mailing list