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

TP: LiveUpdate VM roll-out strategy support for instance types and preferences

XMLWordPrintable

    • cnv-instancetypes-hotplug
    • Hide
      • MUST allow references to an instance type and/or preference to be updated when using the LiveUpdate VMRolloutStrategy feature
      • MUST match the existing LiveUpdate VMRolloutStrategy feature behaviour
      • MUST not require changes to instance types or preferences to enable
      • MUST have tier 1 functional tests
      • MUST have a design
      Show
      MUST allow references to an instance type and/or preference to be updated when using the LiveUpdate VMRolloutStrategy feature MUST match the existing LiveUpdate VMRolloutStrategy feature behaviour MUST not require changes to instance types or preferences to enable MUST have tier 1 functional tests MUST have a design
    • Green
    • To Do
    • 0% To Do, 0% In Progress, 100% Done
    • dev-ready, doc-ready, po-ready, qe-ready, ux-ready
    • Hide

      doc pending
      Roni Kishner please raise your voice if you have doubts about the green state...

      Show
      doc pending Roni Kishner please raise your voice if you have doubts about the green state...

      Goal

      Currently, VMs defined using instance types do not support the LiveUpdate VMRolloutStrategy feature. Any attempt to modify a running VM referencing an instance type with the LiveUpdate VMRolloutStrategy feature enabled will be rejected.

      The goal of this epic is to extend the LiveUpdate VMRolloutStrategy feature to allow for the instance type or preference of a running VM to be modified and where possible have the resulting resource changes propagated down to the running VMI and guest.

      For example, a running VM using the u1.medium (1vCPU (socket by default) and 1Gi RAM) common instance type could be updated to reference the u1.large (2vCPU (socket by default) and 4Gi RAM) common instance type.

      This should result in an additional socket  and RAM being plugged into the running VMI/Guest.

      User Stories

      • As a VM owner, I want to change the instance type and/or preference associated with my running VM and where possible have updates propagated to the running guest

      Non-Requirements

      • Additional LiveUpdate VMRolloutStrategy support for attributes of an instance type or preference not already supported in a vanilla VirtualMachine. For example, GPUs, Host devices, NUMA etc
      • No UI/UX updates are required for this TP version of the epic

      Notes

          1.
          		 upstream roadmap issue Sub-task Closed Normal Unassigned
          2.
          		 upstream documentation 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 in polarion Sub-task Closed Normal Unassigned
          6.
          		 automated tests Sub-task Closed Normal Unassigned
          7.
          		 downstream documentation merged Sub-task Closed Normal Unassigned

              rhn-support-lyarwood Lee Yarwood
              unassigned_jira Unassigned
              Roni Kishner Roni Kishner
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: