C.3. Provisioning Templates

A provisioning template is a collection of settings that defines the way in which a base operating system is installed on a host, and corresponds to a kickstart file for Red Hat Enterprise Linux systems. In the user interface, you can create and work with standalone provisioning templates in which all required settings are contained in a single template, and blocks of code that can be used across multiple provisioning templates, such as snippets, post-installation scripts, and generic installation scripts.

Note

The default provisioning template used to provision hosts in a RHEL OpenStack Platform environment can be edited as necessary to configure custom options. However, options that are configured using dedicated user interface elements, such as the root password, time zone, or custom repos, must be configured using the relevant operating system parameter or deployment option.
Create a new provisioning template entry.

Procedure C.5. Creating a Provisioning Template

  1. From the title bar in the main screen of the user interface, click HostsProvisioning templates.
  2. Click New Template.
  3. Configure general provisioning template details:
    1. Enter a name for the provisioning template in the Name field.
    2. Enter the body of the provisioning template in the Template editor text area.
    3. Enter a comment describing the creation of the provisioning template in the Audit Comment field.
  4. Configure the provisioning template type:
    1. Click the Type tab.
    2. Select Snippet to designate the provisioning template as a snippet. A snippet is not a standalone provisioning template, but a part of a provisioning template that can be inserted into other provisioning templates.
    3. If you did not select the Snippet check box, select the type of the provisioning template from the Type list:
      • PXELinux: A PXELinux template.
      • PXEGrub: A PXEGrub template.
      • iPXE: An iPXE template.
      • Provision: The main provisioning template, such as a kickstart file for Red Hat Enterprise Linux systems.
      • finish: A post-installation script such as that specified in a kickstart file for Red Hat Enterprise Linux systems.
      • script: A generic script that can be run during the provisioning process, such as that specified in a kickstart file for Red Hat Enterprise Linux systems.
      • user_data: A user_data block.
      • ZTP: A Zero Touch Provisioning template.
  5. Configure the provisioning template associations:
    1. Click the Associations tab.
    2. From the All items list in the Applicable Operating Systems section, click the name of an operating system entry to move that operating system entry to the Selected items list and make the provisioning template available to that operating system entry.
    3. Optionally, click Add combination and select a host group from the Host Group list or an environment from the Environment list to make the provisioning template available to the specified combination of host groups and environments.
  6. Click Submit.
Lock a provisioning template to prevent users from editing its properties.

Procedure C.6. Locking a Provisioning Template

  1. From the title bar in the main screen of the user interface, click HostsProvisioning templates.
  2. Click the disclosure arrow next to the Clone button for the provisioning template.
  3. Click Lock.
    The Lock button

    Figure C.3. The Lock button

  4. Click OK when prompted.
You have locked the provisioning template, and users cannot edit the properties of that provisioning template other than its associations. You must unlock the provisioning template to edit any other properties.