Linux Virtualization Naming Conventions: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 8: | Line 8: | ||
=Storage Volume 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 [[Linux_Virtualization_Concepts#Virtual_Machine_Image|virtual machine image]], the volume name should follow the pattern: | |||
<pre> | |||
<vm-name|generic-name>-<purpose>.storage | |||
</pre> | |||
Example: | |||
<pre> | |||
node1-docker.storage | |||
</pre> | |||
Revision as of 21:07, 28 June 2017
Internal
Virtual Machine Naming Convention
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