Red Hat Summit Red Hat SummitSuporteConsoleDesenvolvedoresComeçar um testeContato

Este conteúdo não está disponível no idioma selecionado.

Chapter 3. Preparing provisioning content

You have to configure provisioning content that will be used for installation of the operating system on the provisioned host.

3.1. Preparing a synchronized Kickstart repository
Copiar o link

Satellite contains a set of synchronized Kickstart repositories that you use to install the provisioned host’s operating system. For more information about adding repositories, see Synchronizing repositories in Managing content.

Use this procedure to set up a Kickstart repository.

Prerequisites

You must enable both BaseOS and AppStream Kickstart before provisioning.

Procedure

  1. Add the synchronized Kickstart repository that you want to use to the existing content view, or create a new content view and add the Kickstart repository.

    For Red Hat Enterprise Linux 8, ensure that you add both Red Hat Enterprise Linux 8 for x86_64 - AppStream Kickstart x86_64 8 and Red Hat Enterprise Linux 8 for x86_64 - BaseOS Kickstart x86_64 8 repositories.

    If you use a disconnected environment, you must import the Kickstart repositories from your Red Hat Enterprise Linux binary DVD.

  2. Publish a new version of the content view where the Kickstart repository is added and promote it to a required lifecycle environment. For more information, see Managing content views in Managing content.
  3. When you create a host, in the Operating System tab, for Media Selection, select the Synced Content checkbox.

To view the Kickstart tree, enter the following command: 

$ hammer medium list --organization "My_Organization"
Copy to Clipboard Toggle word wrap

3.2. Adding installation media to Satellite
Copiar o link

Installation media are sources of packages that Satellite Server uses to install a base operating system on a machine from an external repository. You can use this parameter to install third-party content. Red Hat content is delivered through repository syncing instead.

You can view installation media by navigating to Hosts > Provisioning Setup > Installation Media.

Installation media must be in the format of an operating system installation tree and must be accessible from the machine hosting the installer through an HTTP URL.

By default, Satellite includes installation media for some official Linux distributions. Note that some of those installation media are targeted for a specific version of an operating system. For example CentOS mirror (7.x) must be used for CentOS 7 or earlier, and CentOS mirror (8.x) must be used for CentOS 8 or later.

If you want to improve download performance when using installation media to install operating systems on multiple hosts, you must modify the Path of the installation medium to point to the closest mirror or a local copy.

To use the CLI instead of the Satellite web UI, see the CLI procedure.

Procedure

  1. In the Satellite web UI, navigate to Hosts > Provisioning Setup > Installation Media.
  2. Click Create Medium.
  3. In the Name field, enter a name to represent the installation media entry.

  4. In the Path enter the URL that contains the installation tree. You can use following variables in the path to represent multiple different system architectures and versions:

    • $arch – The system architecture.
    • $version – The operating system version.
    • $major – The operating system major version.

    • $minor – The operating system minor version.

      Example HTTP path: 

      http://download.example.com/centos/$version/Server/$arch/os/
      Copy to Clipboard Toggle word wrap
  5. From the Operating system family list, select the distribution or family of the installation medium. For example, CentOS and Fedora are in the Red Hat family.
  6. Click the Organizations and Locations tabs, to change the provisioning context. Satellite Server adds the installation medium to the set provisioning context.
  7. Click Submit to save your installation medium.

CLI procedure

  • Create the installation medium using the hammer medium create command: 

    $ hammer medium create \
--locations "My_Location" \
--name "My_Operating_System" \
--organizations "My_Organization" \
--os-family "Redhat" \
--path "http://download.example.com/centos/$version/Server/$arch/os/"
    Copy to Clipboard Toggle word wrap

3.3. Configuring Satellite to provision from a Red Hat Image Builder image
Copiar o link

In Satellite, you can enable integration with the RHEL web console to perform actions and monitor your hosts. Using the RHEL web console, you can access Red Hat Image Builder and build images. Afterwards, you can use these images to provision hosts.

Additional resources

3.3.1. Provisioning from a Red Hat Image Builder image on Capsule
Copiar o link

You can upload a Red Hat Image Builder image to Satellite and use this image to provision hosts by using network boot.

When you provision from a Red Hat Image Builder image, Anaconda installer partitions disks, downloads and mounts the image, and copies files over to a host.

Prerequisites

  • An existing TAR image created by using Red Hat Image Builder in the RHEL web console. Ensure that your blueprint to build the image includes the required packages.
  • If you want to use Capsule Server URL, then the referenced lifecycle environment, such as Library, must be synchronized to that Capsule Server. For more information, see Adding lifecycle environments to Capsule Servers in Installing Capsule Server.

Procedure

  1. On Satellite, create a custom product, add a custom file type repository to this product, and upload the image to the repository. For more information, see Importing individual ISO images and files in Managing content.
  2. In the Satellite web UI, navigate to Configure > Host Groups.
  3. Select the host group that you want to use.
  4. Click the Parameters tab, and then click Add Parameter.

  5. Create a parameter named kickstart_liveimg with type string and set the value to the full URL of the image location or the file name of the image inside a published content view, for example:

    • Full URL: https://capsule.example.com/pulp/content/My_Organization_Label/Library/custom/My_Product_Label/My_Repository_Label/My_Image_Name.tar

    • Image file name: My_Image_Name.tar

      You can use the image file name only if the host is subscribed to a single content view and lifecycle environment, and the kt_activation_keys parameter is defined for the host. The content view must be published.

      If a content source is assigned to the host, Satellite will use the content source Capsule of the host. If a content source is not assigned, Satellite will use Satellite Server.

  6. Click Submit to save your changes.

Additional resources

3.3.2. Provisioning from a Red Hat Image Builder image on an HTTP server
Copiar o link

You can upload a Red Hat Image Builder image to an HTTP server and use this image to provision hosts by using network boot.

When you provision from a Red Hat Image Builder image, Anaconda installer partitions disks, downloads and mounts the image, and copies files over to a host.

Prerequisites

  • An existing TAR image created by using Red Hat Image Builder in the RHEL web console. Ensure that your blueprint to build the image includes the required packages.

Procedure

  1. Copy the image to an existing HTTP server that your hosts can reach.
  2. In the Satellite web UI, navigate to Configure > Host Groups.
  3. Select the host group that you want to use.
  4. Click the Parameters tab, and then click Add Parameter.
  5. Create a parameter named kickstart_liveimg with type string and set the value to the URL of the image location, such as https://webserver.example.com/path/My_Image_Name.tar.
  6. Click Submit to save your changes.

Additional resources

3.3.3. Packages required in a Red Hat Image Builder image
Copiar o link

For the use in Satellite, the Red Hat Image Builder image must contain the following minimum of packages:

  • NetworkManager
  • authselect
  • chrony
  • dnf
  • dracut
  • efibootmgr
  • firewalld
  • grub2
  • grub2-efi
  • grub2-tools-extra
  • insights-client – required only if you plan to use Red Hat Lightspeed reporting
  • iproute
  • iputils
  • kernel
  • kernel-core
  • lvm2
  • subscription-manager
  • wget
Voltar ao topo
Red Hat logoGithubredditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar. Explore nossas atualizações recentes.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja o Blog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

Theme

© 2025 Red Hat