Volumes - Revision history

Jason Lee at 18:28, 23 January 2017

2017-01-23T18:28:53Z

2017-01-23T18:28:35Z

2016-01-05T22:57:33Z

2016-01-01T17:26:33Z

2015-05-20T18:39:04Z

2015-01-29T16:54:54Z

2014-09-28T18:51:52Z

2014-09-28T18:51:41Z

2014-09-28T18:50:19Z

2014-09-08T01:16:49Z

@@ Line 18: / Line 18: @@
   <nowiki>mkfs.ext4 /dev/vdc
-mkdir /mnt/myvolmue
+mkdir /mnt/myvolume
 mount /dev/vdc /mnt/myvolume</nowiki>

@@ Line 18: / Line 18: @@
   <nowiki>mkfs.ext4 /dev/vdc
-mkdir /mnt/mvyolmue
+mkdir /mnt/myvolmue
 mount /dev/vdc /mnt/myvolume</nowiki>

@@ Line 9: / Line 9: @@
 == Managing volumes ==
-Start off by creating a new, empty volume. Head over to the [https://dynamic.lunanode.com/panel/volumes.php volume management page], enter a label (like "myvolume") and a size in gigabytes, and press the create button. Note that volume storage is charged at $0.03 per GB per month, billed hourly.
+Start off by creating a new, empty volume. Head over to the [https://dynamic.lunanode.com/panel/volumes volume management page], enter a label (like "myvolume") and a size in gigabytes, and press the create button. Note that volume storage is charged at $0.03 per GB per month, billed hourly.
 After a few seconds, your volume should be ready. You can view volume details by selecting the name from the volume list.

← Older revision		Revision as of 17:26, 1 January 2016
Line 1:		Line 1:
−	Volumes are detachable block storage devices that are stored volumes on a fault-tolerant distributed ~~filesystem~~, and can be attached and detached from virtual machine instances on the fly.	+	Volumes are detachable block storage devices that are stored volumes on a fault-tolerant distributed block storage cluster (Ceph RBD), and can be attached and detached from virtual machine instances on the fly.

	== Use cases ==		== Use cases ==

@@ Line 9: / Line 9: @@
 == Managing volumes ==
-Start off by creating a new, empty volume. Head over to the [https://dynamic.lunanode.com/panel/volumes.php volume management page], enter a label (like "myvolume") and a size in gigabytes, and press the create button. Note that volume storage is charged at $0.04 per GB per month, billed hourly.
+Start off by creating a new, empty volume. Head over to the [https://dynamic.lunanode.com/panel/volumes.php volume management page], enter a label (like "myvolume") and a size in gigabytes, and press the create button. Note that volume storage is charged at $0.03 per GB per month, billed hourly.
 After a few seconds, your volume should be ready. You can view volume details by selecting the name from the volume list.

← Older revision		Revision as of 16:54, 29 January 2015
Line 22:		Line 22:

	Then, you will be able to access the volume via '''/mnt/myvolume'''. (Note that the device might be '''/dev/hdc''' or '''/dev/sdc''' or something else instead of '''/dev/vdc'''.)		Then, you will be able to access the volume via '''/mnt/myvolume'''. (Note that the device might be '''/dev/hdc''' or '''/dev/sdc''' or something else instead of '''/dev/vdc'''.)
		+
		+	You can also boot a new virtual machine instance from a volume by selecting the volume in the VM creation page. The volume must be available or this will throw an error.

	'''Note for IDE driver''': if you are using IDE driver (didn't select virtio when adding an image; Windows for example does not natively support virtio) then you will need to shut-down your VM prior to attaching the volume. The "auto" target will also not work, you should enter /dev/hdc instead.		'''Note for IDE driver''': if you are using IDE driver (didn't select virtio when adding an image; Windows for example does not natively support virtio) then you will need to shut-down your VM prior to attaching the volume. The "auto" target will also not work, you should enter /dev/hdc instead.

← Older revision		Revision as of 18:51, 28 September 2014
Line 23:		Line 23:
	Then, you will be able to access the volume via '''/mnt/myvolume'''. (Note that the device might be '''/dev/hdc''' or '''/dev/sdc''' or something else instead of '''/dev/vdc'''.)		Then, you will be able to access the volume via '''/mnt/myvolume'''. (Note that the device might be '''/dev/hdc''' or '''/dev/sdc''' or something else instead of '''/dev/vdc'''.)

−	~~[b]~~Note for IDE driver~~[/b]~~: if you are using IDE driver (didn't select virtio when adding an image; Windows for example does not natively support virtio) then you will need to shut-down your VM prior to attaching the volume. The "auto" target will also not work, you should enter /dev/hdc instead.	+	'''Note for IDE driver''': if you are using IDE driver (didn't select virtio when adding an image; Windows for example does not natively support virtio) then you will need to shut-down your VM prior to attaching the volume. The "auto" target will also not work, you should enter /dev/hdc instead.

@@ Line 13: / Line 13: @@
 After a few seconds, your volume should be ready. You can view volume details by selecting the name from the volume list.
-Once the status on the volume details page shows as '''available''', the volume is ready to be attached to a virtual machine instance. You can select the virtual machine from the dropdown and hit "Attach volume" (leave target device as auto; if that fails, then try setting it to /dev/vdc).
+Once the status on the volume details page shows as '''available''', the volume is ready to be attached to a virtual machine instance. You can select the virtual machine from the dropdown and hit "Attach volume" (leave target device as auto; if that fails, then try setting it to /dev/vdc or /dev/hdc, depending on your disk driver).
 Now, login to your virtual machine; in /dev, you should see the volume appear now. You will want to format it so that you can mount it as a filesystem on your VM: