Automated Satellite Workshop: RHEL In-place Upgrade Automation Exercise - Your Lab Environment

Table of Contents

Objectives

Guide

Your Lab Environment

The workshop is provisioned with a pre-configured lab environment. You will have access to a host deployed with Ansible Automation Platform (AAP) which you will use to control the playbook and workflow jobs that automation the RHEL in-place upgrade workflow steps. You will also have access to three RHEL hosts. These are the hosts where we will be upgrading the RHEL operating system (OS).

Role Inventory name
Ansible Automation Platform controller ansible-1
Satellite Server satellite
Managed Host 1 - RHEL node1
Managed Host 2 - RHEL node2
Managed Host 3 - RHEL node3
Managed Host 4 - CentOS/OracleLinux node4
Managed Host 5 - CentOS/OracleLinux node5
Managed Host 6 - CentOS/OracleLinux node6

Step 1 - Access the AAP Web UI

The AAP Web UI is where we will go to submit and check the status of the Ansible playbook jobs we will use to automate the RHEL in-place upgrade workflow.

Step 2 - Access the Visual Studio Code Web UI

We will use Visual Studio Code (VS Code) as it provides a convenient and intuitive way to use a web browser to edit files and access terminal sessions. If you are a command line hero, direct SSH access is available if VS Code is not to your liking. There is a short YouTube video to explain if you need additional clarity: Ansible Workshops - Accessing your workbench environment.

Note

A welcome wizard may appear to guide you through configuring your VS Code user experience. This is optional as the default settings will work fine for this workshop. Feel free to step though the wizard to explore the VS code bells and whistles or you may just skip it.

Step 3 - Open a Terminal Session

Terminal sessions provide access to the RHEL commands and utilities that will help us understand what’s going on “behind the curtain” when the RHEL in-place upgrade automation is doing its thing.

Step 4 - Access the Satellite Web UI

The Satellite Web UI is where we will go to review the Lifecycle Environments, Content Views and Activation Keys configured on the Satellite, as well as tracking the status of the RHEL hosts as we proceed through the upgrade workflow through as they move to the next RHEL major version.

Step 5 - Access the RHEL Web Console

We will use the RHEL Web Console to review the results of the Leapp pre-upgrade reports we generate for our three-tier app servers.

Step 6 - RHEL In-place Upgrade Automation exercise job template deploy

Step 7 - Challenge Labs

You will soon discover that many exercises in the workshop come with a “Challenge Lab” step. These labs are meant to give you a small task to solve using what you have learned so far. The solution of the task is shown underneath a warning sign.

Conclusion

In this exercise, we learned about the lab environment we will be using to continue through the workshop exercises. We verified that we are able to use VS Code in our web browser and from there we can open terminal sessions. We also made sure we are able to access the AAP Web UI which will be the “self-service portal” we use to perform the next steps of the RHEL in-place upgrade automation workflow. We also made sure we are able to access the Satellite Web UI where we can review the repositories providing the packages for the RHEL in-place upgrade automation workflow, as well as the status of the hosts themselves. Next, we connected to the RHEL Web Console where we will soon be reviewing pre-upgrade reports. Finally, we ran a job template which employed Configuration as Code (CaC) to populate additional job and workflow templates, as well as additional Ansible inventory sources.

Use the link below to move on the the next exercise.


Navigation

Next Exercise

Home