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

Support vsphere in-tree migrated volume resize

XMLWordPrintable

    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • 50% To Do, 50% In Progress, 0% Done
    • XS
    • 0

      Feature Overview (aka. Goal Summary)  

      An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

      Currently vsphere migrated in-tree PVs cannot be resized. It was a VMware limitation that they resolved. The goal of this epic is to enable resized in OCP.

      Goals (aka. expected user outcomes)

      The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

      Customers who upgraded OCP and have CSI migration enabled want to benefit from VMware improvements.

      Test and document in-tree vsphere volume resize

      Requirements (aka. Acceptance Criteria):

      A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

      Resize in-tree volumes pass CI

       

      Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

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

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

      1. As an OCP user, I want to resized an in-tree PV that has been migrated to CSI.

      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.

      None, should not require operator changes

      Out of Scope

      High-level list of items that are out of scope.  Initial completion during Refinement status.

      Limited to what is delivered by vmware

      Background

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

      Resizing in-tree migrated volumes were limited in terms of resize, vmware added support in their driver, we need to align by testing and documenting this feature.;

      Customer Considerations

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

      Only applies to vsphere customers who went through CSI migration.

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

      Remove resize limitation for in-tree and document how to update the thin storage class.

      Interoperability Considerations

      Which other projects, including ROSA/OSD/ARO, 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.

      vsphere only

              rh-gs-gcharot Gregory Charot
              rh-gs-gcharot Gregory Charot
              Hemant Kumar Hemant Kumar
              Wei Duan Wei Duan
              Lisa Pettyjohn Lisa Pettyjohn
              Hemant Kumar Hemant Kumar
              Gregory Charot Gregory Charot
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: