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

diff --git a/system/AA-bonding.md b/system/AA-bonding.md
index a37c9d3..d1e28cf 100644
--- a/system/AA-bonding.md
+++ b/system/AA-bonding.md
@@ -11,7 +11,7 @@ general idea is to use this command
 	
 or in an equivalent manner
 
-	export bonding= 2015.04.13--f18
+	export bonding=bond212015.04.13--f18
 	run -G
 	
 # requirements
@@ -63,3 +63,46 @@ 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 `nodedistro-f22` can be used to change a node's fcdistro
+
+
+## testing upgrade (one node)
+
+testing a node upgrade; we start from a f21 myplc and upgrade the node to f22
+
+### Init
+
+    f21
+    bond22
+    rung
+
+### Upgrade the node
+    
+    run nodedistro-f22 nodestate-upgrade
+    run reset-node wait-node
+    
+### Reinstall - back to square 1
+
+	run nodedistro-f21 nodestate-reinstall
+	run reset-node wait-node
+    
+### Run bootmanager interactively during upgrade
+To deploy experimental bootmanager code:
+
+* Insert breakpoints in the bootmanager code
+* turn on `BREAKPOINT_MODE = True` in `utils.py`
+* `make sync` 
+
+Then 
+
+    run nodedistro-f22 nodestate-safeboot 
+    run reset-node ssh-node-debug
+    testnodedbg
+    
+    cd /tmp/source
+    ./BootManager.py upgrade
+    
+