Linux Virtualization Naming Conventions: Difference between revisions
Jump to navigation
Jump to search
Line 33: | Line 33: | ||
node1-docker.raw | node1-docker.raw | ||
support-nfs.raw | support-nfs.raw | ||
=Disk Image Snapshot Naming Conventions= | |||
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||}} |
Revision as of 17:50, 4 July 2017
Internal
Virtual Machine Naming Convention
For more details about the virtual machine name, see
Virtual Machine Image Naming Convention
The ... that will hold a virtual machine image should follow the pattern:
<vm-name>.<image-format>
Example:
node1.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 Naming Conventions
More about disk image snapshots is available here:
This is how image snapshots are taken:
- [[|]]