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?