Containerized Data Importer (CDI) on OpenShift Virtualization Training

Introduction

Mon, 01 Jan 0001 00:00:00 +0000

The Containerized Data Importer Project¹ is an independently installed Operator. It is primarily used to provide a declarative way to build Virtual Machine Disks on PVCs for OpenShift Virtualization VMs. The CDI Operator provides the custom resource DataVolume which is an abstraction above the PVC.

CDI Operator components

Note

The Operator has already been installed in namespace cdi. If you want to deploy the Operator, check the Deploy section of the CDI documentation.

You may see the CDI Operator components with:

Create a DataVolume

Mon, 01 Jan 0001 00:00:00 +0000

Provisioning a Virtual Machine Disk

In the following lab, we will provision a disk from a given url. We will use a DataVolume to create the Disk. We then create a VM with the disk attached.

We want to provision a VM running an Alpine Cloud Image¹.

Task 2.2.1: Write your own DataVolume manifest

Create a file dv_lab02-alpinedisk.yaml in folder labs/lab02and start with the content from the previous section:

apiVersion: cdi.kubevirt.io/v1beta1
kind: DataVolume
metadata:
 name: lab02-blankdv
spec:
 source:
 blank: {}
 contentType: "kubevirt"
 storage:
 accessModes:
 - ReadWriteOnce
 resources:
 requests:
 storage: 64Mi

Now adapt your DataVolume to fulfill the following specifications:

Using the Alpine disk

Mon, 01 Jan 0001 00:00:00 +0000

In the previous section we have provisioned a custom Alpine cloud disk image. We will now create a VM which uses this disk image.

Task 2.3.1: Attach the disk

Write a new VirtualMachine manifest named lab02-alpine.yaml in the directory labs/lab02.

Note

This Alpine Cloud Image has cloud-init included. We will need another disk (cloudinitdisk) which configures our environment. We will look into cloud-init in a later section. For now, just use the cloudinitdisk specification from the snippet below.

Block needed to reference the PVC as a disk and the cloudinitdisk: