Translations:Managing your cloud resources with OpenStack/22/en: Difference between revisions
(Importing a new version from external source) |
m (FuzzyBot moved page Translations:OpenStack/22/en to Translations:Managing your cloud resources with OpenStack/22/en without leaving a redirect: Part of translatable page "OpenStack") |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Booting | ==Booting from a Volume== | ||
If you want to run a persistent machine, it is safest to boot from a volume. When you boot a VM from an image rather than a volume, the VM is stored on the local disk of the actual machine running the VM. If something goes wrong with that machine or its disk the VM may be lost. Volume storage has redundancy which protects the VM from hardware failure. Typically when booting from a volume VM flavors starting with a 'p' are used (see [[Virtual machine flavors]]). | If you want to run a persistent machine, it is safest to boot from a volume. When you boot a VM from an image rather than a volume, the VM is stored on the local disk of the actual machine running the VM. If something goes wrong with that machine or its disk the VM may be lost. Volume storage has redundancy which protects the VM from hardware failure. Typically when booting from a volume VM flavors starting with a 'p' are used (see [[Virtual machine flavors]]). | ||
Latest revision as of 18:42, 8 November 2022
Booting from a Volume
If you want to run a persistent machine, it is safest to boot from a volume. When you boot a VM from an image rather than a volume, the VM is stored on the local disk of the actual machine running the VM. If something goes wrong with that machine or its disk the VM may be lost. Volume storage has redundancy which protects the VM from hardware failure. Typically when booting from a volume VM flavors starting with a 'p' are used (see Virtual machine flavors).