This config is on the VMware host. In my case, that’s a MacOS Mojave MacBook Pro running VMware Fusion. Any recent VMware hypervisors (Fusion, Workstation ESXi) are capable of providing this. VirtualBox and Parallels can to. This scope of this guide is staying with VMware Fusion on MacOS.
* for simplicity, this VMNET config uses an entire class c range (private/non-routable of course), and then allocates the bottom half for static IP and lets the DHCP process serve the top half.
- INTRODUCTION: Overview of the starting point for this install, and reasons why to do it.
- STEP 1 – clone an existing “minimal” VM (or build one).
- STEP 2 – prepare to install/config PXE/RepoSync/RepoTrack (load software packages).
- STEP 3 – add/config a 2nd virtual hard disk for the repo files.
- STEP 4 – CONFIG RepoSync/RepoTrack to support multiple OS Distros, Releases, and Architectures.
- STEP 5 – configure an EXCLUDE LINE for YUM CONFIG files
- STEP 6 – build REPOSYNC commands for SCRIPT “rs-c7x64-update.sh”
- STEP 7 – CREATE /etc/yum.repos.d/c7x64.repo for the CentOS 7 64-bit REPOSYNC CLIENTS
- STEP 8 – CREATE /etc/yum.repos.d/c7x32.repo for the CentOS 7 32-bit REPOSYNC CLIENTS
- STEP 9 – ENABLE and CONFIGURE PXE (uses vmware dhcp; does not require CentOS NTP/DHCP/DNS/vsftd/xinetd)
- STEP 10 – Create a PXE BOOT MENU
- STEP 11 – create the kickstart files referenced by the PXE Boot menu:
- STEP 12 – Put the required PXE client boot files in place.
- STEP 13 – Provide PXE boot server info to DHCP clients, via VMware Fusion vnet config (not a CentOS DHCP server).
- STEP 14 – Test PXE Boot and Kickstart installation.
- SIDEBAR 1 – Alternate ways to provide PXE BOOT IMAGES to clients (a brief summary)
- SIDEBAR 2 – Optional NFS SHARE: convenient for exploring repo contents from a gui desktop VM.
- SIDEBAR 3 – PXE client note re memory: the boot image uses a ramdisk.