Ask Your Question

What is the difference between images and volumes?

asked 2013-10-08 04:03:28 -0500

anonymous user


I've been reading many of the openstack docs and have already a test installation thanks to stackforge, but I seem to be missing a critical piece of insight into what exactly the difference between volumes and images is. Obviously they support different use-cases (e.g. "launch an image" vs. "boot from volume"), but I've not found a consise explanation what is what and how this fits together.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2013-10-08 05:49:20 -0500

sngirame gravatar image

As far as my understanding goes

Images are similar to VM templates of vmware, wherein OS is pre-installed & you can create instances out of it. Even if you do not assign a volume to an image they can boot and work as the image by default has some disk assigned. By assigning volume (block storage) to an image you get additional drive on the VM where you can have your structural data. Even if you delete the VM, the data on volume is persistent. You can attach the volume to another VM just like an USB drive.

I hope this answers you query

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-10-08 04:03:28 -0500

Seen: 3,434 times

Last updated: Oct 08 '13