X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=system%2FAA-bonding.md;h=d712d8a7ad29592577e4efdc08871c2060855d14;hb=93b57f5a05dc3eafa1a5c2c4ac54e852f508d10d;hp=a37c9d3996c0f131f0633dcc597097b43dfeaf2f;hpb=6f9cfa7ae380b6582f2ef85b39d01399093baf11;p=tests.git

diff --git a/system/AA-bonding.md b/system/AA-bonding.md
index a37c9d3..d712d8a 100644
--- a/system/AA-bonding.md
+++ b/system/AA-bonding.md
@@ -63,3 +63,32 @@ as a matter of fact when doing `run -g $bonding` one can invoke most of the usua
 	<<visual check>>
 	rung bonding-node
 
+
+# upgrading nodes
+
+targets like `nodefcdistro-f20` can be used to change a node's fcdistro
+
+----
+
+usual sequence for testing a node upgrade; we start from a f20 myplc and upgrade the node to f21
+
+ would be - e.g. from f20 to f21
+
+
+    f20
+    bond ../$(t)*f21
+    rung
+    run nodeplain-off nodefcdistro-f21 nodestate-upgrade
+    run qemu-kill-mine qemu-start wait-node
+
+-----
+Or, the other way around, using a f21 myplc, and a f20 bonding node, that we upgrade
+
+    f21
+    bond ../$(t)*f20
+    rung
+    rung node qemu-start wait-node
+    rung nodefcdistro-f21 nodestate-upgrade
+    rung qemu-kill-mine qemu-start wait-node
+    
+