Go to file
stack72 7776bf596b builder/triton: Add a data source for source_machine_image
fixes: #5476

Based on this new template addition:

```
{
    "variables": {
        "image_version": "",
        "triton_account": "",
        "triton_key_id": "",
        "triton_key_material": ""
    },
    "builders": [{
        "type": "triton",
        "triton_account": "{{user `triton_account`}}",
        "triton_key_id": "{{user `triton_key_id`}}",
        "triton_key_material": "{{user `triton_key_material`}}",
        "source_machine_package": "g4-highcpu-128M",
        "source_machine_image_filter": {
          "name": "ubuntu-16.04",
          "most_recent": "true"
        },
        "ssh_username": "root",
        "image_version": "{{user `image_version`}}",
        "image_name": "teamcity-server"
    }],
    "provisioners": [
        {
            "type": "shell",
            "start_retry_timeout": "10m",
            "inline": [
                "sudo apt-get update -y",
                "sudo apt-get install -y nginx"
            ]
        }
    ]
}

```

I got the following output from packer:

```
packer-testing % make image
packer build \
		-var "triton_account=stack72_joyent" \
		-var "triton_key_id=40:9d:d3:f9:0b:86:62:48:f4:2e:a5:8e:43:00:2a:9b" \
		-var "triton_key_material=""" \
		-var "image_version=1.0.0" \
		new-template.json
triton output will be in this color.

==> triton: Selecting an image based on search criteria
==> triton: Based, on given search criteria, Machine ID is: "7b5981c4-1889-11e7-b4c5-3f3bdfc9b88b"
==> triton: Waiting for source machine to become available...
==> triton: Waiting for SSH to become available...
==> triton: Connected to SSH!
==> triton: Provisioning with shell script: /var/folders/_p/2_zj9lqn4n11fx20qy787p7c0000gn/T/packer-shell797317310
    triton: Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
    triton: Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
```

I can verify from the triton cli tools that the id `7b5981c4` (from the packer output) is indeed the correct ID

```
terraform [master●] % triton images name=~ubuntu-16.04
SHORTID   NAME          VERSION   FLAGS  OS     TYPE        PUBDATE
49b22aec  ubuntu-16.04  20160427  P      linux  lx-dataset  2016-04-27
675834a0  ubuntu-16.04  20160505  P      linux  lx-dataset  2016-05-05
4edaa46a  ubuntu-16.04  20160516  P      linux  lx-dataset  2016-05-16
05140a7e  ubuntu-16.04  20160601  P      linux  lx-dataset  2016-06-01
e331b22a  ubuntu-16.04  20161004  P      linux  lx-dataset  2016-10-04
8879c758  ubuntu-16.04  20161213  P      linux  lx-dataset  2016-12-13
7b5981c4  ubuntu-16.04  20170403  P      linux  lx-dataset  2017-04-03 <------- THIS IS THE LATEST UBUNTU IMAGE
```
2017-11-02 16:10:16 +02:00
.github Updated ISSUE_TEMPLATE.md 2017-06-28 07:39:26 +02:00
builder builder/triton: Add a data source for source_machine_image 2017-11-02 16:10:16 +02:00
command Merge pull request #5444 from vijayinvites/packer-vhdx 2017-10-13 11:53:27 -07:00
common Merge pull request #5491 from BenPhegan/hyperv-disk_additional_size 2017-10-31 08:42:07 -07:00
communicator Merge pull request #5273 from StuporHero/master 2017-08-30 13:52:07 -07:00
contrib Update _packer 2017-08-03 23:11:52 +02:00
examples azure: sysprep improvements for Windows examples 2017-09-29 12:39:52 -07:00
fix Fix typo in fixer file name 2017-09-26 17:50:47 +01:00
helper add echo test to winrm connection. 2017-09-01 15:26:41 -07:00
packer only output telemetry logs when enabled. 2017-10-05 14:31:24 -07:00
plugin/example delete unneeded plugin file 2017-09-28 10:52:54 -07:00
post-processor 🎨 Fix typo in "copyed" -> "copied" usages. 2017-10-26 07:42:49 -05:00
provisioner rephrase log message. 2017-10-26 10:41:49 -07:00
scripts skip doc PRs in changelog helper 2017-10-10 17:11:28 -07:00
template Unit test to verify that parsing fails on a certain kind of malformed JSON 2017-05-19 16:42:42 -04:00
test [lxc] add bats tests 2017-09-05 15:18:07 -07:00
vendor Bump Joyent/triton-go to modern version of the SDK 2017-10-31 18:08:53 +02:00
version next version is 1.1.2 2017-10-13 18:48:57 -07:00
website builder/triton: Add a data source for source_machine_image 2017-11-02 16:10:16 +02:00
.gitattributes On windows a lot of git clients will convert LF to CRLF. This would be a problem where file contents are compared exactly 2016-12-12 22:44:50 +00:00
.gitignore Merge pull request #5206 from sandersaares/hyperv-second-temp-dir 2017-10-09 10:08:00 -07:00
.travis.yml add go 1.9 to travis 2017-08-24 16:21:55 -07:00
CHANGELOG.md update changelog 2017-10-31 08:44:26 -07:00
CODEOWNERS codeowners for post-processors 2017-10-30 12:51:22 -07:00
CONTRIBUTING.md go <= 1.6 are no longer supported 2017-07-24 13:27:31 -07:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile Merge pull request #5082 from nak3/makefile-copy-binary 2017-10-13 14:40:15 -07:00
README.md use correct oracle builder name 2017-10-23 12:10:31 -07:00
Vagrantfile Update go 1.5 references to 1.6 2016-02-17 16:29:38 -08:00
appveyor.yml fix appveyor 2017-06-06 11:52:21 -07:00
azure-merge.sh Added merge script to automatically pull in and fix the upstream repo 2016-03-14 20:08:12 -07:00
checkpoint.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
commands.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
config.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
log.go Fix debug logging 2016-10-07 21:10:20 +02:00
main.go only output telemetry logs when enabled. 2017-10-05 14:31:24 -07:00
main_test.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
panic.go Add telemetry reporting through checkpoint 2017-06-15 13:21:11 -07:00
stdin.go ctrl-c closes stdin for plugins so that they are unblocked 2013-07-25 23:27:13 -07:00

README.md

Packer

Build Status Windows Build Status GoDoc GoReportCard

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
  • Azure
  • CloudStack
  • DigitalOcean
  • Docker
  • Google Compute Engine
  • Hyper-V
  • 1&1
  • OpenStack
  • Oracle Cloud Infrastructure
  • Parallels
  • ProfitBricks
  • QEMU. Both KVM and Xen images.
  • Triton (Joyent Public Cloud)
  • VMware
  • VirtualBox

Support for other platforms can be added via plugins.

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

Quick Start

Download and install packages and dependencies

go get github.com/hashicorp/packer

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 `secret_key`}}",
    "region": "us-east-1",
    "source_ami": "ami-af22d9b9",
    "instance_type": "t2.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:

https://www.packer.io/docs

Developing Packer

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