I'm looking to replicate the functionality of Windows Deployment Services (WDS) for our Linux systems in my company. Currently, we have a Windows server running the WDS service for imaging and deploying Windows machines. I want to do something similar for Linux computers, and I already have one Linux machine set up to create an image. Our servers and computers are on the same LAN with a DHCP server in place. I came across a tutorial that suggested using two LAN cards in the server but that isn't feasible for us, as both the DRBL/Clonezilla server and client will stay on the same production LAN. Does anyone have a comprehensive guide or steps to achieve this?
6 Answers
Try using PXE boot with kickstart and Ansible; this combination is pretty powerful for deployments.
It's better to focus on a recipe-based installation rather than just imaging. This way, your setup remains current when you upgrade your Linux version, plus it avoids the need for additional storage for custom images.
For Linux deployments, consider using a lightweight kickstart file. It allows you to install only necessary packages, set up SSHD, and inject an SSH key for access. Then, you can use Ansible from a management node to SSH into your Linux nodes for configuration management. I recommend AlmaLinux if you're looking for a stable, no-cost RHEL alternative.
You should also look into Terraform for VM setups and Packer for imaging. It simplifies the entire process significantly, no matter what operating system you're using!
Consider iPXE for your needs. It can present a menu that allows you to load the appropriate image whether it's for Windows or Linux via netboot.
You should forget about WDS since it’s Windows-specific. The first thing is to clarify which Linux distribution you’re using since that can change your approach. Honestly, I don't get why you need two network interfaces for what you’re trying to accomplish. Maybe take a moment to reassess what you're actually aiming for?
I think I must've picked that up from an outdated guide. We're using Ubuntu Server for the server side, not related to others in the network. Clients will start with Kubuntu but might switch to regular Ubuntu or Mint.
Totally agree, that's a solid strategy.