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

LVM Storage support advanced LVM config and usage

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • LVMS
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-16OpenShift - Kubernetes and Core Platform
    • 0
    • 0% 0%
    • 0
    • 0

      Feature Overview (aka. Goal Summary)  

      LVM Storage is using RHEL LVM has backend. LVM has a long history and provides a lot of more complex features (e.g. software RAID, different block sizes etc). Currently, only very basic LVM (single/multiple disks) can be used. This feature enables customers to use more avanced configuration and settings of LVM. 

      Goals (aka. expected user outcomes)

      Provide ways to configure advanced LVM features like software raid etc. We will test and create some prescribed / opionated configurations that are tested by LVMS QE. All other configurations are "use at your own risk" / "comercially reasonably supported". 

      The prescribed configurations are:

      • Software RAID5 3 disk devices (to provide protection against single disk outage) 
      • ...

      Requirements (aka. Acceptance Criteria):

      Provide access to LVM options, e.g. using the already exisitng "lvmcreate-options" field from the lvmd.yaml, which is currently not exposed to the CRD.

       

       

      Questions to Answer (Optional):

      Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

       

      Out of Scope

      Configuring options on individual PVC level. All options are on CRD / Storage Class level, not on individal PVCs. 

      Background

      Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

       

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

       

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

       

      Interoperability Considerations

      Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

            dfroehli42rh Daniel Fröhlich
            dfroehli42rh Daniel Fröhlich
            Gregory Giguashvili
            Suleyman Akbas Suleyman Akbas
            Mike Fiedler Mike Fiedler
            Daniel Macpherson Daniel Macpherson
            Chad Scribner Chad Scribner
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: