Packer

Packer, Photon, Python, Flask, WSGI, vROps. Holy smokes folks.. I’m not sure I could make a more click-bait-y post if I tried!

I recently took a position at a new company and had the opportunity to stand up a greenfield environment. Part of this environment was obviously configuring monitoring. Since we’re pretty heavily tied to VMware here, we’re using vROps for our monitoring. For escalation of alerts, we’re using OpsGenie, and for normal collaboration we’re using Teams. Unfortunately, vROps versions older than 8.4 do not support sending alerts to OpsGenie or Teams out of the box. Fortunately, we can still get this working with a bit of work.

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
  • Builders
  • Attaching ISOs and Floppy Images
    • ISOs
    • Floppy Images
  • Communicators
  • Provisioners
• Linux Templates
• Windows Templates
  • Autounattend.xml
    • windowsPE
    • offlineServicing
    • generalize
    • specialize
    • oobeSystem
• Examples
  • Windows
    • In Action
  • Linux
    • In Action
• References

Traditional Enterprise Template Management

1. Templates Across Multiple Sites – create a master template and replicate to ensure the same state exists
   1. Introduces operational complexity
   2. Extends the total amount of time it takes to patch all templates
2. OS and Application updates need to be performed for every application on every template
   1. Repetition sucks!
   2. Introduces risk due to C2K errors
3. Template creation ends up being a work of art.
   1. Individuals sometimes spend years fine-tuning all of the customization in a windows template.
   2. On-boarding time is significantly increased
   3. Projects delivered by third parties will take extra time to complete projects, as reverse engineering will need to occur in templates
4. Documentation? Do you have it for your Windows and Linux Template?