Linux Virtualization Naming Conventions: Difference between revisions
Jump to navigation
Jump to search
| 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|name}}. | ||
=Virtual Machine Image Naming Convention= | =Virtual Machine Image Naming Convention= | ||
Revision as of 13:40, 30 June 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>.img
Example:
node1.img
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>.storage
Example:
node1-docker.storage