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

MicroLVMS - LVMS / TopoLVM Controller Consolidation

XMLWordPrintable

    • MicroLVMS - LVMS / TopoLVM Controller Consolidation
    • Product / Portfolio Work
    • OCPSTRAT-1023LVM Storage resource footprint reduction
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • L

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      Why is this important?

      • Having reduced resource footprint for Edge customers that are not having as much room in their k8s installations as most kubernetes distributions is important for LVMS usability
      • Red Hat can now offer a native Dynamic Provisioning Local Storage Provider with a minimal footprint that sets it apart from other Providers.
      • LVMS can now be the goto Local Storage Provider for Edge, especially for small form factor SNO deployments.
      • MicroShift can save resources AND gain features from switching to LVMS instead of pure TopoLVM by using our optimizations for Red Hat Device Edge.
      • The Telco RAN Reference Specification can consider LVMS an alternative to LSO without compromising on resources, allowing it to run in the Management CoreSet, freeing up resources for customers.

      Scenarios

      1. Microshift is run with TopoLVM Midstream via existing lvmd.conf file and needs to have all previous functionality of TopoLVM while consuming less resources at idle or under stress
      2. While LVMS is already migrated to a minifed version for SNO/MNO customers for 4.16, Microshift still needs to work with the previous version of non-modified TopoLVM to ensure its compatibility guarantees

      Acceptance Criteria

      • Container Count reduction
        • 1 Deployment (2 before)
        • 1 DaemonSet (2 before)
        • 2 Containers (11 before)
        • 4 Services (5 before)
      • CPU / Memory reduction
      • Image count/ size reduction
        • Total Image Size <100 Mi
        • Total Image Count 1
      • Fully upgradeable via CSV Subscription
      • Not breaking any APIs
      • Fully compatible with previous versions of LVMS
      • No disabled Controllers or otherwise critical functionality

      Dependencies (internal and external)

      Previous Work (Optional):

      1. https://issues.redhat.com/browse/OCPEDGE-662 - Investigate MicroLVMS Compatibility with Microshift and propose Migration Scenarios

      Open questions:

      1.  

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              rh-ee-jmoller Jakob Moeller (Inactive)
              rh-ee-jmoller Jakob Moeller (Inactive)
              Jakob Moeller (Inactive), Suleyman Akbas
              Rahul Deore Rahul Deore
              Daniel Macpherson Daniel Macpherson
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: