user avatar
Merge pull request #3349 from keyan/master
Rickard von Essen authored
provisioner/puppet-masterless: Add ignore exit codes option
9d1a6b08
Name Last commit Last update
.github Delete the PR template before submitting.
Godeps Add support for NTLM the WinRM communicator.
builder Merge branch 'googlecompute-disk-type' of https://github.com/meatballhat/packer into f-google-disk-type
command Make the build name error message show the original regexp
common Removed ftp/ftps schemas since they don't work.
communicator Add support for NTLM the WinRM communicator.
contrib/zsh-completion Fix zsh-completion
fix Added fixer for ssh_key_path
helper Add support for NTLM the WinRM communicator.
packer file provisioner improvements
plugin go fmt
post-processor Add debug logging for the credentials used for S3 in amazon-import
provisioner Add ignore_exit_codes param for puppet-masterless provisioner
scripts Update dist script to sign signature file
template Display better error messages on json.SyntaxError
test Add sftp file transfer support
vendor Udpated winrmcp dep
website Add docs for ignore_exit_codes param
.gitignore Ignore logs from packer tests
.travis.yml If go version is 1.4 use godeps to restore dependencies
CHANGELOG.md Added google disk_type to changelog
CONTRIBUTING.md Update go 1.5 references to 1.6
LICENSE LICENSE: MPL2
Makefile If go version is 1.4 use godeps to restore dependencies
README.md Moved the bulk of go setup to CONTRIBUTING.md so it doesn't need to be maintained in two places
Vagrantfile
appveyor.yml
checkpoint.go
commands.go
config.go
log.go
main.go
main_test.go
panic.go
signal.go
stdin.go
version.go

Packer

Build Status Windows Build Status

Packer is a tool for building identical machine images for multiple platforms from a single source configuration.

Packer is lightweight, runs on every major operating system, and is highly performant, creating machine images for multiple platforms in parallel. Packer comes out of the box with support for the following platforms:

  • Amazon EC2 (AMI). Both EBS-backed and instance-store AMIs
  • DigitalOcean
  • Docker
  • Google Compute Engine
  • OpenStack
  • Parallels
  • QEMU. Both KVM and Xen images.
  • VirtualBox
  • VMware

Support for other platforms can be added via plugins.

The images that Packer creates can easily be turned into Vagrant boxes.

Quick Start

Note: There is a great introduction and getting started guide for those with a bit more patience. Otherwise, the quick start below will get you up and running quickly, at the sacrifice of not explaining some key points.

First, download a pre-built Packer binary for your operating system or compile Packer yourself.

After Packer is installed, create your first template, which tells Packer what platforms to build images for and how you want to build them. In our case, we'll create a simple AMI that has Redis pre-installed. Save this file as quick-start.json. Export your AWS credentials as the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.

{
  "variables": {
    "access_key": "{{env `AWS_ACCESS_KEY_ID`}}",
    "secret_key": "{{env `AWS_SECRET_ACCESS_KEY`}}"
  },
  "builders": [{
    "type": "amazon-ebs",
    "access_key": "{{user `access_key`}}",
    "secret_key": "{{user `access_key`}}",
    "region": "us-east-1",
    "source_ami": "ami-de0d9eb7",
    "instance_type": "t1.micro",
    "ssh_username": "ubuntu",
    "ami_name": "packer-example {{timestamp}}"
  }]
}

Next, tell Packer to build the image:

$ packer build quick-start.json
...

Packer will build an AMI according to the "quick-start" template. The AMI will be available in your AWS account. To delete the AMI, you must manually delete it using the AWS console. Packer builds your images, it does not manage their lifecycle. Where they go, how they're run, etc. is up to you.

Documentation

Comprehensive documentation is viewable on the Packer website:

http://www.packer.io/docs

Developing Packer

See CONTRIBUTING.md for best practices and instructions on setting up your development environment to work on Packer.