Uploaded image for project: 'Virtualization Strategy'
  1. Virtualization Strategy
  2. VIRTSTRAT-509

Declarative and consistent storage hotplug API

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • CNV v4.22.0
    • None
    • Storage Platform
    • None
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • 33% To Do, 0% In Progress, 67% Done

      Feature Overview

      Declarative disk hotplug has now been delivered into kubevirt but it is behind a feature gate: DeclarativeHotplugVolumes which is off-by default. Currently, the UI and virtctl use the old sub-resource API to perform disk hotplug operations. Once DeclarativeHotplugVolumes is on by default we want to use that API everywhere in favor of the old sub-resource API.

      Goals
      Provide high-level goal statement, providing user context and expected user outcome(s) for this Initiative

      • ArgoCD customers benefit from declarative hotplug
      • Any guest sided automation beneifts from the consistent device names

      Requirements

      Requirement Notes isMvp?
           
           
           
           
           

      (Optional) Use Cases

      How will the user interact with this feature? 
      Which users will use this and when will they use it?

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

      <your text here>
      Questions to answer...

      Out of Scope

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

      <your text here>
      **

      Background, and strategic fit

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

      <your text here>

      Assumptions

      • <your text here>

       

      Customer Considerations

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

      <your text here>

       

      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.

      <your text here>

       

              alitke@redhat.com Adam Litke
              fdeutsch@redhat.com Fabian Deutsch
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: