commit | 5a2d6ec24b32b4812bf74ca430b59c6559edce57 | [log] [tgz] |
---|---|---|
author | azvyagintsev <azvyagintsev@mirantis.com> | Thu Jul 19 21:25:25 2018 +0300 |
committer | azvyagintsev <azvyagintsev@mirantis.com> | Thu Jul 19 22:36:23 2018 +0300 |
tree | baf617eacb6c1444914120ca4136d6652bb7972d | |
parent | badeb370df66cff069274963261d7d0c0eb729f0 [diff] |
add pretty sugar day01 image * 80% of debug done at cfg01 host. so, why not to have it easier ? Change-Id: I53a21bdde957794c951b01e7324b07982ebd857b
Packer templates are used to:
PACKER_URL="https://dl.bintray.com/mitchellh/packer/packer_0.8.2_linux_amd64.zip" PACKER_ZIP=$(basename ${PACKER_URL}) PACKER_ZIP_MD5="bc37abe5e183a11bd8c1b2efc385059b" mkdir -p ~/bin/packer cd ~/bin/packer export PATH="${PATH}:~/bin/packer" wget -O ${PACKER_ZIP} ${PACKER_URL} echo "${PACKER_ZIP_MD5} ${PACKER_ZIP}" >> md5sum md5sum -c --status md5sum unzip ${PACKER_ZIP}
Enter build directory by selecting OS type and version. You should see file template.json.
Start building some images:
packer build -only=virtualbox-iso template.json
Directory http/ contains OS installer config files (preseed/kickstart/..)
Directory scripts/ contains set of scripts for provision after image build.