Chapter 1. Introduction to Red Hat Openstack Services on OpenShift certification policy guide

This guide describes the technical certification requirements for software certification Partners who want to offer their applications, management applications, or plugin or driver software for use with Red Hat OpenStack Services on OpenShift (RHOSO) in a jointly supported customer environment.

The certification process includes a series of tests to ensure that certified solutions meet enterprise cloud requirements. This process is supported by both Red Hat and the Partner’s organization.

The Red Hat OpenStack Services on Openshift Certification Workflow Guide includes multiple tests, each with a series of subtests and checks. Not all tests are required for each certification.

Submit logs from a single run with all mandatory and optional tests to Red Hat for new certifications and recertifications. The certification tooling and workflow supports certifications that are in progress for 90 days.

Red Hat encourages using the latest version of the certification tooling and workflow for the certification process. A 90-day grace period is provided for previous versions of the tooling and workflow upon a new release, allowing ongoing certifications to proceed without disruption. After the grace period, results from older tooling versions are not accepted.

The latest version of the certification tooling and workflow is available via Red Hat Subscription Management and documented in the Red Hat OpenStack Services on OpenShift Certification Workflow Guide.

To start your certification journey, you must meet the following requirements:

As part of Red Hat OpenStack Services on OpenShift (RHOSO), Red Hat distributes components committed to a release of the upstream OpenStack project. These components are called In-tree components. You are responsible for the certification and distribution of all dependencies that are not part of the upstream OpenStack project.

You are also responsible for distributing products or components that are not committed to the upstream OpenStack project. These components are referred to as Out-of-tree components.