Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Setting Up the Undercloud for RHOSP 17.1

Follow this topic to set up the undercloud for a Contrail Networking deployment on RHOSP 17.1.

Prepare for Director Installation

Use this example procedure to prepare for RHOSP 17.1 director installation on a node running a freshly installed RHEL 9.2 OS.

Note: This procedure tailors the standard RHOSP 17.1 undercloud preparation procedure to our example. We provide this procedure purely for illustration and convenience. This procedure in no way supersedes the procedures in Red Hat documentation. Where conflicting information exists between this procedure and the documented Red Hat procedures, the Red Hat documentation prevails.
  1. SSH into the undercloud node as root.
  2. Create the stack user.
    1. Create the user and configure the password.
    2. Add the user to the sudo user list.
  3. Switch to the new stack user and perform the remaining steps as this new stack user.
  4. Configure the hostname if you didn't already configure it during OS installation.
    For example, to set the hostname to undercloud.contrail.lan:
  5. Add an entry for this hostname to the /etc/hosts file.
    For example, add this line to /etc/hosts using sudo:where 192.168.213.10 is the IP address of the interface connecting the director to the provisioning network.
  6. Set the locale to UTF-8.
  7. Register the machine and update the packages.
    1. Register the machine.
      Enter your Red Hat user name and password when prompted.
    2. Set the release to RHEL 9.2.
    3. Disable all default repositories, and enable the required RHEL 9.2 repositories.
      Note: You might need to manually attach a pool before you can run this command if your license doesn't allow automatic entitlement. See Red Hat documentation.
    4. Update the packages.
  8. Reboot the machine.
  9. SSH back in as the stack user and install the Tripleo client.
  10. Prepare the containers-prepare-parameter.yaml file.
    1. Generate the default containers-prepare-parameter.yaml.
    2. Configure the file to suit your deployment.
      For this example, we simply add the registry.redhat.io login credentials to the parameter_defaults section and leave all other content as is.where <my_username> and <my_password> are your Red Hat login credentials.

See Also

Install the Director

Use this example procedure to install the director.

Note: This procedure tailors the standard RHOSP 17.1 undercloud installation procedure to our example. We provide this procedure purely for illustration and convenience. This procedure in no way supersedes the procedures in Red Hat documentation. Where conflicting information exists between this procedure and the documented Red Hat procedures, the Red Hat documentation prevails.
  1. SSH into the undercloud node as stack.
  2. Configure the undercloud.
    1. Copy the undercloud configuration file sample.
    2. Modify undercloud.conf to suit your deployment.
      Here is the configuration for our example:Table 1 describes the main configuration parameters. For more information or for parameters not described, see Red Hat documentation.
      Table 1: Main Undercloud Configuration Parameters
      Parameter Description Setting
      local_ip IP address of interface attached to provisioning network. 192.168.213.10/24
      local_interface Name of interface attached to provisioning network. enp2s0
      container_images_file Location of containers-prepare-parameter.yaml file. /home/stack/containers-prepare-parameter.yaml
      undercloud_ntp_servers Name or IP address of your NTP server(s). Specific to your deployment.
      undercloud_nameservers Name or IP address of your DNS server(s). Specific to your deployment.
      gateway Gateway for the provisioning network. We're using the undercloud VM as the gateway. 192.168.213.10
      cidr The subnet mask for the provisioning network. 192.168.213.0/24
      dhcp_start The start of the range of IP addresses that the undercloud will assign to devices in the provisioning network. 192.168.213.150
      dhcp_end The end of the range of IP addresses that the undercloud will assign to devices in the provisioning network. 192.168.213.200
      inspection_iprange The range of IP addresses that the undercloud will assign during inspection. This range must be outside the regular DHCP assignment range. 192.168.213.201,192.168.213.230
  3. Install the director.
  4. Confirm that the RHOSP service containers are running.

See Also

Obtain and Import the Base Overcloud Images

After you install the undercloud, obtain and import the base overcloud images to the undercloud. These are the kernel images that Red Hat provides for introspection and deployment of overcloud nodes.

Note: This procedure tailors the standard RHOSP 17.1 overcloud image import procedure to our example. We provide this procedure purely for illustration and convenience. This procedure in no way supersedes the procedures in Red Hat documentation. Where conflicting information exists between this procedure and the documented Red Hat procedures, the Red Hat documentation prevails.
  1. SSH into the undercloud as the stack user.
  2. Source the stackrc file.
  3. Obtain the base overcloud images.
    This installs the images tarfile into the /usr/share/rhosp-director-images directory.
  4. Extract the images to the images directory.
  5. Import the images to the director so that the director can serve these images to the overcloud nodes as they come up.
    You can find the overcloud image in /var/lib/ironic/images and the introspection PXE images in /var/lib/ironic/httpboot.
You've installed the undercloud. You're now ready to create the overcloud.

See Also