github.com/aspring/packer@v0.8.1-0.20150629211158-9db281ac0f89/website/source/docs/templates/veewee-to-packer.html.markdown (about)

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