Partners are expected to have a Vendor Single Sign On (SSO) account, a Product profile, and must compulsorily complete the Align, Build and Certify (ABC) Workflow on Red Hat Connect for Technology Partners before beginning the certification process. The SSO credentials will be used to access Red Hat products, the certification toolset and other Red Hat assets.

The certification process assures that a certified solution/product meets all the requirements of an enterprise cloud and is jointly supported by Red Hat and your organization. A certified product is listed on Red Hat OpenStack Certification Ecosystem Page.

The certification specific policies and requirements are covered in Red Hat OpenStack Certification Policy Guide.

Install the relevant version of Red Hat OpenStack Platform (against which the certification is required) using Red Hat OpenStack Platform Product Documentation. After Red Hat OpenStack Platform is installed, read the product documentation to understand its usage and configuration.

After installing Red Hat OpenStack Platform, install the plugin/driver or application that needs to be certified on an Overcloud node. Complete the following steps after the installation:

For more information, refer Test Environment Overview. To install the required software packages on the OpenStack deployment-under-test/test client, complete the following steps:

The software packages required on the test server must be installed by subscribing to Red Hat Certification channel via CDN. This ensures that the required dependencies are automatically installed.

To install the required software packages on the test server, complete the following steps:

If your network utilizes a proxy, you may need to manually configure the test server and/or test client for the proxy as outlined below:

In the test server, update the /etc/rhcert.xml file as per the following settings:

<urls>
<proxy-url protocol="http">PROXY_SERVER:PROXY_PORT</proxy-url>
<proxy-url protocol="https">PROXY_SERVER:PROXY_PORT</proxy-url>
</urls>

Replace PROXY_SERVER with the IP or dns-name of your proxy server, and PROXY_PORT with your proxy port number.

For example:

<proxy-url protocol="http">http://rhcert-example.redhat.com:3148<proxy-url>
<proxy-url protocol="https">https://rhcert-example.redhat.com:3148<proxy-url>

To open port 80 and port 8009 on test server and test client, run the rhcert-cli register command.

For more information, we recommend you to refer How can we access to the Hardware Certification (rhcertd web interface) via proxy?

To create a new certification request, complete the following steps:

If the OpenStack application undergoing certification falls under this category (see Red Hat OpenStack Certification Policy Guide for more details), complete the following steps on the test server to run certification tests on the OpenStack deployment-under-test/test client.

This test checks the generation of tempest_config based on the lab environment details. Being an interactive test it asks for the following details:

If the OpenStack application undergoing certification falls under this category see Red Hat OpenStack Certification Policy Guide, and perform the steps documented in the Section 4.2, “Preparing the Test Server” on the test server to run certification tests on the OpenStack deployment-under-test.

Partners need to perform following steps on Red Hat certification web UI to run the trusted container test:

Certification tests are run on the application-under-test. The status of the certification test run is displayed on the Testing Page under the relevant hostname.

Figure 6.9. Test Run Status

After the test run completes, the test logs from the openstack/supportable tests are stored in the same log file as for the openstack/director test on the test server. See section Section 7.1, “Viewing and Submitting the Test Logs using web UI” in the guide to submit the test logs.

To run the certification tests using Red Hat Certification CLI (rhcert-cli), execute the following commands on the System Under Test (SUT):

#rhcert-cli clean
#rhcert-cli plan
#rhcert-cli run --test cinder_volumes

#rhcert-cli run --test supportable --test tempest_config --test cinder_volumes --test cinder_consistency_groups

All component-based tests in openstack are tagged, which means the following commands will run all the tests for cinder, manila or neutron, respectively:

#rhcert-cli run --tag cinder
#rhcert-cli run --tag manila
#rhcert-cli run --tag neutron

After the tests run, the test logs/results are automatically collected in a single .xml.gz file. To save the test results/logs, run the following command on the image-under-test.

# rhcert-cli save --server [hostname/IP address of LTS]

It is also possible to directly submit the test results/logs for validation without saving them on the image-under-test.

The test runs generate two log files based on the type of product undergoing certification. The log files generated are as follows:

It is mandatory to submit the log files generated based on your product type to Red Hat Certification services for review.

To submit the test logs using Red Hat Certification CLI, run the following command on the image-under-test.

# rhcert-cli submit

Type your Red Hat account credentials previously enabled for certifcation in the Red Hat Catalog Username and Password.The Certification ID is generated when you successfully create a certification request. Type the ID of the certification request in the Certification ID dialog box.

The # rhcert-cli submit command works only if the image has a network that can connect to the Red Hat services. The command submits the latest timestamped test logs on your host/image to Red Hat certification services for review. The test log file is reviewed by Red Hat certification services and Red Hat Review team. The certification results are displayed on Red Hat Certification web user interface.

If the image-under-test does not have internet access, save the test logs on the image-under-test using the # rhcert-cli save --server [hostname/IP address of LTS] command.