Gitiles
Code Review Sign In
gerrit.mcp.mirantis.com / mk / packer-templates / cae5b3e1273e716932a07c3d1ed90aa9eaab2964
commitcae5b3e1273e716932a07c3d1ed90aa9eaab2964[log] [tgz]
authorDenis Egorenko <degorenko@mirantis.com>Fri Dec 13 15:03:44 2019 +0400
committerDenis Egorenko <degorenko@mirantis.com>Fri Dec 13 15:03:44 2019 +0400
treef96cc023315bf3899bcf02b65f166aa90377ded3
parente5f37ab8d08b4f120ae3e4ce2f5795834baf8cfe [diff]
Add ability to build offline image with MU tag inside

MU tag inside will be just simple symlink to latest available MU
release and needed to be able to deploy by tag from image.

Change-Id: I73e5876a633c18dc55767bc20c5d0686fd426caf
Related-Prod: PROD-34366
1 file changed
tree: f96cc023315bf3899bcf02b65f166aa90377ded3
  1. centos-7/
  2. common/
  3. day01-image/
  4. debian-8/
  5. http/
  6. mirror-image/
  7. trymcp-day01-image/
  8. ubuntu-14.04/
  9. ubuntu-16.04/
  10. ubuntu-18.04/
  11. .gitignore
  12. packer-image-buid.groovy
  13. README.md
README.md

Packer templates

Packer templates are used to:

  • automagically create OS images with upgraded packages
  • provision user defined changes to created image
  • remove user defined elements from image
  • build single version of OS image for multiple hypervisors

Features

Operating Systems

  • Ubuntu 14.04 (trusty)
  • Ubuntu 16.04 (xenial)
  • Debian 8 (jessie)

Providers

  • qemu
  • docker
  • virtualbox
  • vagrant/libvirt
  • vagrant/virtualbox
  • digitalocean

Usage

Install Packer

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}

Image build

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

Development

Directory http/ contains OS installer config files (preseed/kickstart/..)

Directory scripts/ contains set of scripts for provision after image build.

Notes

  • some builders cannot work at the same time (by design)