This is the seventh in a series of posts on using a Packer pipeline to generate Vagrant .box files.
In the last post we covered using ovftool to convert Packer generated virtual machines into Vagrant .box files. I promised to show you a better way of exporting and creating the Vagrant .box files, so in this post we will be combining the following items in one script:
Kicking off the Packer build of a specific template Exporting the Packer generated virtual machine Creating the necessary metadata.
This is the sixth in a series of posts on using a Packer pipeline to generate Vagrant .box files.
In the last post we covered copying our existing CentOS 6.7 template and adding the Puppet agent in order to generate a new Packer template. In this post we will be covering how to use ovftool to convert Packer generated virtual machines into Vagrant .box files. This post will be going over the manual steps on purpose, since I feel it will make more sense when we start to cover automating the steps that you can already performed by hand.
This is the fifth in a series of posts on using a Packer pipeline to generate Vagrant .box files.
In the last post we covered creating a Packer template for installing CentOS 6.7 with vmtools. In this post we will be basing a new Packer template on the one we created last post and add installing the Puppet Enterprise 3.8.2 agent.
This is an older version of the Puppet Enterprise agent, but it will let us create a Vagrant .
This is the fourth in a series of posts on using a Packer pipeline to generate Vagrant .box files.
In the last two posts we covered installing a ESXi virtual machine for use with Packer and Setting up Packer, ovftool and Apache web server on a CentOS virtual machine. In this post we will be putting all this prep work to use in order to install a CentOS 6.7 image using Packer.
This is the third in a series of posts on using a Packer pipeline to generate Vagrant .box files.
In the last post we setup a ESXi virtual machine that would be the target for creating Packer images. In order to follow along with this post you will need two things:
A fresh CentOS virtual machine on which we will install Packer - I’m using CentOS 6.6 minimal install named “packer-centos” with 2 vCPU, 4GB of memory and a 100GB virtual hard drive.
This is the second in a series of posts on using a Packer pipeline to generate Vagrant .box files.
In order to begin using Packer to create images, we will first need to lay the “virtual” ground work. Packer can create virtual machine images on a wide variety of virtualization or cloud platforms, but since I work for VMware I have been using the ESXi hypervisor.
This post will be covering installing ESXi as a virtual machine on a vSphere cluster.
Recently at work, the vCloud Air Zombie team has been using Packer to generate Vagrant templates for use in development and testing. I have previously covered how to use Packer to create create a .box template for use with Vagrant, but I thought it might be useful to others to demonstrate how we are using Packer to create images.
This will be the first of several blog posts in which I intend to cover:
In the previous post I demonstrated using packer to create a ESXi .box template on OS X with fusion and the vagrant vmware provider. Both of these pieces of software have a cost associated with their usage, so in this post I will demonstrate how to use CentOS 6.5 and ESXi for the same results.
In this post we will again talk about two helpful gosddc projects:
gosddc/packer-post-processor-vagrant-vmware-ovf. This repo contains a packer post processor that leverages VMware OVF Tool to create a vmware_ovf Vagrant box that is compatible with vagrant-vcloud, vagrant-vcenter and vagrant-vcloudair vagrant providers.