Packer templates for CentOS

Overview

This repository contains templates for CentOS that can create Vagrant boxes using Packer.

Current Boxes

64-bit boxes:

• CentOS 7.0 (64-bit), VMware 426MB/VirtualBox 361MB/Parallels 406MB
• CentOS 7.0 Desktop (64-bit), VMware 1.1GB/VirtualBox 1.0GB/Parallels 1.1GB
• CentOS 7.0 Core with Docker (64-bit), VMware 434MB/VirtualBox 369MB/Parallels 415MB
• CentOS 6.6 (64-bit), VMware 488MB/VirtualBox 405MB/Parallels 493MB
• CentOS 6.6 Desktop (64-bit), VMware 1.2GB/VirtualBox 1.2GB/Parallels 1.2GB
• CentOS 6.6 with Docker (64-bit), VMware 481MB/VirtualBox 411MB/Parallels 494MB
• CentOS 6.5 (64-bit), VMware 455MB/VirtualBox 389MB/Parallels 460MB
• CentOS 6.5 Desktop (64-bit), VMware 1.1GB/VirtualBox 1.0GB/Parallels 1.2GB
• CentOS 6.5 with Docker (64-bit), VMware 460MB/VirtualBox 396MB/Parallels 460MB
• CentOS 6.4 (64-bit), VMware 432MB/VirtualBox 356MB/Parallels 427MB
• CentOS 6.4 Desktop (64-bit), VMware 1.1GB/VirtualBox 1.1GB/Parallels 1.1GB
• CentOS 5.10 (64-bit), VMware 256MB/VirtualBox 180MB/Parallels 236MB
• CentOS 5.10 (64-bit), VMware 254MB/VirtualBox 179MB/Parallels 234MB
• CentOS 5.9 (64-bit), VMware 253MB/VirtualBox 177MB/Parallels 232MB

32-bit boxes:

• CentOS 6.6 (32-bit), VMware 421MB/VirtualBox 355MB/Parallels 402MB
• CentOS 6.5 (32-bit), VMware 407MB/VirtualBox 349MB/Parallels 403MB
• CentOS 6.4 (32-bit), VMware 407MB/VirtualBox 324MB/Parallels 382MB
• CentOS 5.11 (32-bit), VMware 244MB/VirtualBox 168MB/Parallels 224MB
• CentOS 5.10 (32-bit), VMware 244MB/VirtualBox 168MB/Parallels 223MB
• CentOS 5.9 (32-bit), VMware 242MB/VirtualBox 167MB/Parallels 222MB

Building the Vagrant boxes

To build all the boxes, you will need Packer and the desktop virtualization software VirtualBox, VMware Fusion, and Parallels Desktop for Mac installed.

Parallels requires that the Parallels Virtualization SDK for Mac be installed as an additional preqrequisite.

A GNU Make Makefile drives the process via the following targets:

make        # Build all the box types (VirtualBox, VMware & Parallels)
make test   # Run tests against all the boxes
make list   # Print out individual targets
make clean  # Clean up build detritus

Proxy Settings

The templates respect the following network proxy environment variables and forward them on to the virtual machine environment during the box creation process, should you be using a proxy:

• http_proxy
• https_proxy
• ftp_proxy
• rsync_proxy
• no_proxy

Tests

The tests are written in Serverspec and require the vagrant-serverspec plugin to be installed with:

vagrant plugin install vagrant-serverspec

The Makefile has individual targets for each box type with the prefix test-* should you wish to run tests individually for each box. For example:

make test-box/virtualbox/centos66-nocm.box

Similarly there are targets with the prefix ssh-* for registering a newly-built box with vagrant and for logging in using just one command to do exploratory testing. For example, to do exploratory testing on the VirtualBox training environmnet, run the following command:

make ssh-box/virtualbox/centos66-nocm.box

Upon logout make ssh-* will automatically de-register the box as well.

Makefile.local override

You can create a Makefile.local file alongside the Makefile to override some of the default settings. The variables can that can be currently used are:

• CM
• CM_VERSION
• HEADLESS
• <iso_path>
• UPDATE

Makefile.local is most commonly used to override the default configuration management tool, for example with Chef:

# Makefile.local
CM := chef

Changing the value of the CM variable changes the target suffixes for the output of make list accordingly.

Possible values for the CM variable are:

• nocm - No configuration management tool
• chef - Install Chef
• chefdk - Install Chef Development Kit
• puppet - Install Puppet
• salt - Install Salt

You can also specify a variable CM_VERSION, if supported by the configuration management tool, to override the default of latest. The value of CM_VERSION should have the form x.y or x.y.z, such as CM_VERSION := 11.12.4

The variable HEADLESS can be set to run Packer in headless mode. Set HEADLESS := true, the default is false.

The variable UPDATE can be used to perform OS patch management. The default is to not apply OS updates by default. When UPDATE := true, the latest OS updates will be applied.

The variable PACKER can be used to set the path to the packer binary. The default is packer.

Another use for Makefile.local is to override the default locations for the ISO install files.

For CentOS, the ISO path variables are:

• CENTOS59_X86_64
• CENTOS59_I386
• CENTOS510_X86_64
• CENTOS510_I386
• CENTOS511_X86_64
• CENTOS511_I386
• CENTOS64_X86_64
• CENTOS64_I386
• CENTOS65_X86_64
• CENTOS65_I386
• CENTOS66_X86_64
• CENTOS66_I386
• CENTOS70_X86_64

This override is commonly used to speed up Packer builds by pointing at pre-downloaded ISOs instead of using the default download Internet URLs: CENTOS66_X86_64 := file:///Volumes/CentOS/CentOS-6.6-x86_64-bin-DVD1.iso

Contributing

1. Fork and clone the repo.
2. Create a new branch, please don't work in your master branch directly.
3. Add new Serverspec or Bats tests in the test/ subtree for the change you want to make. Run make test on a relevant template to see the tests fail (like make test-virtualbox/centos65).
4. Fix stuff. Use make ssh to interactively test your box (like make ssh-virtualbox/centos65).
5. Run make test on a relevant template (like make test-virtualbox/centos65) to see if the tests pass. Repeat steps 3-5 until done.
6. Update README.md and AUTHORS to reflect any changes.
7. If you have a large change in mind, it is still preferred that you split them into small commits. Good commit messages are important. The git documentatproject has some nice guidelines on writing descriptive commit messages.
8. Push to your fork and submit a pull request.
9. Once submitted, a full make test run will be performed against your change in the build farm. You will be notified if the test suite fails.