Å·²©ÌåÓýƽ̨

With the recent developments in the virtualization space, customers are looking for robust platforms that can run their virtualized workloads. Red Hat® OpenShift® Virtualization is a solution that provides customers with features that lead to faster production times, allow for easier migrations, and streamline operations.

We’re helping our partners quickly test and validate support for their products with our platform. This applies to products that can run in a Red Hat OpenShift cluster as a virtual machine (VM) or provide infrastructure services to virtual machines in a Red Hat OpenShift cluster.

Partners can validate software in 4 steps:

1. Become a Red Hat partner.
2. Validate your product.
3. Document compatibility with Red Hat OpenShift Virtualization. 
4. Publish your product listing in the .

Register for the partner program

If your company is not yet registered with the technology partner program, use  to register. Note that sections “Initial onboardingâ€�, “Managing your accountâ€�, and “Partner benefitsâ€� provide all the information you’ll need to join the program. If your company already has a profile, reach out to your account’s organization administrator and submit a request to join your company’s profile.  If you need assistance, contact the Partner Acceleration Desk, a global team that can troubleshoot issues associated with partner registration.

Validate your product

Verify and test your product’s functionality on Red Hat OpenShift using a Red Hat Partner Subscription(RHPS); you can  if you need guidance setting up your environment. Alternatively, for a limited amount of time, you can request access to a cluster hosted by Red Hat through the OpenShift Partner Lab.

Red Hat does not provide specific test criteria. It is up to partners to determine how to verify the functionality of their product according to their support standards. Performance testing and benchmarks are not considered functional testing for these purposes. Å·²©ÌåÓýƽ̨ goal is to stand up and test the VM to make sure it's working on Red Hat OpenShift in the same way you would see it work in other virtualized environments. 

Documentation

Partners should indicate support for Red Hat OpenShift Virtualization using their standard documentation practices. This is usually captured in a support matrix or product installation guide. Multiple documentation types can be included to better assist customers consulting the Red Hat Ecosystem Catalog. Å·²©ÌåÓýƽ̨y can include:

• Reference architectures
• Blog posts
• User guides
• Videos
• Whitepapers

As required of catalog listings, documentation must be publicly accessible, and you must link to at least 1 document.  We strongly recommend that the documentation cover how a customer would be able  run the VM on Red Hat OpenShift.

Get started!

Once you’ve registered or confirmed your company as a partner, you can access the partner workflow to complete or update your company profile and review the partner agreement.  Details can be found in our .

Å·²©ÌåÓýƽ̨ key areas that are needed for the catalog listing are:

• A product listing 
• Completion of the company profile
• Legal terms and conditions have been signed
• Creation of at least 1 product component

Once you’ve completed the profile and created the product listing, you can start the validation workflow by following in our Red Hat software certification workflow guide.

If your product integrates with Red Hat OpenShift using the container network interface (CNI) or container storage interface (CSI), follow the corresponding certification workflow for or , which incorporates virtualization tests.

If you require assistance with partner registration or have any other general questions on Red Hat OpenShift Virtualization, contact the Partner Acceleration Desk through the “Technical partners� section, log into your account, and submit a support ticket.

Next steps

To ensure a good support experience for our customers, we recommend establishing collaborative support.

If you’d like to learn more about Red Hat OpenShift Virtualization, view our blog which highlights several resources and best practices.