X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=system%2FAA-bonding.md;h=d1e28cf3735fc085661797b7c241f6dd89198233;hb=d9a55ada6d0eeb7732863fc50a7564294d57ac70;hp=e2e52e91038398ae8b94014a02d610ee35e7dba7;hpb=44274b7f5146e38f1f1b6965eb3db98a595c663e;p=tests.git diff --git a/system/AA-bonding.md b/system/AA-bonding.md index e2e52e9..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 @@ -66,29 +66,43 @@ as a matter of fact when doing `run -g $bonding` one can invoke most of the usua # upgrading nodes -targets like `nodefcdistro-f20` can be used to change a node's fcdistro +targets like `nodedistro-f22` 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 +## testing upgrade (one node) - would be - e.g. from f20 to f21 +testing a node upgrade; we start from a f21 myplc and upgrade the node to f22 +### Init - f20 - bond ../$(t)*f21 + f21 + bond22 rung - run 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 +### Upgrade the node + + run nodedistro-f22 nodestate-upgrade + run reset-node wait-node + +### Reinstall - back to square 1 - f21 - bond ../$(t)*f20 - rung - rung node qemu-start wait-node - rung nodefcdistro-f21 nodestate-upgrade - rung qemu-kill-mine qemu-start wait-node + 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