network bridge=br0,model=virtio,mac=C0:FF:EE:D0:5E:$ /var/lib/tftpboot/networkboot/CentOS7/Ĭreate the PXE configuration directory: $ sudo mkdir -p /var/lib/tftpboot/pxelinux.cfgĬreate the PXE boot configuration file /var/lib/tftpboot/pxelinux.cfg/default with the following content: default menu.c32Īppend initrd=/networkboot/CentOS7/initrd.img inst.repo= ks=ĭHCP server has to be configured to use 10.11.1.20 as the next-server, e.g.: allow booting įor DHCP server configuration, see here. When I deploy a new VM, I normally do the following: $ VM_ID="08" I use KVM to run my virtual machines (it’s enterprise quality and free). This has grown to 12GB over time and has become a resource hog. When I started with Katello I could get away with 8GB of memory. Its system requirements have also increased by 50%. I’ve found myself using Katello less and less. As a result, my homelab requirements have changed. I will admit that I did not anticipate the scale of it.įast forward some months, I changed jobs to work on a Kubernetes project. I was surprised to see so many OpenShift use cases: from Public Health England using OpenShift to support scientific computing to automotive industry building flexible production infrastructures. Due to global pandemic, the Red Hat Summit 2020 was held online as a Virtual Experience, and I was able to attend it for the first time. I’ve been focused on adopting Docker and getting into the world of containers and infrastructure as a code. My main area of interest has shifted in the last twelve months. Upgrades can be painful at times but you learn to read the CHANGELOG. I’ve been using Katello to manage my homelab for some years now, and it’s done the job well. I am moving away from Foreman managed PXE functionality to a standalone PXE boot server.
0 kommentar(er)
