Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-49615

TP: OCP Virtualization self-certification package for Cloud providers

XMLWordPrintable

    • cnv-self-certification-tp
    • Product / Portfolio Work
    • 77
    • Hide

      CNV has a simple package(s) that anyone can execute to verify if the cloud platform is ready for CNV and Red Hat will be supporting CNV on that platform.

      Show
      CNV has a simple package(s) that anyone can execute to verify if the cloud platform is ready for CNV and Red Hat will be supporting CNV on that platform.
    • Green
    • Done
    • VIRTSTRAT-499 - OCP Virtualization self-certification package for Cloud providers
    • VIRTSTRAT-499OCP Virtualization self-certification package for Cloud providers
    • 0% To Do, 0% In Progress, 100% Done
    • dev-ready, po-ready, qe-ready, ux-ready
    • Hide

      2025-06-02:
      manual test and kcs article left....

      Show
      2025-06-02: manual test and kcs article left....

      Goal

      Let cloud providers do necessary verification of OpenShift Virtualization on their side, with minimal or no help from Red Hat. The idea is that OCP Virt will provide instructions/requirements/automatic means of verifying whet OCP Virt can generally run in a given cloud.

      The work will most likely be needed on Storage and potentially on Network side.

      User Stories

      • As a CNV Product Manager and Engineering manager, I want to have less load for certifying various clouds on OCP Virt
      • As Cloud provider, I want to have easy way to be able to say that my product is OCP Virt ready/validated.
      • I want to install OpenShift Virtualization, run a command line, wait a while, and receive feedback that it works well on my cloud, or a clear report stating what is missing.
      • If I am a good certified OpenShift administrator, I would not need Red Hat's assistance to run the test or interpret its result.
      • The executed tests should include KubeVirt's Comformace tests, maybe more.

      Non-Requirements

      • List of things not included in this epic, to alleviate any doubt raised during the grooming process.

      Notes

          1.
          upstream roadmap issue Sub-task Closed Normal Unassigned
          2.
          upstream design Sub-task Closed Normal Unassigned
          3.
          upstream documentation Sub-task Closed Normal Unassigned
          4.
          upgrade consideration Sub-task Closed Normal Unassigned
          5.
          CEE/PX summary presentation Sub-task Closed Normal Unassigned
          6.
          test plans in polarion Sub-task Closed Normal Unassigned
          7.
          automated tests Sub-task Closed Normal Unassigned
          8.
          downstream documentation merged Sub-task Closed Normal Unassigned

              kmajcher@redhat.com Krzysztof Majcher
              unassigned_jira Unassigned
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: