This is a first pass. I'll review this code myself and do more
testing, but I wanted to get folks a look at it to make sure I
was going in the right direction.
BUG=none
TEST=ran using both cell and hostname scenarios
Review URL: http://codereview.chromium.org/3007002
Clean up command-line argument used to disable re-download of image bits down to the upgrade server. This is now handed via a much more concise "--no_copy_archive" argument. and user output output "fast restart" messages
Output information on how to run the "image_to_live.sh" client unconditionally (even if a client isn't being launched by this instance).
BUG=none
TEST=Reran commands, observed output
Review URL: http://codereview.chromium.org/2919009
cros_copy_upgrade_server had a bug where it would always start servers
on port 8081 regrdless of whether that port was free. This was a bug
in the "get next free port" code.
BUG=chromium-os:4776
TEST=Reran multiple instances at once, run netstat -nlt
Review URL: http://codereview.chromium.org/2975006
Currently the output of build_image signs the kernel partition with the recovery keys on the final image. This script allows us to replace the kernel vblock and resign the kernel with the right set of keys (for example, using the normal boot path kernel keys, or the keys for factory install, etc.)
BUG=4623
TEST=Tested by running the script on one of the latest builbot images (801) and resigning with test kernel keys. The resulting image was dd-ed off to an SSD and was succesfully able to boot on one of our dev systems with our custom firmware with both dev mode and recovery mode turned off.
To test (can do outside chroot):
1) Download the latest image from the buildbot (I used build 801)
2) Run script with the following arguments and paths adjusted below
resign_image
--from /path/to/chromiumos_image.bin \
--datakey /path/to/vboot_reference/tests/devkeys/kernel_data_key.vbprivk \
--keyblock /path/to/vboot_reference/tests/devkeys/kernel.keyblock \
--vsubkey /path/to/vboot_reference/tests/devkeys/kernel_subkey.vbpubk \
--vbutil_dir /path/to/vbutil/binaries
--to image.out
This re-signs the image with the normal test keys (instead of recovery as done by build_image)
3) Copy the image to an SSD drive
dd if=image.out of=/dev/ssd [replace with the correct device]
4) Boot with the latest custom firmware in normal mode (recovery and dev mode turned off).
5) Profit!
Review URL: http://codereview.chromium.org/2938004
