github.com/phobos182/packer@v0.2.3-0.20130819023704-c84d2aeffc68/website/source/intro/why.html.markdown (about) 1 --- 2 layout: "intro" 3 page_title: "Why Use Packer?" 4 prev_url: "/intro/index.html" 5 next_url: "/intro/use-cases.html" 6 next_title: "Packer Use Cases" 7 --- 8 9 # Why Use Packer? 10 11 Pre-baked machine images have a lot of advantages, but most have been unable 12 to benefit from them because images have been too tedious to create and manage. 13 There were either no existing tools to automate the creation of machine images or 14 they had too high of a learning curve. The result is that, prior to Packer, 15 creating machine images threatened the agility of operations teams, and therefore 16 aren't used, despite the massive benefits. 17 18 Packer changes all of this. Packer is easy to use and automates the creation 19 of any type of machine image. It embraces modern configuration management by 20 encouraging you to use a framework such as Chef or Puppet to install and 21 configure the software within your Packer-made images. 22 23 In other words: Packer brings pre-baked images into the modern age, unlocking 24 untapped potential and opening new opportunities. 25 26 ## Advantages of Using Packer 27 28 ***Super fast infrastructure deployment***. Packer images allow you to launch 29 completely provisioned and configured machines in seconds, rather than 30 several minutes or hours. This benefits not only production, but development as well, 31 since development virtual machines can also be launched in seconds, without waiting 32 for a typically much longer provisioning time. 33 34 ***Multi-provider portability***. Because Packer creates identical images for 35 multiple platforms, you can run production in AWS, staging/QA in a private 36 cloud like OpenStack, and development in desktop virtualization solutions 37 such as VMware or VirtualBox. Each environment is running an identical 38 machine image, giving ultimate portability. 39 40 ***Improved stability***. Packer installs and configures all the software for 41 a machine at the time the image is built. If there are bugs in these scripts, 42 they'll be caught early, rather than several minutes after a machine is launched. 43 44 ***Greater testability***. After a machine image is built, that machine image 45 can be quickly launched and smoke tested to verify that things appear to be 46 working. If they are, you can be confident that any other machines launched 47 from that image will function properly. 48 49 Packer makes it extremely easy to take advantage of all these benefits. 50 51 What are you waiting for? Let's get started!