Gitiles
Code Review Sign In
gerrit.mcp.mirantis.com / mk / packer-templates / a5888ad74de1c1f5aeeccb8bf36b81167322b119
commita5888ad74de1c1f5aeeccb8bf36b81167322b119[log] [tgz]
authorVladimir Khlyunev <vkhlyunev@mirantis.com>Tue Apr 28 13:00:57 2020 +0400
committerVladimir Khlyunev <vkhlyunev@mirantis.com>Tue Apr 28 15:51:48 2020 +0400
tree1ffa8248ca5a7b5e837df4994e328731815ee7b3
parent3187965b1df40160b53ba3e914085794e48aac78 [diff]
Remove zerodisk from mcp offline image build

We don't need to extend image file and truncate it later
(it consumes extra 40 GB of jenkins slave for nothing)

Closes-bug: PROD-35231
Change-Id: Ia8b9290a936ce36be3033a98742cc6ffb34b8c0a
2 files changed
tree: 1ffa8248ca5a7b5e837df4994e328731815ee7b3
  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)