Linux Virtualization Naming Conventions: Difference between revisions
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
=Virtual Machine Naming Convention= | =Virtual Machine Naming Convention= | ||
The ... that will hold a [[Linux_Virtualization_Concepts#Virtual_Machine_Image|virtual machine image]] should follow the pattern: | |||
<pre> | |||
<vm-name>.img | |||
</pre> | |||
Example: | |||
<pre> | |||
node1.img | |||
</pre> | |||
=Virtual Machine Image Naming Convention= | =Virtual Machine Image Naming Convention= | ||
Revision as of 21:10, 28 June 2017
Internal
Virtual Machine Naming Convention
The ... that will hold a virtual machine image should follow the pattern:
<vm-name>.img
Example:
node1.img
Virtual Machine Image Naming Convention
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