Managing Linux OS Resources and Deployment Media
You can import Linux OS Resources needed to create network boot media and to capture and deploy Linux images
Importing Linux OS Resources for RHEL, SLES and CentOS deployments
Linux OS Resources are required to capture Linux reference machines, to create network boot media for Linux deployments and to install Linux OS.
To create it from the Bundle and Media Manager dashboard, click the corresponding button in the Deployment Resources tab. Browse to the fully qualified path of the Linux ISO file from which the OS Resource will be imported, and click OK. When the action completes, the Linux OS Resource is displayed in the list. To delete a Linux OS Resource entry, select it and click Delete.
A Linux OS Resource for the same OS level is also created when its setup image is imported from the Image Library dashboard.
For a Linux resource, the specific grub2 bootloader for UEFI targets is also included in it. You can check if the grub2 bootloader for UEFI targets is included in the OS Resource by checking the Resource Info column, where grub.efi or grubx64.efi is reported if it is included. If it is not included, the Linux deployment on UEFI target uses the external grub2 bootloader if present, as described in Creating Bare Metal Profiles for Linux Images; otherwise, the embedded elilo.efi bootloader is used.
To use the grub2 bootloader for Linux deployment on UEFI target, the DHCP server must provide the option "next-server" with the value of the bare metal server IP address. On some DHCP servers, this options is provided together with the option 66.
Importing Linux OS Resources for RHEL in-place upgrade
RHEL in-place upgrade OS resource is needed to run the in-place upgrade from RHEL 6 to RHEL 7, from RHEL 7 to RHEL 8 and from RHEL 8 to RHEL 9. The resource will be applied to the initial OS and most files needed to create it can be found in the installation media of the initial OS. The files that cannot be found on the installation media must be downloaded from the RHEL web site, after authenticating with a user authorized for rpm download.
You can create RHEL in-place upgrade OS resource for RHEL 6.10 to upgrade to RHEL 7.9, for RHEL 7.9 to upgrade to RHEL 8.8 and 8.10, for RHEL 8.8 to upgrade to RHEL 9.2, for RHEL 8.9 to upgrade to RHEL 9.3, for RHEL 8.10 to upgrade to RHEL 9.4 or later.
To create it from the Bundle and Media Manager dashboard, click the corresponding button in the Deployment Resources tab. Browse to the dedicated folder where the files needed for the initial OS of your in-place upgrade task are and click OK. When the action completes, the Linux in-place OS Resource is displayed in the list. To delete a Linux OS Resource entry, select it and click Delete.
- FOR RHEL 6.10:
- fakeroot-1.12.2-22.2.el6.x86_64.rpm
- fakeroot-libs-1.12.2-22.2.el6.x86_64.rpm
- gdb-7.2-92.el6.x86_64.rpm
- openscap-1.2.13-2.el6.x86_64.rpm
- openscap-engine-sce-1.2.13-2.el6.x86_64.rpm
- openscap-scanner-1.2.13-2.el6.x86_64.rpm
- openscap-utils-1.2.13-2.el6.x86_64.rpm
- preupgrade-assistant-2.6.2-1.el6.noarch.rpm
- preupgrade-assistant-el6toel7-0.8.0-3.el6.noarch.rpm
- preupgrade-assistant-el6toel7-data-0.20200704-1.el6.noarch.rpm
- pykickstart-1.74.22-1.el6.noarch.rpm
- redhat-rpm-config-9.0.3-51.el6.noarch.rpm
- redhat-upgrade-tool-0.8.0-9.el6.noarch.rpm
- rpm-build-4.8.0-59.el6.x86_64.rpm
- rpmdevtools-7.5-2.el6.noarch.rpm
- yum-utils-1.1.30-42.el6_10.noarch.rpm
- For RHEL 7.9:
- audit-2.8.5-4.el7.x86_64.rpm
- audit-libs-2.8.5-4.el7.x86_64.rpm
- audit-libs-python-2.8.5-4.el7.x86_64.rpm
- checkpolicy-2.5-8.el7.x86_64.rpm
- dnf-4.0.9.2-2.el7_9.noarch.rpm
- dnf-data-4.0.9.2-2.el7_9.noarch.rpm
- json-glib-1.4.2-2.el7.x86_64.rpm
- leapp-deps-0.17.0-1.el7_9.noarch.rpm
- leapp-upgrade-el7toel8-0.20.0-2.el7_9.noarch.rpm
- leapp-upgrade-el7toel8-deps-0.20.0-2.el7_9.noarch.rpm
- libcgroup-0.41-21.el7.x86_64.rpm
- libcomps-0.1.8-14.el7.x86_64.rpm
- libdnf-0.22.5-2.el7_9.x86_64.rpm
- libmodulemd-1.6.3-1.el7.x86_64.rpm
- librepo-1.8.1-8.el7_9.x86_64.rpm
- libreport-filesystem-2.1.11-53.el7.x86_64.rpm
- librhsm-0.0.3-3.el7_9.x86_64.rpm
- libsemanage-python-2.5-14.el7.x86_64.rpm
- libsolv-0.6.34-4.el7.x86_64.rpm
- libyaml-0.1.4-11.el7_0.x86_64.rpm
- pciutils-3.5.1-3.el7.x86_64.rpm
- policycoreutils-2.5-34.el7.x86_64.rpm
- policycoreutils-python-2.5-34.el7.x86_64.rpm
- python-chardet-2.2.1-3.el7.noarch.rpm
- python-enum34-1.0.4-1.el7.noarch.rpm
- python-IPy-0.75-6.el7.noarch.rpm
- python-requests-2.6.0-10.el7.noarch.rpm
- python-urllib3-1.10.2-7.el7.noarch.rpm
- python2-dnf-4.0.9.2-2.el7_9.noarch.rpm
- python2-hawkey-0.22.5-2.el7_9.x86_64.rpm
- python2-leapp-0.17.0-1.el7_9.noarch.rpm
- python2-libcomps-0.1.8-14.el7.x86_64.rpm
- python2-libdnf-0.22.5-2.el7_9.x86_64.rpm
- setools-libs-3.3.8-4.el7.x86_64.rpm
- For RHEL 8.8:
- leapp-0.15.1-1.el8.noarch.rpm
- leapp-deps-0.15.1-1.el8.noarch.rpm
- leapp-upgrade-el8toel9-0.18.0-1.el8_8.2.noarch.rpm
- leapp-upgrade-el8toel9-deps-0.18.0-1.el8.noarch.rpm
- python3-leapp-0.15.1-1.el8.noarch.rpm
- python3-pip-9.0.3-22.el8.noarch.rpm
- python3-setuptools-39.2.0-7.el8.noarch.rpm
- python36-3.6.8-38.module+el8.5.0+12207+5c5719bc.x86_64.rpm
- systemd-container-239-74.el8_8.x86_64.rpm
- For RHEL 8.9:
- leapp-0.16.0-2.el8.noarch.rpm
- leapp-deps-0.16.0-2.el8.noarch.rpm
- leapp-upgrade-el8toel9-0.19.0-1.el8.noarch.rpm
- leapp-upgrade-el8toel9-deps-0.19.0-1.el8.noarch.rpm
- python3-leapp-0.16.0-2.el8.noarch.rpm
- python3-pip-9.0.3-23.el8.noarch.rpm
- python3-setuptools-39.2.0-7.el8.noarch.rpm
- python36-3.6.8-38.module+el8.5.0+12207+5c5719bc.x86_64.rpm
- systemd-container-239-78.el8.x86_64.rpm
- For RHEL 8.10:
- leapp-0.17.0-1.el8.noarch.rpm
- leapp-deps-0.17.0-1.el8.noarch.rpm
- leapp-upgrade-el8toel9-0.20.0-2.el8.noarch.rpm
- leapp-upgrade-el8toel9-deps-0.20.0-2.el8.noarch.rpm
- python3-leapp-0.17.0-1.el8.noarch.rpm
- python3-pip-9.0.3-24.el8.noarch.rpm
- python3-setuptools-39.2.0-7.el8.noarch.rpm
- python36-3.6.8-39.module+el8.10.0+20784+edafcd43.x86_64.rpm
- systemd-container-239-82.el8.x86_64.rpm
Creating and importing OS Resources for Ubuntu deployments
Linux Ubuntu, deployments require that you create and import a corresponding OS resource. To create and import OS Resources for Ubuntu deployments, see Create and Import OS Resources for Linux Ubuntu Deployments.
Creating network boot media for Linux RHEL, SLES, and CentOS targets
- From the Bundle and Media Manager dashboard, import a Linux OS Resource by clicking the corresponding button. Select the fully qualified path to the ISO file. The supported ISO files are RedHat Enterprise Linux (RHEL) Release 6, 7, 8, 9, CentOS Linux Release 7, 8 or SUSE Linux Version 12 or 15. If you have already imported Linux OS Resources for these platforms skip this step.
- From the Linux Media tab, click Create Deployment Media. The Media creation wizard is displayed. Select the OS Deployment Server where the media will be created, and click Next.
- Select or specify the following:
- The Linux OS Resource to be included in the media. You must have previously imported the resource.
- Specify the fully qualified path on the OS Deployment Server where the ISO file for the media will be created
- In the Server Settings section, specify the IP address and the administrative user password of the OS Deployment Server to which the target connects at boot time. This server can be the same or a different OS Deployment server from the one you are creating the media on. Alternatively, you can specify the connection parameters at boot time, by checking the corresponding option.
- Select the type of network configuration settings that are assigned to the client at boot time. By default, a dynamic IP address is assigned (DHCP). Alternatively, you can specify a static IP address, network mask, and gateway address. If you specify static network settings, you can overwrite them at boot time by checking the corresponding option.
- You can optionally specify to have the user start the boot sequence on the target. In this case, a prompt is displayed on the target and the boot sequence begins only when the user responds to the prompt.
- If the network boot media must connect to a bare metal server of version 7.1.1.20.311.12 or lower, you must select the specific option.
- When you have completed your selections, click OK. The information that you provided is validated before the media creation task begins.
- If you want to deploy a Linux setup image in multicast from network boot media, the Linux OS resource that you include in the media must be of the same major version of the image that you are deploying. For example, you can use a RedHat Enterprise Linux (RHEL) Versions 7 Update 8 resource to deploy all Red Hat Enterprise Linux (RHEL) Version 7 setup images using multicast communication.
- Only CD/DVD media are supported.
- Deployment of the media on UEFI targets is not supported.
- Media creation and deployment on Ubuntu Linux is not supported.