![]() ![]() Then mount the iso files to the VM and boot up with the static IP and its network settings automatically, therefore overcomes the environmental restrictions of DHCP. With some further helping tools like govc or simply scp we can transfer the iso files to the VMware or to the KVM host. The ISO file is about 70mb (for OCP 4.2). In fact, I automate the customization of this file with the following template, joining the lines together. We will create a Iso image for each of the nodes. The ignition url points to the matchbox services, where it will return the respective ignition content based on the name selector. ![]() Update the Kernel parameters, appending the node-specific settings, as one line. The isolinux.cfg is a text configuration file for the boot menu. ![]() ![]() The isolinux directory defined how the Linux system should be boot up. On a Linux shell, sudo mount -o loop rhcos-4.2.18-x86_64-installer.iso /mnt/iso mkdir -p iso cp -r /mnt/iso/* isoįor MacBook, hdiutil mount rhcos-4.2.18-x86_64-installer.iso mkdir -p iso cp -r /Volumes/CDROM/* iso/ Custom Isolinux config Given the ocp4 ISO image, let's mount it and extract out the content. As the RHCOS is a Linux system that follows the common Linux boot up, why not we define those kernel booting parameters into the ISO image and let it boot up accordingly? Extract the ISO image Sadly, there is no copy and paste before the OS is up. What a long typing! 300+ characters and need to do the same for the other three master nodes, three worker nodes. When the bootup menu appears, we hit the Tab key and key in the following extra Kernel parameters to define the static IP, the image URL, and the ignition URL, ip=192.168.10.30::192.168.10.1:255.255.255.0.cpak:ens3:none nameserver=192.168.10.39 _dev=vda _url= _url= ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |