Skip to content
Matthew Kelly edited this page Jul 30, 2017 · 1 revision

Overview

The Drives section is where you can define additional unmanaged data disks for your VMs. These disks will then be created as new drive partitions on your VM.

The drive section can only be used in a VM template object, under the drives array object:

{
    "template": [
        {
            "type": "vm",
            "drives": [
                {
                    "lun": 1,
                    "name": "Logs",
                    "letter": "K",
                    "size": 256,
                    "caching": "ReadOnly"
                }
            ]
        }
    ]
}

You can specify none, one or as many drives as you want - but you are limited by the main size/offer of the VM that you've created, as well as drive letters available.

Fogg can update drives - such as size, name, letter and caching mode - but it will never remove them

Properties

Below are the properties that are used when defining a drive object

Name Type Required Description
lun int yes The disks Logical Unit Number, once set this must never be changed
name string yes The drive's name on the VM, must be alphanumeric. Only for display purposes, and can be updated
letter char yes The drive's letter on the VM, can only be between letters F-Y. This can be updated
size int yes The size of the disk in GB, you may update this but only to a larger value
caching string no Default: ReadOnly. The caching mode of the disk, possible values are ReadOnly, ReadWrite and None. This can be updated

When updating a disk, you cannot decrease the size - only increase or remain the same. Also, when you define the LUN value, you must never change the value

You are able to update the name, letter and size of a disk/drive as you feel free. However, when updating the name and letter, refrain from updating to names/letters of drives that already exist. This will fail, and could have drastic results.

Clone this wiki locally