VMware Template Management using Hashicorp Packer
VMware Templates: they make life amazing, don’t they? Creating a your first vSphere template is easy, but there are limitations when using them in enterprise environments. In this article, I will talk about the downsides of traditional enterprise template management, how Packer can help, and give examples (and code!) for creating Windows and Linux templates in VMware vCenter using Packer.
Table of Contents
Toggle
- Traditional Enterprise Template Management
- Enterprise Template Management With Packer
- Source Code
- Packer Intro
- Packer Template File & User Variables
- Linux Templates
- Windows Templates
- Examples
- References
Traditional Enterprise Template Management
- Templates Across Multiple Sites – create a master template and replicate to ensure the same state exists
- Introduces operational complexity
- Extends the total amount of time it takes to patch all templates
- OS and Application updates need to be performed for every application on every template
- Repetition sucks!
- Introduces risk due to C2K errors
- Template creation ends up being a work of art.
- Individuals sometimes spend years fine-tuning all of the customization in a windows template.
- On-boarding time is significantly increased
- Projects delivered by third parties will take extra time to complete projects, as reverse engineering will need to occur in templates
- Documentation? Do you have it for your Windows and Linux Template?
Continue reading “VMware Template Management using Hashicorp Packer”
