Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-36354

Implement VMRolloutStrategy as a means of updating VMs

XMLWordPrintable

    • rollout-strategy
    • Hide
      • MUST Remove LiveUpdateFeatures field. It is currently still protected by FeatureGate.
      • MUST Add cluster level VMRolloutStrategy setting
      • MUST Add RestartRequired condition to VMIs to be present if a non-liveupdateable change was performed to the VM
      • MUST be a declarative API
      • MUST GA the upstream feature
      • MUST a description of the VM rollout strategy concept in the developer and user-guide
      • MUST have a design
      Show
      MUST Remove LiveUpdateFeatures field. It is currently still protected by FeatureGate. MUST Add cluster level VMRolloutStrategy setting MUST Add RestartRequired condition to VMIs to be present if a non-liveupdateable change was performed to the VM MUST be a declarative API MUST GA the upstream feature MUST a description of the VM rollout strategy concept in the developer and user-guide MUST have a design
    • Green
    • To Do
    • CNV-33617 - Dynamic VM reconfiguration
    • CNV-33617Dynamic VM reconfiguration
    • 0% To Do, 0% In Progress, 100% Done
    • dev-ready, doc-ready, po-ready, qe-ready, ux-ready
    • Hide

      Testing is Done....

      Show
      Testing is Done....

      Goal

      Currently, VMs are updated by using the LiveUpdateFeatures field, this leads to an inconsistent and confusing API. This epic is about retiring that field and instead implementing VMRolloutStrategy at the cluster level.

      User Stories

      • As a cluster admin, I would like to be able to control how changes to user's workloads are propagated so that they don't need to worry about such details.
      • As a workload owner, I would like declarative changes I make to a VM to be propagated without having to restart so that my workloads are not interrupted.

      Non-Requirements

      • This is not about propagating every change to the VM without restart--this is about specific fields.

      Notes

          1.
          		 upstream roadmap issue Sub-task Closed Normal Unassigned
          2.
          		 upstream documentation for VMRolloutStrategy Sub-task Closed Normal Unassigned
          3.
          		 upgrade consideration Sub-task Closed Normal Unassigned
          4.
          		 CEE/PX summary presentation Sub-task Closed Normal Unassigned
          5.
          		 Test Plans covering VMRolloutStrategy Sub-task Closed Normal Kedar Bidarkar
          6.
          		 automated tests Sub-task Closed Normal Unassigned
          7.
          		 Design document detailing VMRolloutStrategy Sub-task Closed Undefined Unassigned
          8.
          		 downstream documentation merged Sub-task Closed Undefined Unassigned

              jelejosne Jed Lejosne
              sgott@redhat.com Stuart Gott
              Vasiliy Sibirskiy Vasiliy Sibirskiy
              Sabrina Jess Sabrina Jess
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: