Red Hat Training

A Red Hat training course is available for Red Hat Certified Cloud and Service Provider Certification

Red Hat Cloud Instance Type Workflow

Red Hat Certified Cloud and Service Provider Certification 1.0

For Use with Red Hat Cloud Instance Type Workflow

Red Hat Customer Content Services

Abstract

This guide describes the workflow for Partners to certify their Cloud Instance Type with Red Hat. It provides an overview of the entire certification process, explains how to set up the certification environment, create new certification requests, perform certification test, submit the results to Red Hat for verification, and complete the certification.

Chapter 1. Introduction

This guide provides an overview of the Cloud Instance Type certification workflow for Partners who want to offer their own hardware via cloud infrastructure. It is geared towards the engineer who has been tasked with certifying their company’s products to run with Red Hat’s products.

1.1. Cloud Instance Type Certification Process Summary

The Red Hat Certification Program is Red Hat’s method of certifying Cloud Instance Type compatibility with Red Hat Enterprise Linux (RHEL) and other Red Hat software products. The program has the following three main elements:

  • the test suite, which tests the instance undergoing certification.
  • the Red Hat Certification Catalog, which displays certified Cloud Instance Type to the public, and
  • a joint support relationship between Red Hat and the Partner, whose Cloud Instance Type will undergo the certification.

Partners are expected to perform the following Preliminary and Certification steps:

Preliminary steps:

  1. Establish a certification relationship with Red Hat.
  2. Create a test environment consisting of the Partner’s product and the Red Hat product combination to be certified.
  3. Do preliminary testing to ensure this combination works well.
  4. Install the redhat-certification tool.

The preliminary steps are further explained in Chapter 3, Program and Product Prerequisites and Chapter 4, Configuring the Test Environment

Certification steps:

  1. Create a Cloud Instance Type certification request the certification using redhat-certification tool.
  2. Create the official test plan.
  3. Run the tests specified in the official test plan and submits results using redhat-certification to Red Hat for analysis.
  4. Analyze the test results and marking credit as appropriate and communicating any required retesting.
  5. Provide details to Red Hat regarding a representative instance sample that covers the Instance Type that is being certified.

The certification steps are expanded upon in Chapter 5, Certification Workflow

When all tests are PASS, the certification is complete and the entry is made visible to the public on the external Red Hat Certification Catalog.

Chapter 2. Giving Feedback and Getting Help

2.1. Giving Feedback

If you experience any difficulty during the certification process with a Red Hat product, the certification toolset, or with a procedure described in this guide, visit Red Hat Customer Portal. The portal allows you to gain access to Red Hat product documentation as well as solutions and technical articles about Red Hat products. You may also open a case under the following instances:

  • To report issues and get help with the certification process
  • To submit feedback and request enhancements in the certification toolset & documentation
  • To receive assistance on the Red Hat product on which your product/application is being certified
Note

To receive Red Hat product assistance, it is necessary to have the required product entitlements or subscriptions, which may be separate from the Partner program and certification program memberships.

2.2. Opening a Support Case

To open a support case, see How do I open and manage a support case. Complete the support case by providing the following mandatory details:

  • From the Product field, select Red Hat Enterprise Linux.
  • From the Product Version field, select the version of the Red Hat product on which your product/application is being certified.
  • In the Problem Statement field, type a problem statement/issue or feedback using the following format:

    {Partner Certification} (The Issue/Problem or Feedback)

  • Replace (The Issue/Problem or Feedback) with either the issue/problem faced in the certification process/Red Hat product or feedback on the certification toolset/documentation. For example: {Partner Certification} Error occurred while submitting certification test results using Red Hat Certification application.
Important

It is mandatory to write the problem statement with the {Partner Certification} tag to ensure assignment of the case to the appropriate group(s).

All cases related to Certification use a Severity 3 SLA which requires one business day response time.

Chapter 3. Program and Product Prerequisites

It is expected that you have a basic knowldge about the software that is being used for certification and familiar with concepts about operating system installation, software installation, and operational knowledge of Cloud Instance Type.

Before starting the certification process, we recommend that you read the Cloud Instance Type Policy Guide to understand requirements and policy for Cloud Instance Type certification.

3.1. Program Membership, Accounts, and Entitlements

To certify instances, active membership in the Certified Cloud and Service Provider (CCSP) Program is required. If you are not already a member, visit Red Hat Connect for Business Partners to learn more and become a member.

During the CCSP program sign-up process, a Red Hat Single Sign-On (SSO) account will be created for you. This SSO account and its credentials will be used throughout the certification process to access Red Hat products, the certification toolset, and other Red Hat assets.

The SSO account must be entitled with certification privileges. To do this, open a support case and include the following information in the Problem Statement field:

  • Partner Certification: CCSP Certification Access for {Red Hat SSO Username} at {Partner Name}
  • Optionally, include all of the following information in the field “What do you expect to see?” to have a Red Hat associate service your case and create the first certification request for you:
  • Name of the Cloud Instance Type or the Cloud Instance Type Service Offering
  • Public Catalog URL/Public URL of the Cloud Instance Type or Cloud Instance Type Service Offering
  • Supported Regions (Global/Australia & New Zealand/ASEAN/EMEA/Japan/LATAM/North America/Public Sector):
  • Supported Languages
  • Any 3rd Party Certifications Acquired (E.g. FedRAMP, Systrust, SAS 70, PCI, Other Non-NA Certs, etc.):
  • RHEL Version ( 8.x ) of the first certification desired to be achieved
  • Attached Partner Brand Logo (PNG 256x256)
Important

Instance Type Certification must be performed using drivers provided by Red Hat. Any third-party drivers required for enablement is not eligible for certification.

3.2. Cloud Instance Type Certification Requirements

To gain a cloud Instance type certification, it is expected to certify the cloud Instances in catalog. The certification process provides your Red Hat customers with the assurance that they will have a consistent experience across cloud instance providers, the customer’s experience comes with the highest level of support, and good security practices are available to the customers.

The Instance needs to meet the its complete list of requirements and policies that are outlined in the Cloud Instance Type Certification Policy Guide. The test plan is created based on certification policy.

Chapter 4. Configuring the Test Environment

The test environment for RHEL certification consists of System Under Test (SUT), and Local Test Server (LTS). The appropriate version(s) of Red Hat Enterprise Linux for your environment can be downloaded from the Red Hat Customer Portal.

The certification test suite that runs on both the SUT and LTS is composed of the following packages:

  • LTS packages

    • redhat-certification (RHEL 7 only)
    • python-django (RHEL 7 only)
    • python-django-bash-completion (RHEL 7 only)
  • SUT packages

    • dt
    • lmbench
    • stress
    • redhat-certification-backend
    • redhat-certification-hardware

All test suite packages are available on the Red Hat Customer Portal.

4.1. Configuring the System Under Test (SUT)

The SUT machine contains the Cloud Instance Type that will undergo certification. The SUT runs the version of RHEL on which the instance is being certified.

The certification test suite also requires two debuginfo files to be installed on the SUT:

  • kernel-debuginfo-$VERSION

    Where $VERSION is the running kernel version number as shown in the output of uname -a or via the kernel RPM filename

  • kernel-debuginfo-common-$ARCH-$VERSION

    Where $ARCH is x86_64, i686, etc. and $VERSION is the same as above

    The debuginfo packages can be downloaded from the Red Hat Customer Portal as explained in the Appendix of the Red Hat Knowledgebase article.

    1. Locate the SUT and all the components that must be tested as part of the certification activities.
    2. Download the appropriate architecture and version of RHEL, the certification test suite, and the necessary debuginfo packages from the locations mentioned earlier and install them on the SUT.

The OS should be configured as explained in the appropriate RHEL kickstart file. Choose the file that matches the version and architecture of RHEL you are certifying.

4.2. Configuring the Local Test Server (LTS)

Perform the following steps to prepare LTS:

  1. Locate an appropriate machine to function as the LTS.

    The LTS is not required to be a certified system; however, to ensure proper functionality, network connectivity should be of equal or greater speed than the interfaces on the SUT in order to properly test the SUT’s network devices. The LTS runs the latest version of RHEL 7.x. A single LTS system can control multiple SUT systems, but it should only perform network or kdump testing on one SUT at a time due to network bandwidth limitations.

  2. Download the appropriate architecture and version of

  3. Install them on the LTS.
  4. Configure the OS as explained in the appropriate RHEL kickstart file. Choose the file for RHEL 7 or RHEL 8.

    The kickstart files can be automatically downloaded and installed on the LTS. If you wish to manually download the files and place them on your LTS, here are the steps to take: After setting up a local test server as explained in Section 4.2, “Configuring the Local Test Server (LTS)”.

  5. Run the following command to start Apache, Red Hat Certification back-end server and the server listener process:

    # rhcertd start

4.2.1. Hosting Prebuilt Guest Files on the LTS

If the system being tested supports virtualization it must be tested. We have prebuilt guest files that are automatically downloaded by the SUT during the fv_* tests to satisfy this requirement. Those files can be hosted on your LTS if you wish to shorten the download time from the Red Hat FTP site, or if your testing environment is disconnected from the network.

The RHEL 8 - fv-images files for x86_64 architecture are available here.

The RHEL8 - aarch64 files for fv testing (Developer Preview) are available here.

The RHEL8 - ppc64le files for fv testing are available here.

The RHEL8 - s390x files for s390x are available here.

Certifying for RHEL 8

  1. Create a directory on the LTS called /var/www/rhcert/store/transfer/fv-images/RHEL8.
  2. Copy the following files of Red Hat Enterprise Linux 8 FTP site to the local directory

    • x86_64 architecture files:

      • hwcertData.img.tar.bz2 Results transfer package from guest to host
      • hwcert-x86_64.xml.tar.bz2 Full-virt guest configuration file for x86_64
      • hwcert-x86_64.img.tar.bz2 Full-virt KVM guest image for x86_64
    • aarch64 fv testing files:

      • hwcertData.img.tar.bz2 Results transfer package from guest to host
      • hwcert-aarch64.xml.tar.bz2 Full-virt guest configuration file
      • hwcert-aarch64.img.tar.bz2 Full-virt KVM guest image
      • hwcert-aarch64_VARS.fd.tar.bz2 Full-virt nvram file
    • ppc64le fv testing files:

      • hwcertData.img.tar.bz2 Results transfer package from guest to host
      • hwcert-ppc64le.xml.tar.bz2 Full-virt guest configuration file
      • hwcert-ppc64le.img.tar.bz2 Full-virt KVM guest image
    • s390x files:

      • hwcertData.img.tar.bz2 Results transfer package from guest to host
      • hwcert-s390x.xml.tar.bz2 Full-virt guest configuration file
      • hwcert-s390x.img.tar.bz2 Full-virt KVM guest image

4.3. Proxy Settings for Test Server and Test Client

To open port 80 and port 8009 on test server and test client, run the rhcert-cli register command. If your network utilizes a proxy, you need to manually configure the test server by updating the /etc/rhcert.xml file as per the following settings
  1. 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>

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

<proxy-url protocol="http">http://rhcert-example.redhat.com:3148<proxy-url>
<proxy-url protocol="https">https://rhcert-example.redhat.com:3148<proxy-url>
  1. Use FTP proxy to download FV images through FTP.

    For example:

    <urls>
    <proxy-url protocol="ftp">http://proxy.example.com:3287</proxy-url>
    </urls>

Chapter 5. Certification Workflow

The following diagram represents the entire Cloud Instance Type certification workflow along with the roles & responsibilities of Red Hat and the Partners.

Certification Workflow

5.1. Opening a New Cloud Instance Type Certification Request

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

  1. In your test server, launch the Red Hat Certification web user interface (WUI) in a browser using the http://machine-IP link.
  2. Type your Red Hat account credentials previously enabled for certification in the Username and Password fields. Click Login.
  3. Click the New Certification button. This will take you to Choose the Red Hat Certification web page.
  4. From the Product drop-down list, select Red Hat Enterprise Linux. The Version and Platform value gets generated automatically. However, Partners can select the version and platform fields according to their requirement. Click Next.
  5. On the next dialog box, Click New Product to create a product entry. Then choose the program, Red Hat Enterprise Linux Certified Hardware and Click Next.
  6. On the Product Definition form, fill in the product information to represent the set of instance type to be certified. Use the Make field to indicate the cloud service, and the Model field to indicate the name of the Cloud Instance Type to be certified (entries for specific sizes will be created later).

It displays a message with details of the requested Cloud Instance Type certification. After the request is created, monitor the request for questions from the review team.

5.2. Running Certification Tests

Certification tests can be run using Red Hat Certification web UI (by launching Red Hat Certification application on the local test server).

5.2.1. Running Certification Tests using Red Hat Certification WUI

To run certification tests on the instance-type-under-test using Red Hat Certification WUI, perform the following steps on the test server:

  1. Launch Red Hat Certification WUI in a browser using the http://machine-IP link. Replace machine-IP with the IP address/hostname of your machine.
  2. Type Red Hat account credentials previously enabled for certification in the Username and Password fields. Click Log In.
  3. On Red Hat Certification home page, click the Server settings tab.
  4. In the Register a System field, enter the hostname or IP address of the instance-type-under-test and then click Add. On the Red Hat Certification home page, click on your existing certification entry. The Progress tab displays the certification tests available in the certification test suite and the progress of the previous runs (if any).
  5. Click the Testing link to open the Testing Page and click Add System.
  6. In the Select host page, select the host/hostname of the instance-type-under-test and click Test.

    A certification test plan is ready for the instance-type-under-test. The status column displays a Finished test run status.

  7. Click Continue Testing.
  8. From the table, select all the tests which are displayed and then click Run Selected.
Note

It is mandatory to run all the tests which are displayed after the creation of a test plan for certification. It is recommended to select and run specific tests only for debugging purposes.

Result

Certification tests are run on the instance-type-under-test. The status of the certification test run is displayed on the Testing page. Tests with the interactive label will require feedback from the user during runtime. The status column on the Testing page displays a question and a textbox for inputs during testing. The test pauses until you provide a response and click Submit.

After the test run completes, the test logs from various tests are stored in a single log file in .xml.gz format.

5.3. Adding Certifications to Previously Certified Cloud Instance Type

To create a certification request for RHEL 7 on an instance that already has an in-progress or completed RHEL 6 certification request perform the following steps:

  1. Log in to Red Hat Certification and click the New Certification button.
  2. Select the Red Hat product, version, and platform for certification and click Next.
  3. State the Vendor, Make, Model (Name and Size), and Architecture of the product to be certified . Provide URL of Cloud Instance Type to be certified and click Next.

After the request is created, monitor the request for questions from the review team. Testing can begin as described in section Selecting and Running Tests when the test plan is complete.

5.4. Cloud Instance Type Pass-Through Certification

An Instance Type Pass-Through certification essentially creates a copy of a certified Cloud Instance Type, and lists it in a different vendor name, a different make, or a different model.

Pass-through is used when a vendor sells their Instance Type to a partner who then rebrands it, or if a vendor sells two or more Instance Type Product where one Instance Type Product is a superset of the other(s). In such situations, the vendor should have tested in the existing Cloud Instance Type Product certification as that covers all the Instances Sizes in the new Pass-Through certification.

After the Cloud Instance Type Product is certified, the Cloud Instance Type Size Pass-Through certification is performed. Each Cloud Instance Type Size individually undergoes Pass-Through certification and is published to catalog.

  1. To create a system certification refer Steps 1 to 4 of Open a New Cloud Instance Product Certification Request
  2. State the Vendor, Make, Model (Name and Size), and Architecture. Click the Instance Type button. This will take you to Choose the Certification Program web page.
  3. State the Vendor and Program as Cloud Instance Type. Click the Next button. This will take you to Define the Red Hat Cloud Instance Type Certification Vendor Cloud Instance Type certification web page.
  4. Fill in all the relevant details. From the drop down list of the Category field, select the category as Cloud Instance Type.

This creates the Cloud Instance Type Certification. The Red Hat certification team certifies and publishes the newly created Cloud Instance Type Certification. After the certificate is certified and published, it becomes public for other partners to refer it as a pass-through Cloud Instance Type.

Chapter 6. Running Tests and Submitting Logs for Review

6.1. Selecting and Running Tests

There are two types of tests:

  • Automated tests run when selected without user intervention.
  • Interactive tests are labeled as such and require additional user input for completion.

Use the following steps to choose which tests to run:

For certifications that are associated with an entry on the catalog

  1. Click the Certifications tab, then click the name of the Red Hat product on the line that corresponds with your system or component.
  2. The Certification section of the certification entry should be highlighted when the entry loads.
  3. If it is not,

    1. Click Certification on the left of the page.
    2. Click the Testing tab.
    3. Click the Continue Testing button and skip ahead to Step 3, below, to select tests.

For sandbox certifications

  1. Click the Sandboxes tab, then the name of the Red Hat product on the line that corresponds with your system or component.
  2. Click the Continue Testing button on the Testing tab.
  3. Choose the test(s) you wish to run by selecting the checkbox next to the test(s) and begin the run by clicking the Run Selected button.
Note
  • You can run tests in any order and in any combination.
  • If the test is interactive, you will be prompted for additional information (insert or remove a device, for example) during the test.
  • The tests will run and display their progress on screen.
  • After the run finishes, it will appear in the list of runs and the Continue Testing button will reappear.
  • You can then run additional tests or view the logs from the previous run(s) and submit results.

6.2. Viewing and Submitting the Test Logs for Review

You can see the test runs on the Testing tab of the certification on your LTS. Click on the entries under Run, such as `2017-06-30 12:59:04`to see what tests were performed and whether they passed or failed. Clicking a result will give more detailed information about that run of the test.

To submit results from a run where the certification is associated with the catalog:

  1. Click on the run you wish to submit. Optionally, you can use the drop-down boxes under the Save Assignment column to choose which test plan item that test result will satisfy.
  2. Click the Submit Results button at the bottom of the page to send the results from the displayed run to the Red Hat Certification Catalog.

To submit results from a sandbox run:

  1. Click on the run you wish to submit.
  2. In the Action drop-down box, select Download and download the results file.
  3. Go to Red Hat Certification and open the certification.
  4. Go to the Testing tab and select Upload Results File.

To submit results using CLI:

To submit the test logs using Red Hat Certification CLI, run the `# rhcert-cli submit command on the SUT.

Type your Red Hat account credentials previously enabled for certification 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 operations team. The certification results are displayed on Red Hat Certification web user interface.

If SUT does not have internet access, save the test logs on the SUT using the # rhcert-cli save --server [hostname/IP address of LTS] command. The rhcert-cli save command can also be implemented on the LTS.

6.3. Red Hat Review of Test Results

After you submit your results, the review team will analyze their contents and award credit for each passing test that is part of the test plan.

As they verify each passing test, the team sets each test plan item to Confirmed on the certification site’s test plan, which you can see under the Results tab on the catalog. This allows you to see at a glance which tests are outstanding and which have been verified as passing.

If any problems are found, the review team will update the certification request with a question, which will automatically be emailed to the person who submitted the cert.

You can see all the discussion, and respond to or ask any questions, on the Dialog tab of the certification.

6.4. Completing Certifications

A certification is complete once all the items on the official test plan have been reviewed and found to have passing results. At this point the certification can be closed and published.

After a successful certification, the certified product is listed on Red Hat Certified Cloud Instance Type Page.

Chapter 7. Reference Material

For more information on Red Hat Instance Type Certification, refer the following documents/pages.

Legal Notice

Copyright © 2019 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.