Uploaded image for project: 'OpenShift Edge Enablement'
  1. OpenShift Edge Enablement
  2. OCPEDGE-14

Reduce LVMS resource footprint and refine runtime topology

XMLWordPrintable

    • Reduce LVMS resource footprint and refine runtime topology
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • None

      Telco is targeting to replace LSO with LVMS but the resource requirements are too high for Single-Node OpenShift (SNO). The goal of this epic is to reduce the overall footprint of LVMS so it can replace LSO on SNO.

      LVMO
      - aggregate cpu requests - 580 mc
      - 4 pods
      - 13 containers
      - 5 probes
      - 5 services
      - 10 secrets 
      
      LSO
      - aggregate cpu requests - 6 mc (best effort)
      - 2 pods
      - 3 containers
      - 0 probes
      - 1 service
      - 7 secrets  

       

      High Level Requirements:

      • Resource Reduction
        • Remove CPU limits from all containers
        • Reduce the CPU requests for all the pods. From our testing, looks all pods with the exception of topolvm-node could be as low as 2m with topolvm-node at 10m
      • Topology Reduction
        • Reduce pod footprint to 2, one controller, one daemonset - not possible with the current architecture
        • Reduce the number of containers, max 6 - not possible with the current architecture
        • Provide an option to disable snapshotting, it could be an optional container
        • Add workload partitioning annotation to the pods so that we can use workload partitioning
      • Container Image size Reduction
        • For the remaining container images, take a pass to reduce image sizes, to reduce pull time and increase initial startup after install/updates.
        •  
      •  

              sakbas@redhat.com Suleyman Akbas
              rhn-support-cscribne Chad Scribner
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: