Images
We provide public images of the most common Linux distributions. They are the distributors' own generic cloud images, kept up to date and configured for the best performance on our platform.
Available images
| Image | Login user | Available until |
|---|---|---|
| AlmaLinux 8 | almalinux |
2029-05-31 |
| AlmaLinux 9 | almalinux |
2032-05-31 |
| AlmaLinux 10 | almalinux |
2035-05-31 |
| CentOS Stream 9 | cloud-user |
2027-05-31 |
| CentOS Stream 10 | cloud-user |
2030-05-31 |
| Debian 13 | debian |
2028-08-09 |
| Rocky 8 | rocky |
2029-05-31 |
| Rocky 9 | rocky |
2032-05-31 |
| Rocky 10 | rocky |
2035-05-31 |
| Ubuntu 22.04 | ubuntu |
2027-06-01 |
| Ubuntu 24.04 | ubuntu |
2029-05-31 |
| Ubuntu 26.04 | ubuntu |
2031-05-29 |
Log in over SSH as the login user, with the key pair the server was created
with. The user has passwordless sudo.
An image is available until its distributor's official security support ends,
and is removed from the catalogue after that date. Servers and volumes already
created from it are not affected, but they no longer receive security updates
from the distributor, so plan to migrate them to a newer release in good time.
The date is also published in the image's provided_until property.
Updates
Every day, each image is checked against its distributor, and replaced when the distributor has published a new build. A server created from an image therefore starts out with all updates released up to that point, and only needs the ones published since.
An updated image keeps its name, but gets a new ID. The image it replaces is removed from the catalogue, and can no longer be used to create new servers. Existing servers and volumes created from it are not affected, and a server reprovisioned from the image name gets the current build.
Refer to images by name
Image IDs are not stable. Scripts and automation should look an image up by its name, as in the Terraform / OpenTofu example below.
The date the current build was made by its distributor is published in the
image_build_date property.
Metadata
The images carry the metadata of the
SCS image metadata standard,
such as os_distro, os_version, image_build_date and provided_until.
They also set image properties
that give servers modern virtual hardware:
| Property | Value | Effect |
|---|---|---|
hw_machine_type |
q35 |
Modern PCIe chipset |
hw_firmware_type |
uefi |
UEFI firmware |
hw_disk_bus, hw_scsi_model |
scsi, virtio-scsi |
Disks on a virtio-scsi controller |
hw_cdrom_bus |
scsi |
The config drive on the same virtio-scsi controller |
hw_vif_multiqueue_enabled |
true |
One network queue per vCPU |
hw_rng_model |
virtio |
Hardware random number generator |
hw_watchdog_action |
reset |
A watchdog device that resets a hung server |
hw_qemu_guest_agent |
yes |
A channel for the QEMU guest agent, see below |
min_disk and min_ram are also set, so the web interface suggests a volume
size that fits the image.
QEMU guest agent
With the QEMU guest agent running in the server, the platform can:
- freeze the file systems of a volume-backed server while it is snapshotted;
- set a password with
openstack server set --root-password. Despite the option's name, this sets the password of the image's login user, named in itsos_admin_userproperty.
The agent is installed and enabled in the AlmaLinux, CentOS Stream and Rocky
images. The Debian and Ubuntu images do not include it; install the
qemu-guest-agent package to use it.
Terraform / OpenTofu
Look the image up by name with the openstack_images_image_v2 data source.
Since a new build gets a new ID, tell Terraform/OpenTofu to ignore changes to
the image ID; otherwise every update to the image would make it replace the
server:
data "openstack_images_image_v2" "ubuntu" {
name = "Ubuntu 24.04"
visibility = "public"
most_recent = true
}
resource "openstack_compute_instance_v2" "web" {
name = "web.example.com"
flavor_name = "g4b.medium"
key_pair = "alice"
security_groups = ["remote administration"]
block_device {
uuid = data.openstack_images_image_v2.ubuntu.id
source_type = "image"
destination_type = "volume"
volume_size = 20
boot_index = 0
delete_on_termination = true
}
network {
name = "internal"
}
lifecycle {
ignore_changes = [block_device[0].uuid]
}
}
New servers are created from the image's current build, while existing ones are left as they are.
Private images
You can upload your own images to your project. They are only visible within it.
The platform's defaults for images without these properties are conservative, to support older operating systems. For the best performance, copy the properties under Metadata that your operating system supports from a public image:
Then upload the image with them:
openstack image create --import \
--disk-format qcow2 --container-format bare --file my-image.qcow2 \
--property hw_machine_type=q35 \
--property hw_firmware_type=uefi \
--property hw_disk_bus=scsi \
--property hw_scsi_model=virtio-scsi \
--property hw_cdrom_bus=scsi \
--property hw_vif_multiqueue_enabled=true \
--property hw_rng_model=virtio \
--property hw_qemu_guest_agent=yes \
"My image"
--import converts the image to the format the platform stores images in,
which makes creating volumes from it much faster.
Only set hw_firmware_type=uefi if the image can boot with UEFI, and the
scsi buses if it has the virtio_scsi driver. Properties can also be
changed afterwards, with openstack image set --property.