Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-2413

Running (tempest) tests on NextGen

XMLWordPrintable

    • Running (tempest) tests on NextGen
    • False
    • Hide

      None

      Show
      None
    • False
    • Committed
    • No Docs Impact
    • In Progress
    • test-operator-bundle-container-1.0.0-17
    • Committed
    • Committed
    • 0% To Do, 0% In Progress, 100% Done
    • Hide

      RHOSO18Beta waived:CI: tempest

      Show
      RHOSO18Beta waived: CI : tempest
    • Automated
    • 2023Q4
    • Tempest

      In order to run tests on NextGen, all test frameworks need to be at least containerized - have an image. Tempest already has one. It makes sense that the tempest plugins are part of that image as they are basically 'test batteries', in other words, they require tempest to run them. In case of other testing frameworks, right now Tobiko and Rally are in question, they should have their own image and thus an own container they'll be running from.

      There are practically 3 ways how to execute tests:

      1. directly via podman - podman run
      2. a pod definition - oc create -f <pod definition>
      3. an operator - the most complex option

      Tempest container is rebuilt every day (based on the tag in RDO Antelope) using TCIB - the container definition here.

      The test-operator is basically a hello world for a tempest's operator we may work on later -> tracked here

      Questions:

      • how are we gonna run QA tooling (tempest, python-tempestconf) there?
        • via a container -> in an operator, in a pod or directly via Podman -> all ways documented here: https://openstack-k8s-operators.github.io/test-operator/index.html
        • does python-tempestconf need a standalone container?
          • we run it only if we plan to run tempest, so it's ok if tempestconf is a part of tempest container, however, it would be good if we could run only tempestconf (without tempest)
      • what existing tests from tempest and plugins can be reused/effectively run
      • do we need new tests? if so, where? tempest? plugins? new plugin?

       

      Steps to prepare an env:

      1. Install RHEL9.2
      2. Follow https://ci-framework.readthedocs.io/en/latest/quickstart/04_non-virt.html (https://issues.redhat.com/browse/OSP-27157)

       

      DoD

      • we are able to run Tempest with tempest plugins on OSP 18
      • all issues encountered while running Tempest on OSP 18 are recorded (Jira, BZs ...) and linked from here (this epic)
      • all child issues are addressed (completed, closed or moved elsewhere)
         

      Useful links:

      Steps to run Tempest on OpenShift doc

      https://quay.io/repository/tripleozedcentos9/openstack-tempest
      https://opendev.org/openstack/tripleo-common/src/branch/master/container-images/tcib/base/os/tempest/tempest.yaml <- probably superseded by https://github.com/openstack-k8s-operators/tcib/tree/main/container-images/tcib/base/os/tempest

      https://github.com/openstack-k8s-operators/osp-director-operator

      https://github.com/openstack-k8s-operators/install_yamls

      https://github.com/openstack-k8s-operators/osp-director-dev-tools/blob/master/ansible/templates/tempest/tempest_script.sh.j2

      NextGen QE Q2 Notes:

      https://docs.google.com/document/d/1r7mQHtlfACMBplw9ZXlTKMmyS5vgX7R5kDff54LIQx4/edit

      NextGen Dev Preview Doc:
      https://docs.google.com/document/d/11sTRxeMMBlSZJ2VSfd8etXoKATWuqVWZyI6vm1EzN_k/edit#heading=h.x61jav3yvsxv

            kopecmartin Martin Kopec
            kopecmartin Martin Kopec
            rhos-tempest
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: