Linux Virtualization Naming Conventions: Difference between revisions
Jump to navigation
Jump to search
| (14 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
=Virtual Machine Naming Convention= | =Virtual Machine Naming Convention= | ||
For more details about the virtual machine name, see {{KVM_Virtual_Machine_XML_Configuration_Example#name|name}} | For more details about the virtual machine name, see {{Internal|KVM_Virtual_Machine_XML_Configuration_Example#name|KVM Virtual Machine Definition 'name'}} | ||
=Virtual Machine Image Naming Convention= | =Virtual Machine Image Naming Convention= | ||
The | The main volume of virtual machine, which contains the [[Linux_Virtualization_Concepts#Virtual_Machine_Image|virtual machine image]] should follow the pattern: | ||
< | <font size=-2> | ||
<vm-name>. | <vm-name>.<image-format> | ||
</ | </font> | ||
Example: | Example: | ||
< | <font size=-2> | ||
gp.qcow2 | |||
</ | </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: | ||
< | <font size=-2> | ||
<vm-name|generic-name>-<purpose>. | <vm-name|generic-name>-<purpose>.<image-format> | ||
</ | </font> | ||
Example: | Example: | ||
< | <font size=-2> | ||
node1-docker. | node1-docker.raw | ||
</ | support-nfs.raw | ||
</font> | |||
=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: | |||
{{Internal|Linux_Virtualization_Concepts#Disk_Image_Snapshots|Disk Image Snapshots}} | |||
This is how image snapshots are taken: | |||
{{Internal|Qemu-img#Take_a_Snapshot|qemu-img snapshot}} | |||
Latest revision as of 00:27, 30 July 2023
Internal
Virtual Machine Naming Convention
For more details about the virtual machine name, see
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:
This is how image snapshots are taken: