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

Performance evaluation of VM Delete Protection

XMLWordPrintable

    • perf-vm-delete-protection
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      • (must-have) Performance metrics report comparing protected vs. unprotected VMs.
      • (must-have) No significant impact on VM lifecycle operations (<5% latency increase).
      • (should-have) Smooth integration with live migration and scaling processes.
      • (should-have) Resource usage remains within acceptable thresholds.
      • (should-have) Compatibility with existing features like memory overcommit.
      Show
      (must-have) Performance metrics report comparing protected vs. unprotected VMs. (must-have) No significant impact on VM lifecycle operations (<5% latency increase). (should-have) Smooth integration with live migration and scaling processes. (should-have) Resource usage remains within acceptable thresholds. (should-have) Compatibility with existing features like memory overcommit.
    • None
    • To Do
    • CNV-46398"Delete Protection" like in RHEV for OCP CNV
    • ---
    • ---

      Objectives:

      Evaluate the impact of the "Delete Protection" feature on system performance, ensuring minimal latency, resource overhead, and compatibility with key workflows such as VM operations, live migration, and automation processes.

      User Stories:

      1. As a cluster admin, I want to assess the impact of delete protection on system performance to ensure production readiness.
      2. As an engineer, I want to verify live migration performance with delete protection enabled to identify any issues.

      Scope:

      1. Benchmark Performance Impact:

      • Measure VM operation latency (creation, deletion, migration).
      • Assess API response times and resource consumption.

      2. Scalability Testing:

      • Evaluate performance across small, medium, and large clusters.
      • Identify potential bottlenecks in high-scale environments.

      3. Compatibility Analysis:

      • Verify impact on live migration, backups, and auto-scaling.

      4. Resource Utilization Analysis:

      • Monitor CPU, memory, and storage usage with protection enabled/disabled

              rhn-support-sbennert Sarah Bennert
              nrozen@redhat.com Nir Rozen
              Guy Chen
              Nir Rozen Nir Rozen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: