Some OpenStack Images by Kurt Garloff

These images have been prepared by me for convenience to simplify the deployment of OSISM and Jitsi on OTC and other OpenStack clouds.

Use the sha256 sums to validate the integrity of the download and check the cryptographic signature that I have added with my GnuPG key 2bffc5bf:

pub   rsa4096 2014-07-22 [SC] [expires: 2026-07-19]
      6669 F734 0D31 E95E C556  5490 DE4F 1B3A 2BFF C5BF
      uid           [ultimate] Kurt Garloff <>

Register the openSUSE image with

openstack image create \
	--file "openSUSE-15.6-JeOS.x86_64-" \
	--disk-format qcow2 --min-disk 5 --min-ram 512 --property architecture="x86_64" \
	--property image_build_date="2024-07-03" --property image_original_user="linux" \
	--property os_distro="openSUSE" --property os_version="15.6" \
	--property hw_disk_bus=scsi --property hw_scsi_model=virtio-scsi --property hw_rng_model=virtio \
	--property image_source="" \
	--property image_description="" \
	--tag os:opensuse --tag path:os:linux:opensuse --tag managed_by_$LOGNAME \
	--property uuid_validity=last-3 --property provided_until=2025-07-02 --property replace_frequency=monthly \
	"openSUSE 15.6"
With this, you would promise to do at least monthly updates until beginning of July of 2025 and leave the old images accessible by uuid (for the last 3 versions -- but likely under a different name or hidden).
On OTC, you need to add --property __os_version="OpenSUSE 15.1 64bit" --property __support_kvm=true. For the Ubuntu image for OSISM, on OTC, you would use --min-disk 30 --property __os_version="Ubuntu 18.04 server 64bit" --property __suport_kvm="true" and of course adjust filename and image name. You can lower the min-disk property down to 4(GiB) if you like. For clouds with ceph backend storage, registering raw images may be preferrable, as you can use copy-on-write for image deployment which saves time and storage space. You could use qemu-img convert -S4k -Oraw openSUSE-15.6-JeOS.x86_64- openSUSE-15.6-JeOS.x86_64- to convert and then replace --disk-format and --file in above call with raw.
See the SCS image metadata spec for recommended image metadata.

Actually, I have created a little script that I use for image registration. You may find it handy ...

These are provided without any warranties, use at your own risk. Contact me in case of questions or feedback.