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

Flatten VM definitions when creating from InstanceType

XMLWordPrintable

    • cnv-instancetype-referencePolicy-default-to-expand
    • 77
    • Hide
      • MUST provide cluster configurable to flatten all VMs within a cluster
      • MUST not change the default behaviour of instance types and preferences
      • MUST have tier 1 functional tests
      • MUST be documented as a KCS workaround
      Show
      MUST provide cluster configurable to flatten all VMs within a cluster MUST not change the default behaviour of instance types and preferences MUST have tier 1 functional tests MUST be documented as a KCS workaround
    • To Do
    • 29% To Do, 0% In Progress, 71% Done
    • dev-ready

      Goal

      VMs that are created from IT keeps references to the IT and preferences while VMs that are migrated from other virtualization solutions or created from templates have a single (flat) definition file (yaml). This means that all operations on VMs need to support those two different formats, which adds complexity and is more error prone.

      The goal of this epic is to make sure that when a new VM is created from InstanceType, the definition file of that VM is flattened (has all definitions of the VM) and does not have references definitions in other files (IT and preferences).

      User Stories

      • As a backup / recovery partner I would like to know which files need to be backup and restore when I perform those operations on a VM, regardless if the VMs was created from IT or not
      • As a DR partner I would like to know which files need to be replicated when I replicate a VM, regardless if the VM was created from IT or not
      • As a VM user I would like to have the same customization experience regardless if my VM was created from IT or not

      Non-Requirements

      • List of things not included in this epic, to alleviate any doubt raised during the grooming process.

      Notes

      • How do we handle InstanceType VMs that already exist?

          1.
          		 upstream roadmap issue Sub-task New Normal Unassigned
          2.
          		 upstream design Sub-task New Normal Unassigned
          3.
          		 upstream documentation Sub-task New Normal Unassigned
          4.
          		 upgrade consideration Sub-task New Normal Unassigned
          5.
          		 CEE/PX summary presentation Sub-task New Normal Unassigned
          6.
          		 test plans in polarion Sub-task New Normal Unassigned
          7.
          		 automated tests Sub-task New Normal Unassigned
          8.
          		 downstream documentation merged Sub-task New Normal Unassigned

              rhn-support-lyarwood Lee Yarwood
              rsdeor Ronen Sde-Or
              Geetika Kapoor Geetika Kapoor
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: