5 * one build `2015.04.13--f14` under test
6 * another build `2015.04.13--f18` that you would like to use to create f18 nodes inside `2015.04.13--f14`
8 general idea is to use this command
10 root@testmaster ~/2015.04.13--f14 # run -g 2015.04.13--f18 ...
12 or in an equivalent manner
14 export bonding=bond212015.04.13--f18
19 * the build to test (f14) must be running
20 * the build to bond with does not need to run but needs to be have run under `../2015.04.13--f18` so that its arg-* files reflect its flavour
24 * rung can be used as a symlink to `TestMain.py`
25 * in this case it is like running `run -G`
27 * plus, `comp-testmaster` offers the convenience function
40 will define the f18 node flavour to the f14 build
42 # creating bonding node
46 will create an additional node in tested myplc.
48 **NOTE** for efficiency the IP and hostname of that node are stored in `arg-bonding-$bonding`
52 as a matter of fact when doing `run -g $bonding` one can invoke most of the usual targets, including for starting the node
54 rung start-node wait-node
58 alias rung='run -g $bonding'
59 bonding=2015.04.13--f21
62 cat arg-bonding-$bonding
69 targets like `nodedistro-f22` can be used to change a node's fcdistro
72 ## testing upgrade (one node)
74 testing a node upgrade; we start from a f21 myplc and upgrade the node to f22
83 ### Upgrade the node (make sure nodeplain is off)
85 run nodedistro-f22 nodestate-upgrade
86 run reset-node wait-node
88 ### Reinstall - back to square 1
90 run nodedistro-f21 nodestate-reinstall
91 run reset-node wait-node
93 ### Run bootmanager interactively during upgrade
94 To deploy experimental bootmanager code:
96 * Insert breakpoints in the bootmanager code
97 * turn on `BREAKPOINT_MODE = True` in `utils.py`
102 run nodedistro-f22 nodestate-safeboot
103 run reset-node ssh-node-debug
107 ./BootManager.py upgrade