sync-rewrap:
ssh root@$(KVMHOST) "(cd $(KVMDIR); \
- echo "Rewrapping bootcd.img"; \
- (cd overlay && find . | cpio --quiet -c -o) | gzip -9 > iso/overlay.img; \
echo "Rewrapping overlay.img"; \
- (cd bootcd && find . | cpio --quiet -c -o) | gzip -9 > iso/bootcd.img; \
+ (cd overlay && find . | cpio --quiet -c -o) | gzip -1 > iso/overlay.img; \
+ echo "Rewrapping bootcd.img"; \
+ (cd bootcd && find . | cpio --quiet -c -o) | gzip -1 > iso/bootcd.img; \
mkisofs -o $(NODE).iso $(MKISOFS_OPTS) iso/; \
)"
* and then run it on the testmaster side like this
- iterate-ping-node <nb_iterations>
+ `iterate-ping-node -o run01 <nb_iterations>`
* This allows to run a given bootcd (the iso computed for one node) several times over, and to gather all logs from qemu
-* This is **only** restarting the kvm/qemu node several times, nothing is done to recompute the .iso itself (see below for that). So the game is to easily simulate how a change to `bootcd` would affect a node ISO without rebuilding the whole damn thing.
+* This is **only** restarting the kvm/qemu node several times, nothing is done to recompute the .iso itself (see below for that). So the game is to easily simulate how a change to `bootcd` would affect a node ISO without rebuilding the whole damn thing
+* When -o is provided, the directory argument is created and all log files are stored in there
## Easily redo a .iso