- BUILING VM TEMPLATES ON VMWARE ESXI 5 PATCH
- BUILING VM TEMPLATES ON VMWARE ESXI 5 WINDOWS
The process for me to build a template, say Windows Server 2019, used to be as follows:
But it can start you off in the right place and save you time in the long run.
BUILING VM TEMPLATES ON VMWARE ESXI 5 PATCH
Yes, you'll still have to patch / maintain the VMs down the road, Packer doesn't solve that problem. On top of that, you can bring standardisation to your templates and the VMs they are used to build. Its job is to eliminate the first choice and automate the second. Photo by Mattia Ascenzo / UnsplashĮnter Packer. Neither option sounds very appealing when written like that.
Build new templates more often so that they're current. Accept that updates VMs made from my aging templates will take progressively longer and that they won't be very secure when I clone them. Of course this stance means that I'm left with two choices: Aside from feeling dirty, what happens if I accidentally break something or forget a step? Ok so it's only me using my homelab so my templates are always going to be in a known state (known to me that is), but I've still never liked turning them on, patching them, trying to do a tidy-up and then converting them back in to a template again. I'm very much of the opinion that once something is a template, you shouldn't ever power it back on again unless you're cloning it to be a new VM. Lately however, I've been deploying more linux servers (CentOS) in my homelab and I was aware that my templates very quickly got out of date in terms of patches etc. Other things always seemed more important so it got pushed to the bottom of my task list. HashiCorp Packer is one of those things I've been meaning to get to grips with for some time.
0 kommentar(er)
