1. Publicly Available Container Image for rt-tests:

• • Feature: Provision of the current Fedora rt-tests version as a publicly accessible container image via Quay.io.
  • Reason: Making a container image for the latest rt-tests version accessible to both customers and community members utilizes publicly sourced materials. This facilitates the utilization of newer rt-tests versions for testing on earlier RHEL editions, enhancing compatibility and testing efficiency.
  • Result: Development of a Dockerfile that retrieves the latest rt-tests RPM and a script that automates the detection of new versions, followed by their upload to Quay.io. This ensures the rt-tests tool remains up-to-date and widely available.
  • Notes: This initiative concentrates on leveraging Fedora as the source for publicly distributing rt-tests. Presently, there are no plans to offer cs9 container images to avoid duplication. The focus is to supply container images for the latest active RHEL release via the Red Hat Ecosystem Catalog, necessitating integration with subscription management systems and utilization of UBI as the base image. A separate issue will detail these considerations further.

1. Developer-Oriented Docker File for rt-tests:

• • Feature: Capability to compile the most recent or developer-modified source code effortlessly using a Dockerfile and container.
  • Reason: Traditionally, upstream developers required a specialized development setup for rt-tests. Providing a straightforward, environment-agnostic method for deploying and testing code changes via containers would significantly aid development efforts.
  • Result: A Dockerfile has been introduced and incorporated into the upstream project, available in the repository. This inclusion streamlines the process of developing and testing modifications to rt-tests within a containerized environment, fostering an efficient development workflow for contributors.

Updated Requirements:

This container will be delivered as an 'all-in-one' container including rtla and rteval. This container will be interactive only, and will have no automation built in.