github.com/phobos182/packer@v0.2.3-0.20130819023704-c84d2aeffc68/website/source/docs/templates/veewee-to-packer.html.markdown (about)

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