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

Red Hat OpenStack 18.0 Basic Scale Tests

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Committed
    • ?
    • 33% To Do, 33% In Progress, 33% Done
    • PerfScale Sprint 94, PerfScale Sprint 95, PerfScale Sprint 96, PerfScale Sprint 97, PerfScale Sprint 98, PerfScale Sprint 99, PerfScale Sprint 100, PerfScale Sprint 101, PerfScale Sprint 102, PerfScale Sprint 103, PerfScale Sprint 104

      Feature Overview
      The changes of architecture of the next generation of RHOSO 18 will require to a new paradigm of testing OSP scalability.

      Goals
      The goal of this feature is to ensure that RHOSO 18 can handle increasing workload and user traffic as the system grows, without compromising its performance or stability.

      Requirements
      If an MVP gets shifted, the feature shifts. If a non MVP requirement slips, it does not shift the feature.

      Requirements Notes isMvp?
      250+ compute node Scale testing in OCP 4.14   Yes
      250+ compute nodes of RHOSP 17.1 to RHOSP 18 adoption   Yes
      300 Worker node Shift-on-Stack Scale testing   Yes
           

      Out of Scope
      Any scale test with OpenShift related products like RHACS and RHACM

      Documentation Considerations

      This feature would have an impact of new content about how to improve Scalability by sharding the Podified control plane.

      Interoperability Considerations

      OpenShift interoperatibility with OpenShift EUS versions 4.14 and 4.16 should be considered

      Questions

      Question Outcome
         
         

              rhn-support-jraju Jaison Raju
              pnavarro@redhat.com Pedro Navarro Perez
              rhos-dfg-perfscale
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: