cc_staff
1,486
edits
Managing your cloud resources with OpenStack: Difference between revisions
Jump to navigation
Jump to search
Managing your cloud resources with OpenStack (view source)
Revision as of 15:56, 2 March 2016
, 8 years ago→Working with Volumes
| Line 1: | Line 1: | ||
==Working with Volumes== | ==Working with Volumes== | ||
===Creating a Volume=== | |||
[[File:OpenStack-Dashboard-Compute-Volumes.png|800px|thumb| OpenStack Dashboard, Compute Volumes (Click for larger image)]] | [[File:OpenStack-Dashboard-Compute-Volumes.png|800px|thumb| OpenStack Dashboard, Compute Volumes (Click for larger image)]] | ||
| Line 17: | Line 18: | ||
Finally click the blue "Create Volume" button. | Finally click the blue "Create Volume" button. | ||
===Accessing a Volume from a VM=== | |||
To access the volume from a VM you must attach it. This is done by clicking the "More" drop down and selecting "Edit Attachments" and in the "Attach to Instance" drop down box select the VM you wish to attach it to and click the blue "Attach Volume" button. Once the volume is attached, it will show you on the Compute->Volumes dashboard that the newly created volume <code>data</code> is attached to your selected VM on <code>/dev/vdb</code> or some similar location. This is exactly the same as if you had inserted a USB key or an external drive. | To access the volume from a VM you must attach it. This is done by clicking the "More" drop down and selecting "Edit Attachments" and in the "Attach to Instance" drop down box select the VM you wish to attach it to and click the blue "Attach Volume" button. Once the volume is attached, it will show you on the Compute->Volumes dashboard that the newly created volume <code>data</code> is attached to your selected VM on <code>/dev/vdb</code> or some similar location. This is exactly the same as if you had inserted a USB key or an external drive. | ||
On most linux distributions the following steps can be used to partition, format, and mount the newly created volume. Note if this is not a newly created volume the partition and format steps should be skipped as this will result in loss of data on that volume, unless this is what you want. | ===Formatting and Mounting an Empty Volume=== | ||
On most linux distributions the following steps can be used to partition, format, and mount the newly created volume. Note if this is not a newly created volume the partition and format steps should be skipped as this will result in loss of data on that volume, unless this is what you want, and only the steps to mount the volume should be followed. | |||
<ol> | <ol> | ||
| Line 46: | Line 49: | ||
Then to mount the device just added to <code>/etc/fstab</code> run | Then to mount the device just added to <code>/etc/fstab</code> run | ||
{{Command| sudo mount -a}} | {{Command| sudo mount -a}} | ||
===Booting From a Volume=== | ===Booting From a Volume=== | ||
If running a persistent machine booting from a volume is a safer option. When creating a VM booting from an image, rather than a volume, it will store the VM on the local disk of the actual machine running the VM. If something went wrong with that machine or its disk there is a good chance your VM would be lost. Volume storage has a built in redundancy which will protect your volumes from hardware failure. | If running a persistent machine booting from a volume is a safer option. When creating a VM booting from an image, rather than a volume, it will store the VM on the local disk of the actual machine running the VM. If something went wrong with that machine or its disk there is a good chance your VM would be lost. Volume storage has a built in redundancy which will protect your volumes from hardware failure. | ||