Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-1463

Add multipath SAN support to LVMS (DevPreview)

XMLWordPrintable

    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-1462Unblock OCP Virt SAN customers by adding multipath SAN support to LVMS
    • 33% To Do, 67% In Progress, 0% Done
    • XL
    • 0

      Feature Overview (aka. Goal Summary)  

      Allow Datacenter customers to leverage existing SAN infrastructure with OCP Virt with dynamic provisioning and live migration.  

      Goals (aka. expected user outcomes)

      As Data Center OCP admin, I can add my existing expensive SAN infrastructure to OCP nodes to host VM workloads, so that I can better migration VMs from vSphere to OCP Virt.

      The goal of Dev Preview release is to to provide MVP functions with limited docs, to get early feedback from customers. 

      Requirements (aka. Acceptance Criteria):

      General: 

      • Allow Datacenter customers to leverage existing SAN infrastructure with OCP Virt
      • Support multiple VMs (virtual disks) out of a single LUN with dynamic provisioning for end-user self service with high level of isolation 
      • Support live migration of VMs (--> RWX)

      MVP Scope:

      • 1 LUN per VG
      • many VMs per VG
      • VM can have multiple PV, but they must all be on the same VG (== StorageClass)
      • No multi-path
      • LiveMigration of a single VM from one node to another (RWX)
      • Snapshots/Cloning/ReSizing (CSI conformity >=V1.5)
      • Integration of kubesan as additional backend parallel to topolvm into LVMs

       

      Deployment considerations List applicable specific needs (N/A = not applicable)
      Self-managed, managed, or both both
      Classic (standalone cluster) yes
      Hosted control planes yes (using LVMs as storage for etcd), no special needs 
      Multi node, Compact (three node), or Single node (SNO), or all all
      Connected / Restricted Network yes 
      Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) x86 and Arm
      Operator compatibility yes
      Backport needed (list applicable versions) no
      UI need (e.g. OpenShift Console, dynamic plugin, OCM) no
      Other (please specify)  

      Questions to Answer (Optional):

      1. HW for CI testing - AWS? ReUse from RHV team?

      Out of Scope

      • Full fledge CI, DevPreview has minimum CI testing
      • multi-path SAN (–> TechPreview scope)
      • Thin pool only (Thick pool maybe later)
      • other kubesan backends then SAN-LUN  (NFS, etc)

      Background

      See Integrate KubeSAN into LVMS to unblock OCP Virt SAN customers 

      Customer Considerations

      See Integrate KubeSAN into LVMS to unblock OCP Virt SAN customers 

      Documentation Considerations

      1. Docs needs to be added to the existing LVMS docs which might need a refactoring to allow for the two different backend types (LVM and SAN).  
      2. Constraints and Limitations / OutOfScope needs to be clearly documented

      Interoperability Considerations

      1. OCP Virt
      2. Hosted Control Plane

            dfroehli42rh Daniel Fröhlich
            dfroehli42rh Daniel Fröhlich
            Martin Tessun, Peter Lauterbach
            Bulat Zamalutdinov Bulat Zamalutdinov
            Jeremy Peterson Jeremy Peterson
            Bulat Zamalutdinov Bulat Zamalutdinov
            Daniel Fröhlich Daniel Fröhlich
            Votes:
            1 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated: