Skip to content

Public Images

Overview

We provide and maintains a set of images in the OpenStack Cloud. As soon as vendors publish new images, we will verify their origin, test them and publish them automatically. We publish images with intact digital signatures when the vendor provides them. We don't make any changes in vendor images, to keep checksums intact. That allows our customers to verify image origin if needed.

To maintain your own images, upload them yourself. You can use tools like HashiCorp Packer to build custom images, for example with certain preinstalled software.

Available public images

Name Description
Flatcar Stable Flatcar Container Linux. See https://www.flatcar.org/license for license information
Ubuntu Bionic 18.04 (YYYY-MM-DD) Ubuntu Bionic cloud image. See https://canonical.com/legal for license information.
Ubuntu Focal 20.04 (YYYY-MM-DD) Ubuntu Focal cloud image. See https://canonical.com/legal for license information.
Ubuntu Jammy 22.04 (YYYY-MM-DD) Ubuntu Jammy cloud image. See https://canonical.com/legal for license information.
Ubuntu Noble 24.04 (YYYY-MM-DD) Ubuntu Noble cloud image. See https://canonical.com/legal for license information.
Ubuntu Resolute 26.04 (YYYY-MM-DD) Ubuntu Resolute cloud image. See https://canonical.com/legal for license information.
Red Hat CoreOS <version> (YYYY-MM-DD) Red Hat Enterprise Linux CoreOS (RHCOS). We provide the latest 3 versions of RHCOS. Licensing for RHCOS is depending on your Red Hat subscription. See https://www.redhat.com/en/about/eulas or contact you Red Hat partner for details.

Warning

Red Hat does not provide digital signatures for the CoreOS images. We are not able to verify the authenticity.

Public image lifecycle

As soon as we upload a new version of an operating system image (recognizable by the current date in their name), we will change the visibility of the old image version:

  • If you are using an old public image, the image will stay visible within the project that is using it until you stop using it
  • If you are not using an old public image anymore, the image will become invisible for you after some time.
  • If a public image falls out of use across all customers, we will remove it

Public image properties

Public images get certain properties that you can use for finding the latest images for example with Packer or Terraform.

Property name Description
default_ssh_username If not configured otherwise using cloud-init, servers using this image can be accessed with this SSH username. Same as image_original_user
distribution Unique identifier for the distribution and version (for example, ubuntu-focal)
image_description URL to the vendor's image repository notes
image_source URL to the vendor image file that has been used for this image. Same as source_url
image_build_date Date when the image was added to the catalog
image_original_user If not configured otherwise using cloud-init, servers using this image can be accessed with this SSH username. Same as default_ssh_username
os_distro Name of the distribution (for example, ubuntu)
os_version Version of the operating system (for example, 24.04)
provided_until The date until when the image will be available and updated
replace_frequency How often the image will be replaced with an updated version
source_sha512sum SHA512 hash of the original image file, as provided by the vendor under source_url
source_sha256sum SHA256 hash of the original image file, as provided by the vendor under source_url
source_url URL to the vendor image file that has been used for this image. Same as image_source

We follow the SCS Image Metadata Standard Here is an example for filtering the images by properties using HashiCorp Terraform's image data source:

Example:

data "openstack_images_image_v2" "ubuntu-noble" {
  most_recent = true
  properties = {
    os_version = "24.04"
    os_distro = "ubuntu"
  }
}