naming_convention.md

StorPool naming convention

Addon version

The addon has the folloing versioning schema YY.MM.R where YY is the year of the release, MM is the month of the release and R is the revision in the month.

Datastore templates

Each Datastore in Opennebula has a StorPool template with the following format

${ONE_PX}-ds-${DATASTORE_ID}

Images

PERSISTENT images

Each persistent image registered in a StorPool backed IMAGE datastore is mapped to StorPool volume

${ONE_PX}-img-${IMAGE_ID}

Non-PERSISTENT images

The non-persistent images are clones of a image registered in the IMAGE datastore mapped to StorPool volume

${ONE_PX}-img-${IMAGE_ID}-${VM_ID}-${VMDISK_ID}

CDROM images

The images of type CDROM are created like non-persistent images - cloned volumes with additional StorPool tag type=CDROM

${ONE_PX}-img-${IMAGE_ID}-${VM_ID}-${VMDISK_ID}

VOLATILE images

The volatile images are registered in the StorPool backed SYSTEM datastore as a StorPool volume

${ONE_PX}-sys-${VM_ID}-${VMDISK_ID}-raw

CONTEXTUALIZATION images

Each contextualization image registered in a StorPool backed SYSTEM datastore is mapped to StorPool volume

${ONE_PX}-sys-${VM_ID}-${VMDISK_ID}-iso

CHECKPOINT images

When the addon is configured in qemu-kvm-ev backed flavour (SP_CHECKPOINT_BD=1) The VM's checkpoint file is a StorPool volume

${ONE_PX}-sys-${VM_ID}-rawcheckpoint

When the default qemu-kvm package is used the StorPool volume holding the archive of the checkpoint file has following name

${ONE_PX}-sys-${VM_ID}-checkpoint

Staging images

In the process of importing of an image to a StorPool backed IMAGE datastore the source is stored temporary on a StorPool volume name suffixed with the md5sum of it's name

${ONE_PX}-img-${IMAGE_ID}-${MD5SUM}

Snapshots

Disk snapshot

${VOLUME_NAME}-snap${SNAP_ID}

VM snapshot

${VOLUME_NAME}-ONESNAP-${VMSNAPSHOT_ID}-${UNIX_TIMESTAMP}

NVRAM

${ONE_PX}-sys-${VM_ID}-NVRAM