Chapter 1. Installation checklist

Before you begin installing Red Hat Update Infrastructure (RHUI), refer to the following checklist to ensure that you have all the necessary components and information required for installation.

Table 1.1. List of components required for installing RHUI

Required InformationInformation UsageResources and Notes

Red Hat Credentials

Red Hat credentials to manage subscription and access to Red Hat repositories.

Red Hat Customer Portal

Network and Firewall access

Network and firewall requirements for the Red Hat Update Appliance (RHUA) and Content Delivery Server (CDS) nodes.

It is possible for a CDS to have a client-facing host name that differs from the host name used for intra-Red Hat Update Infrastructure communication. If you are using client-facing host names, note each CDS’s client-facing FQDN and the corresponding IP address.

Proxy settings

Proxy for access to the Red Hat content delivery network.

Proxy settings for RHUI are set automatically during the installation. They are set on the CDS nodes in the /etc/yum.conf files, where you configure the repositories.

Content Repository Size

Storage space for the RPM packages required by Red Hat Update Infrastructure.

See Preparing your Environment for Installation for specific storage requirements, or use the du command from the command line interface to determine its size.

Also, all repositories are placed in the /var/lib/rhui/remote_share directory which the system creates by default during the installation process. However, if you need to create a new mount point for it, you can manually create this directory.

Client Profiles

RHUI content available to the client

A client profile determines the RHUI content that is available to the client and the CDS from which the client downloads that content.


Use a separate storage volume for the installation if you expect to store a large amount of data.

In addition, each RHUI server (RHUA node or CDS node) requires a separate file system of the required size. It is important to use technologies such as LVM, SAN, or NAS storage that allow you to increase the size of the content repository if needed.