Module 1 Lab 1: Platform - OpenShift Dev Spaces for Ansible Development

  • Before you start:

  • Prepares you for: Launching OpenShift Dev Spaces

  • Lab Type: Foundational (activities in this lab prepare you for the remaining labs)

  • Estimated Time: 10 - 20 minutes

We will explore the Red Hat OpenShift Dev Spaces environment you will be working within and learn how to launch and configure development workspaces for Ansible automation development. This includes understanding the various components available in the lab environment, authenticating with git repositories, and using the Ansible Development Tools.

This lab walks through the various components within the lab environment including launching, configuring and using Dev Spaces on OpenShift as your primary development environment for Ansible.

Learning Objectives

After completing this module, you will be able to:

  • Navigate the Red Hat OpenShift Dev Spaces interface

  • Launch and configure development workspaces

  • Understand the components included in the lab environment

  • Set up authentication for git repositories

  • Use basic Ansible Development Tools features

1: Introduction: What is included in the lab environment

  1. Red Hat OpenShift Cluster

  2. Ansible Automation Platform

  3. Red Hat OpenShift Dev Spaces

  4. Gitea Git Server

  5. Windows 2019 managed host

  6. Lab Instructions

2: Contributing to this Lab Documentation

If you see an error in this lab, fork and submit a pull request against https://github.com/rhpds/ansible-super-lab-showroom

3: Dev Spaces console

Red Hat OpenShift Dev Spaces provides consistent, reproducible development environments based on the open-source project Eclipse Che.

It provides, by default, a Visual Studio Code (VS Code) environment as configured by a devfile, a YAML file that defines the entire workspace as code—including all necessary tools, runtimes, and project source. This file is used to instantly generate a pre-configured, containerized development environment, ensuring every developer on a team has an identical setup and solving the "it works on my machine" problem.

3.1: Launching Dev Spaces from OpenShift

  1. Launch the OpenShift Web Console

  2. Select the htpasswd_provider button and use the credentials provided in the Environment Details page to login to the OpenShift console

  3. Use the 9-block icon in the upper right to launch Red Hat OpenShift Dev Spaces directly from the OpenShift console header.

    OpenShift console header showing the 9-block application launcher icon for quick access to Dev Spaces
    Alternatively, the direct URL is https://devspaces.{openshift_cluster_ingress_domain} also available in Environment Details.

4: Dev Spaces Workspace

4.1: Launching a specific Dev Spaces Workspace

Once you have launched the OpenShift Dev Spaces console, use the following steps to access your Ansible Dev Space workspace.

  1. Login via OpenShift authentication using the same credentials as the OpenShift console

  2. Select Allow selected permissions to authorize access and launch the console

  3. Scroll down and select the workspace titled Ansible Dev Space

    Dev Spaces workspace selection page showing available workspaces including Ansible Dev Space
    It will take a few minutes for the Dev Spaces instance to initialize. When it has loaded, a Visual Studio Code interface will appear.
    Dev Spaces workspace loading screen showing VS Code interface initialization

  4. Click the Trust Publishers and Install button to trust the extension publishers that are included within the Dev Spaces workspace

  5. Click the Yes, I trust the Authors button to trust the workspace authors (your instructors).

  6. Wait a few minutes until the additional extension icons appear for Ansible and OpenShift on the left side.

    VS Code interface in Dev Spaces showing Ansible and OpenShift extension icons in the left sidebar

5: Ansible and OpenShift Extensions

For this lab, we have have provided a .code-workspace configuration that included these extensions along with additional configurations to curate your development environment. See https://github.com/jeffcpullen/devspaces-example/blob/main/devspaces.code-workspace for the source of this workspace configuration.

  1. Click on the Ansible extension icon to access the Ansible Development Tools extension (covered in a subsequent lab)

    Ansible extension interface in VS Code showing available Ansible development tools

6: Accessing a Terminal

The majority of the exercises in this lab will be performed using the Visual Studio Code terminal.

  1. Open a new terminal by selecting the VS Code menu starting with the hamburger (3 horizontal lines) in the top left, then selecting Terminal → New Terminal

    VS Code terminal interface showing basic command line operations in the Dev Spaces environment

  2. Explore the environment:

    whoami
    user

  3. Check the Dev Spaces Workspace container OS release:

    cat /etc/redhat-release
    Red Hat Enterprise Linux release 9.7 (Plow)

  4. This workspacs provides access to ansible and additional developer tools:

    ansible --version
    ansible [core 2.19.3]
  config file = None
  configured module search path = ['/home/user/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.11/site-packages/ansible
  ansible collection location = /home/user/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.11.13 (main, Aug 21 2025, 00:00:00) [GCC 11.5.0 20240719 (Red Hat 11.5.0-11)] (/usr/bin/python3.11)
  jinja version = 3.1.6
  pyyaml version = 6.0.3 (with libyaml v0.2.5)

Conclusion

In this lab, you have learned:

  1. The resources provided in the lab environment

  2. Assessing the OpenShift environment

  3. How to launch and navigate an Red Hat OpenShift Dev Spaces workspace

  4. How to provide feedback and contributions to this lab environment

This foundation prepares you to start your Ansible Bootcamp Enablement journey.

Helpful Links

For additional references, refer to the following resources:

  1. Using Ansible Development Workspaces for Automation Content Development

  2. Authenticating to a Git server from a Workspace.

  3. Source for the Dev Space Workspace

  4. Source for this lab content