Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
P
packer
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kristopher Ruzic
packer
Commits
9b1f7930
Commit
9b1f7930
authored
Jun 20, 2013
by
Mitchell Hashimoto
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
website: update terminology
parent
9bc39e9e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
6 deletions
+12
-6
website/source/docs/basics/terminology.html.markdown
website/source/docs/basics/terminology.html.markdown
+12
-6
No files found.
website/source/docs/basics/terminology.html.markdown
View file @
9b1f7930
...
@@ -10,20 +10,20 @@ Luckily, there are relatively few. This page documents all the terminology
...
@@ -10,20 +10,20 @@ Luckily, there are relatively few. This page documents all the terminology
required to understand and use Packer. The terminology is in alphabetical
required to understand and use Packer. The terminology is in alphabetical
order for easy referencing.
order for easy referencing.
<a
class=
"term"
id=
"
#term-build
"
></a>
<a
class=
"term"
id=
"
term-artifact
"
></a>
**Artifacts**
are the results of a single
[
build
](
#term-build
)
, and are
**Artifacts**
are the results of a single
[
build
](
#term-build
)
, and are
usually a set of IDs or files to represent a machine image. Every
[
builder
](
#term-builder
)
usually a set of IDs or files to represent a machine image. Every
[
builder
](
#term-builder
)
produces a single artifact. As an example, in the case of the Amazon EC2 builder,
produces a single artifact. As an example, in the case of the Amazon EC2 builder,
the artifact is a set of AMI IDs (one per region). For the VMware builder,
the artifact is a set of AMI IDs (one per region). For the VMware builder,
the artifact is a directory of files comprising the created virtual machine.
the artifact is a directory of files comprising the created virtual machine.
<a
class=
"term"
id=
"
#
term-build"
></a>
<a
class=
"term"
id=
"term-build"
></a>
**Builds**
are a single task that eventually produces an image for a single
**Builds**
are a single task that eventually produces an image for a single
platform. Multiple builds run in parallel. Example usage in a sentence: "The Packer build
platform. Multiple builds run in parallel. Example usage in a sentence: "The Packer build
produced an AMI to run our web application." Or: "Packer is running the builds
produced an AMI to run our web application." Or: "Packer is running the builds
now for VMware, AWS, and VirtualBox."
now for VMware, AWS, and VirtualBox."
<a
class=
"term"
id=
"
#
term-builder"
></a>
<a
class=
"term"
id=
"term-builder"
></a>
**Builders**
are components of Packer that are able to create a machine
**Builders**
are components of Packer that are able to create a machine
image for a single platform. Builders read in some configuration and use
image for a single platform. Builders read in some configuration and use
that to run and generate a machine image. A builder is invoked as part of a
[
build
](
#term-build
)
that to run and generate a machine image. A builder is invoked as part of a
[
build
](
#term-build
)
...
@@ -31,21 +31,27 @@ in order to create the actual resulting images. Example builders include
...
@@ -31,21 +31,27 @@ in order to create the actual resulting images. Example builders include
VirtualBox, VMware, and Amazon EC2. Builders can be created and added to
VirtualBox, VMware, and Amazon EC2. Builders can be created and added to
Packer in the form of plugins.
Packer in the form of plugins.
<a
class=
"term"
id=
"
#
term-command"
></a>
<a
class=
"term"
id=
"term-command"
></a>
**Commands**
are sub-commands for the
`packer`
program that perform some
**Commands**
are sub-commands for the
`packer`
program that perform some
job. An example somecommand is "build", which is invoked as
`packer build`
.
job. An example somecommand is "build", which is invoked as
`packer build`
.
Packer ships with a set of commands out of the box in order to define
Packer ships with a set of commands out of the box in order to define
its
[
command-line interface
](
#
)
. Commands can also be created and added to
its
[
command-line interface
](
#
)
. Commands can also be created and added to
Packer in the form of plugins.
Packer in the form of plugins.
<a
class=
"term"
id=
"#term-provisioner"
></a>
<a
class=
"term"
id=
"term-post-processor"
></a>
**Post-processors**
are components of Packer that take the result of
a
[
builder
](
#term-builder
)
or another post-processor and process that to
create a new
[
artifact
](
#term-artifact
)
. Examples of post-processors are
compress to compress artifacts, upload to upload artifacts, etc.
<a
class=
"term"
id=
"term-provisioner"
></a>
**Provisioners**
are components of Packer that install and configure
**Provisioners**
are components of Packer that install and configure
software within a running machine prior to that machine being turned
software within a running machine prior to that machine being turned
into a static image. They perform the major work of making the image contain
into a static image. They perform the major work of making the image contain
useful software. Example provisioners include shell scripts, Chef, Puppet,
useful software. Example provisioners include shell scripts, Chef, Puppet,
etc.
etc.
<a
class=
"term"
id=
"
#
term-template"
></a>
<a
class=
"term"
id=
"term-template"
></a>
**Templates**
are JSON files which define one or more
[
builds
](
#term-build
)
**Templates**
are JSON files which define one or more
[
builds
](
#term-build
)
by configuring the various components of Packer. Packer is able to read a
by configuring the various components of Packer. Packer is able to read a
template and use that information to create multiple machine images in
template and use that information to create multiple machine images in
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment