Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 11. Adding the Kickstart file to a UEFI HTTP or PXE installation source
After your Kickstart file is ready, you can make it available for the installation on the destination system.
11.1. Sharing the installation files on an NFS server Copier lienLien copié sur presse-papiers!
You can store Kickstart files on an NFS server to enable automated installations across multiple systems. It eliminates the need for physical media and provides centralized management of installation configurations for efficient system deployment over network file sharing.
Prerequisites
- You have administrator-level access to a server with Red Hat Enterprise Linux 10 on the local network.
- The system to be installed can connect to the server.
Ensure that you use different paths in inst.ks and inst.repo. When using NFS to host the Kickstart, you cannot use the same nfs share to host the installation source.
Procedure
Install the
nfs-utilspackage by running the following command as root:dnf install nfs-utils
# dnf install nfs-utilsCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Copy the Kickstart file to a directory on the NFS server.
Open the
/etc/exportsfile by using a text editor and add a line with the following syntax:/exported_directory/ clients
/exported_directory/ clientsCopy to Clipboard Copied! Toggle word wrap Toggle overflow Replace /exported_directory/ with the full path to the directory holding the Kickstart file. Instead of clients, use the host name or IP address of the computer that is to be installed from this NFS server, the subnetwork from which all computers are to have access the ISO image, or the asterisk sign (
*) if you want to allow any computer with network access to the NFS server to use the ISO image. See the exports(5) man page for detailed information about the format of this field. A basic configuration that makes the/nfs/rhel10-kickstart/directory available as read-only to all clients is:/nfs/rhel10-kickstart/ *
/nfs/rhel10-kickstart/ *Copy to Clipboard Copied! Toggle word wrap Toggle overflow Enable the NFS service in firewalld.
firewall-cmd --permanent --add-service nfs firewall-cmd --permanent --add-service=mountd firewall-cmd --permanent --add-service=rpc-bind firewall-cmd --reload
# firewall-cmd --permanent --add-service nfs # firewall-cmd --permanent --add-service=mountd # firewall-cmd --permanent --add-service=rpc-bind # firewall-cmd --reloadCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
Save the
/etc/exportsfile and exit the text editor. Start the nfs service:
systemctl enable --now nfs-server.service
# systemctl enable --now nfs-server.serviceCopy to Clipboard Copied! Toggle word wrap Toggle overflow If the service was running before you changed the
/etc/exportsfile, enter the following command, in order for the running NFS server to reload its configuration:systemctl reload nfs-server.service
# systemctl reload nfs-server.serviceCopy to Clipboard Copied! Toggle word wrap Toggle overflow The Kickstart file is now accessible over NFS and ready to be used for installation.
NoteWhen specifying the Kickstart source, use
nfs:as the protocol, the server’s host name or IP address, the colon sign (:), and the path inside the directory holding the file. For example, if the server’s host name ismyserver.example.comand you have saved the file in/nfs/rhel10-kickstart/my-ks.cfg, specifyinst.ks=nfs:myserver.example.com:/nfs/rhel10-kickstart/my-ks.cfgas the installation source boot option.
11.2. Sharing the installation files on an HTTP or HTTPS server Copier lienLien copié sur presse-papiers!
You can store Kickstart files on an HTTP or HTTPS server to enable automated installations across multiple systems. It eliminates the need for physical media and provides centralized management of installation configurations for efficient system deployment.
Prerequisites
- You have administrator-level access to a server with Red Hat Enterprise Linux 10 on the local network.
- The system to be installed can connect to the server.
Procedure
To store the Kickstart file on an HTTP, install the
httpdpackage:dnf install httpd
# dnf install httpdCopy to Clipboard Copied! Toggle word wrap Toggle overflow Optional: To store the Kickstart file on an HTTPS, install
httpdandmod_sslpackages:dnf install httpd mod_ssl
# dnf install httpd mod_sslCopy to Clipboard Copied! Toggle word wrap Toggle overflow ImportantIf you use an HTTPS server with a self-signed certificate, you must boot the installation program with the
inst.noverifyssloption.-
Copy the Kickstart file to the HTTP(S) server into a subdirectory of the
/var/www/html/directory. Enable the http service in firewalld.
firewall-cmd --permanent --add-service=http firewall-cmd --reload
# firewall-cmd --permanent --add-service=http # firewall-cmd --reloadCopy to Clipboard Copied! Toggle word wrap Toggle overflow Optional: Enable the
httpsservice in firewalld:firewall-cmd --permanent --add-service=https firewall-cmd --reload
# firewall-cmd --permanent --add-service=https # firewall-cmd --reloadCopy to Clipboard Copied! Toggle word wrap Toggle overflow Start the
httpdservice:systemctl enable --now httpd.service
# systemctl enable --now httpd.serviceCopy to Clipboard Copied! Toggle word wrap Toggle overflow The Kickstart file is now accessible and ready to be used for installation.
When specifying the location of the Kickstart file, use
http://orhttps://as the protocol, the server’s host name or IP address, and the path of the Kickstart file, relative to the HTTP server root. For example, if you are using HTTP, the server’s host name ismyserver.example.com, and you have copied the Kickstart file as/var/www/html/rhel10-install/my-ks.cfg, specifyhttp://myserver.example.com/rhel10-install/my-ks.cfgas the file location.
11.3. Sharing the installation files on an FTP server Copier lienLien copié sur presse-papiers!
You can store Kickstart files on an FTP server to enable automated installations across multiple systems. It eliminates the need for physical media and provides centralized management of installation configurations for efficient system deployment by using the FTP protocol.
Prerequisites
- You have administrator-level access to a server with Red Hat Enterprise Linux 10 on the local network.
- The system to be installed can connect to the server.
Procedure
Install the
vsftpdpackage by running the following command as root:dnf install vsftpd
# dnf install vsftpdCopy to Clipboard Copied! Toggle word wrap Toggle overflow Open and edit the
/etc/vsftpd/vsftpd.confconfiguration file in a text editor.-
Change the line
anonymous_enable=NOtoanonymous_enable=YES -
Change the line
write_enable=YEStowrite_enable=NO. Add lines
pasv_min_port=min_portandpasv_max_port=max_port. Replacemin_portandmax_portwith the port number range used by the FTP server in passive mode, for example,10021and10031.This step can be necessary in network environments featuring various firewall/NAT setups.
- Optional: Add custom changes to your configuration. For available options, see the vsftpd.conf(5) man page. This procedure assumes that default options are used.
-
Change the line
Configure the firewall to allow the FTP port and port range from the previous step:
firewall-cmd --add-port min_port-max_port/tcp --permanent
# firewall-cmd --add-port min_port-max_port/tcp --permanentCopy to Clipboard Copied! Toggle word wrap Toggle overflow Replace min_port-max_port with the port numbers you entered into the
/etc/vsftpd/vsftpd.confconfiguration file.Configure the firewall to allow FTP service.
firewall-cmd --add-service ftp --permanent
# firewall-cmd --add-service ftp --permanentCopy to Clipboard Copied! Toggle word wrap Toggle overflow Reload the firewall to apply the new rules.
firewall-cmd --reload
# firewall-cmd --reloadCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
Copy the Kickstart file to the FTP server into the
/var/ftp/directory or its subdirectory. Ensure that the correct SELinux context and access mode is set on the file:
restorecon -r /var/ftp/your-kickstart-file.ks chmod 444 /var/ftp/your-kickstart-file.ks
# restorecon -r /var/ftp/your-kickstart-file.ks # chmod 444 /var/ftp/your-kickstart-file.ksCopy to Clipboard Copied! Toggle word wrap Toggle overflow Start the
vsftpdservice:systemctl enable --now vsftpd.service
# systemctl enable --now vsftpd.serviceCopy to Clipboard Copied! Toggle word wrap Toggle overflow If the service was running before you changed the
/etc/vsftpd/vsftpd.conffile, restart the service to load the edited file:systemctl restart vsftpd.service
# systemctl restart vsftpd.serviceCopy to Clipboard Copied! Toggle word wrap Toggle overflow The Kickstart file is now accessible and ready to be used for installations by systems on the same network.
NoteWhen configuring the installation source, use
ftp://as the protocol, the server’s host name or IP address, and the path of the Kickstart file, relative to the FTP server root. For example, if the server’s host name ismyserver.example.comand you have copied the file to/var/ftp/my-ks.cfg, specifyftp://myserver.example.com/my-ks.cfgas the installation source.