This article explains how to use Cloud-Init with vRealize Automation and vSphere without requiring a CD drive in every VM.
Not content to build vSphere templates periodically, this introduction shows how VMware Code Stream and Packer can be combined to trigger builds from Git updates.
The final (short) post in this series. Now that vSphere templates can be built repeatably, it's time to think about the next steps to take things further.
Having created a Windows template, in Part 6 of this series it's now time to make one for Linux using my go-to distro, CentOS 8.
Armed with some vSphere variables, it's now time to create a Windows template. In post 5 of this series that process is described.
In part 4 of this series it's finally time to introduce some JSON. The variables that I re-use in every template for telling Packer where to provision machines.
In part 3 of this series I cover some of the configuration and terminology required to get going with builds and that will be used in the rest of the series.
Now Packer is introduced, it's time to prepare for using it to create some vSphere templates. This is part 2 of a series.