The Packer templates are organized under the following directory structure inside the root
<os-distribution>is the operating system distribution, for example
<variant>is the version or variant, e.g.
10.13for macOS, or
<architecture>is the architecture, e.g.
os_dist refers to
arch refers to
architecture. Each directory (
templates/<os_dist>/<variant>/<arch>) may or may not have a
common directory in it. This directory can contain the following files:
- A specialized template that is specific to any sub-directories under that section.
vars.jsonfile containing the required variables needed for other, parent
commontemplates to build successfully.
- Other files, such as scripts, patches, or preseed files.
The intent for the
common directory is to contain things that may be shared by some of the sub-directories.
<os_dist>/<variant>/<arch> directory can contain (1) and (2), and technically (3), but we do not recommend (3) (as it’s highly likely that scripts, patches, or pressed files can apply to multiple architectures of a specific OS variant so they might as well be in their own
common directory). There is one caveat. If a
<os_dist>/<variant>/<arch> directory contains a particular template (e.g. like vmware.base.json) AND a
vars.json file, then all variables for the template should be declared both in the template itself, and in any
vars.json files found in sub-directories — the
vars.json file in the current directory should not have variables for that specific template.
Here are the semantics behind each of the possible locations for a
templates/commoncontains relevant templates and files for our Linux-based distributions. This was done because all of our os distributions, save for Macos, Windows, Solaris, are Linux-based.
<os-dist>/commonrepresents templates, variables and files that are shared by variants of a single OS distribution. For example for our Centos platforms, we have a
centos/commonthat captures a common boot command.
<os-dist>/<variant>/commonrepresents templates, variables, and files specific to architectures of a variant of an OS distribution. For example for our Centos platforms, we have our pressed files in
centos/<variant>/common, as well as some overriding variables for Centos 5.11 and Centos 6.6.
SSH user accounts
- Windows: the Administrator password is
- Solaris: the root password is
- macOS: see the README under templates/macos
- For everything else, the root password is
Some very basic linting has been added to ensure files parse properly through packer. To run these tests do:
Please open any issues within the CPR ( Community Package Repository ) project on the Puppet Labs issue tracker.
This repository is currently undergoing a massive cleanup effort. We have decided to keep only the
vmware.vsphere.nocm templates. If it turns out that this cleanup and refactoring has removed a template that you rely on (e.g. a virtual box or vagrant one), please checkout a version of the puppetlabs-packer repository at SHA
9babc323c862290d2eeb51d52fe133e564eba533 and accept our apologies in advance. We can correct these issues if we’re notified of them in a ticket.