Linux Virtualization Naming Conventions: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 9: Line 9:
=Virtual Machine Image Naming Convention=
=Virtual Machine Image Naming Convention=


The ... that will hold a [[Linux_Virtualization_Concepts#Virtual_Machine_Image|virtual machine image]] should follow the pattern:
The main volume of virtual machine, which contains the [[Linux_Virtualization_Concepts#Virtual_Machine_Image|virtual machine image]] should follow the pattern:


<pre>
<font size=-2>
<vm-name>.<image-format>
<vm-name>.<image-format>
</pre>
</font>


Example:
Example:


<pre>
<font size=-2>
node1.qcow2
gp.qcow2
</pre>
</font>


=Storage Volume Naming Convention=
=Storage Volume Naming Convention=
Line 25: Line 25:
If the volume will be used for raw storage under a filesystem, and it is NOT going to be a [[Linux_Virtualization_Concepts#Virtual_Machine_Image|virtual machine image]], the volume name should follow the pattern:
If the volume will be used for raw storage under a filesystem, and it is NOT going to be a [[Linux_Virtualization_Concepts#Virtual_Machine_Image|virtual machine image]], the volume name should follow the pattern:


<pre>
<font size=-2>
<vm-name|generic-name>-<purpose>.<image-format>
<vm-name|generic-name>-<purpose>.<image-format>
</pre>
</font>


Example:
Example:


<font size=-2>
  node1-docker.raw
  node1-docker.raw
  support-nfs.raw
  support-nfs.raw
</font>


=Disk Image Snapshot Tag Naming Conventions=
=Disk Image Snapshot Tag Naming Conventions=

Latest revision as of 00:27, 30 July 2023

Internal

Virtual Machine Naming Convention

For more details about the virtual machine name, see

KVM Virtual Machine Definition 'name'

Virtual Machine Image Naming Convention

The main volume of virtual machine, which contains the virtual machine image should follow the pattern:

<vm-name>.<image-format>

Example:

gp.qcow2

Storage Volume Naming Convention

If the volume will be used for raw storage under a filesystem, and it is NOT going to be a virtual machine image, the volume name should follow the pattern:

<vm-name|generic-name>-<purpose>.<image-format>

Example:

node1-docker.raw
support-nfs.raw

Disk Image Snapshot Tag Naming Conventions

Use a name that describe the state the snapshot is intended to preserve, and replace space with '_'. Example:

before_OpenShift_installation

More about disk image snapshots is available here:

Disk Image Snapshots

This is how image snapshots are taken:

qemu-img snapshot