104 - Image

It's not all about Image

Read the Docs

If you want to get a better idea about the object that we will be working with in this module, you can review the docs here:

• Image

Objectives

In this module we'll describe how to find VM images that can be used to create your VM(s). The images are a property of your deployment region so we'll demonstrate how to find out which images are available in your chosen region, and how to use them within a Tuono Blueprint.

Image Terminology

AWS

Amazon Machine Image (AMI)

An AMI is an image format used for all Amazon VMs. They can be public, and derived from GA releases of your chosen operating system. For example, an Ubuntu 20.04 direct from Canonical, cognate with the downloadable ISO. They can also be private, and created by you as a user. For example, it might contain certain configurations and/or software required internally within your company.

Azure

Virtual Machine Image (VMI)

An Virtual Machine Image is used for all Azure VMs. They can be public, and derived from GA releases of your chosen operating system. For example, an Ubuntu 20.04 direct from Canonical, cognate with the downloadable ISO. They can also be private, and created by you as a user. For example, it might contain certain configurations and/or software required internally within your company.

Image Concepts

Image Schema

This is where we define the exact image that we want to use for our VM. In a single object we define the publisher, product and SKU - this is how Azure references their VMs. Similarly, we define the image_id, which points directly to the AMI that we wish to use for AWS. This means that we can deploy this to each venue, while still leveraging venue-native concepts.

  image:
    bionic:
      publisher: Canonical
      product: UbuntuServer
      sku: 18.04-LTS
      venue:
        aws:
          image_id: ami-04bb0cc469b2b81cc