github.com/rahart/packer@v0.12.2-0.20161229105310-282bb6ad370f/website/source/docs/templates/veewee-to-packer.html.md (about)

     1  ---
     2  description: |
     3      If you are or were a user of Veewee, then there is an official tool called
     4      veewee-to-packer that will convert your Veewee definition into an equivalent
     5      Packer template. Even if you're not a Veewee user, Veewee has a large library of
     6      templates that can be readily used with Packer by simply converting them.
     7  layout: docs
     8  page_title: Convert Veewee Definitions to Packer Templates
     9  ...
    10  
    11  # Veewee-to-Packer
    12  
    13  If you are or were a user of [Veewee](https://github.com/jedi4ever/veewee), then
    14  there is an official tool called
    15  [veewee-to-packer](https://github.com/mitchellh/veewee-to-packer) that will
    16  convert your Veewee definition into an equivalent Packer template. Even if
    17  you're not a Veewee user, Veewee has a [large
    18  library](https://github.com/jedi4ever/veewee/tree/master/templates) of templates
    19  that can be readily used with Packer by simply converting them.
    20  
    21  ## Installation and Usage
    22  
    23  Since Veewee itself is a Ruby project, so too is the veewee-to-packer
    24  application so that it can read the Veewee configurations. Install it using
    25  RubyGems:
    26  
    27  ``` {.text}
    28  $ gem install veewee-to-packer
    29  ...
    30  ```
    31  
    32  Once installed, usage is easy! Just point `veewee-to-packer` at the
    33  `definition.rb` file of any template. The converter will output any warnings or
    34  messages about the conversion. The example below converts a CentOS template:
    35  
    36  ``` {.text}
    37  $ veewee-to-packer templates/CentOS-6.4/definition.rb
    38  Success! Your Veewee definition was converted to a Packer
    39  template! The template can be found in the `template.json` file
    40  in the output directory: output
    41  
    42  Please be sure to run `packer validate` against the new template
    43  to verify settings are correct. Be sure to `cd` into the directory
    44  first, since the template has relative paths that expect you to
    45  use it from the same working directory.
    46  ```
    47  
    48  ***Voila!*** By default, `veewee-to-packer` will output a template that contains
    49  a builder for both VirtualBox and VMware. You can use the `-only` flag on
    50  `packer build` to only build one of them. Otherwise you can use the `--builder`
    51  flag on `veewee-to-packer` to only output specific builder configurations.
    52  
    53  ## Limitations
    54  
    55  None, really. The tool will tell you if it can't convert a part of a template,
    56  and whether that is a critical error or just a warning. Most of Veewee's
    57  functions translate perfectly over to Packer. There are still a couple missing
    58  features in Packer, but they're minimal.
    59  
    60  ## Bugs
    61  
    62  If you find any bugs, please report them to the [veewee-to-packer issue
    63  tracker](https://github.com/mitchellh/veewee-to-packer). I haven't been able to
    64  exhaustively test every Veewee template, so there are certainly some edge cases
    65  out there.