Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-1408

RHODS Quality Gate: Performance Testing

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • RHODS Quality Gate: Performance Testing
    • False
    • False
    • RHODS-7450ods-ci library and infrastructure
    • No
    • To Do
    • RHODS-7450 - ods-ci library and infrastructure
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined
    • No
    • Pending
    • None

      Created this epic as a placeholder for discussing on how are we going to perform performance tests for rhods.

      Captured few points based on Discussion of Continuous Performance Testing in QE extended Staff meeing:

      1. Perf team uses framework called CPT(continuous performance testing) to automate and execute the perf tests.
      2. For now, perf team executes tests in CPT with minimum workload that gets completed in 3 hours. 
      3. CPT compares the results across releases and also they have pass criteria for each execution based on threshold criteria.
      4. CPT monitors kafka disk usage, uses prometheus end point to collect data.
      5. CPT is been used by teams suchAnsible tower, Satellite, RH Cloud.
      6. They have not added any managed services yet other than subscription watch team, but they are are okay to collaborate with respective qe teams to use CPT.
      7. RH Cloud CPT uses Openshift dedicated AWS EC2 performance clusters.
      8. Openstack performance CI also uses CPT.
      9. Openshift performance and Scale CI covers components such as Networking, Router, Kubelet, etc.,

      We should explore on how we can utilize CPT for our team to do rhods performance testing.

       

              Unassigned Unassigned
              rhn-aloganat Arthy Loganathan
              Sweta Anandpara Sweta Anandpara
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: