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

DevPrev: Introduce template.kubevirt.io/v1alpha1 APIGroup and VirtualMachineTemplate CRD

XMLWordPrintable

    • virtualmachinetemplate-v1alpha1
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      • Must have an in-cluster (object) representation, and be distinguishable from a VM
      • Must retain the same UX (parameterisation and processing) as OpenShift Templates
      • Must be easy to migrate to from a VirtualMachine defined OpenShift Template
      • Must support creation of VirtualMachines in adjacent namespace to template
      • Must be capable of referencing multiple volumes and networks
      • Must be capable of being created from an existing VirtualMachine
      Show
      Must have an in-cluster (object) representation, and be distinguishable from a VM Must retain the same UX (parameterisation and processing) as OpenShift Templates Must be easy to migrate to from a VirtualMachine defined OpenShift Template Must support creation of VirtualMachines in adjacent namespace to template Must be capable of referencing multiple volumes and networks Must be capable of being created from an existing VirtualMachine
    • None
    • In Progress
    • VIRTSTRAT-529 - InstanceType based templates
    • VIRTSTRAT-529InstanceType based templates
    • 50% To Do, 0% In Progress, 50% Done
    • dev-ready, doc-ready, po-ready, qe-ready, ux-ready
    • Release Note Not Required
    • No

      Goal

      Virtual Machine templates are traditionally pre-configured virtual machines that serve as blueprints for creating new VMs. They encapsulate the operating system, installed software, and configuration settings, allowing for the rapid and consistent deployment of virtual machines. Using templates streamlines the VM creation process, reduces errors, and ensures uniformity across the virtualized environment.

      User Stories

      • As a VirtualMachine owner I would like to create a VirtualMachine from a native in-cluster template that
        • can be hosted in a separate namespace
        • tracks a periodically updated golden image
        • was originally created from a VirtualMachine that had customisation
      • As a VirtualMachine owner I would like to share my native in-cluster templates between namespaces I control

      Non-Requirements

      • List of things not included in this epic, to alleviate any doubt raised during the grooming process.
      • Sealing / generalizing existing VMs before creating a template from them.
      • As a VirtualMachine owner I would like to import and export my native in-cluster templates between clusters into namespaces that I control

      Notes

      • Any additional details or decisions made/needed
      • This feature will be Dev Preview in 4.21
      • Deployment will be a manual process in 4.21

              fmatousc@redhat.com Felix Matouschek
              rhn-support-lyarwood Lee Yarwood
              Geetika Kapoor Geetika Kapoor
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: