Of course we want to be able to provision hosts unattended there as well, but with the current solution that would require a new server for DHCP/PXE services and the setup and overhead that comes with that.Īfter some consideration we ended up with trying the custom image route. These days we are in the process of creating a new platform that has little connections in to the existing one. You could come around this problem with deduplication on the storage as well as it's actually only one file that's different between the images. Of course we can delete the images after provisioning and then not worry about the first point, but a nice benefit by only creating specific boot and ks.cfg files is that you will have the opportunity to redeploy quite easily if needed. I had considered using Custom ISOs previously, but stopped because of two reasons: With creating a iso image for a specific host we would need to have 350+ MB images for x hosts lying around and I can imagine that we could get in some unessecary discussions with some support engineers over using "custom" images. There is some complexity involved in setting up and maintaining the server(s) needed, and in our network setup in doesn't scale very well. There's however a couple of drawbacks to this approach in our environment. This has worked well and we have been using this to provision lots of physical ESXi hosts.
Previously I've written some posts on how to provision ESXi hosts through PXE booting and scripts.
0 kommentar(er)
