diff options
Diffstat (limited to 'doc/examples/cloud-config-disk-setup.txt')
| -rw-r--r-- | doc/examples/cloud-config-disk-setup.txt | 21 |
1 files changed, 16 insertions, 5 deletions
diff --git a/doc/examples/cloud-config-disk-setup.txt b/doc/examples/cloud-config-disk-setup.txt index 3fc47699..6ad61c33 100644 --- a/doc/examples/cloud-config-disk-setup.txt +++ b/doc/examples/cloud-config-disk-setup.txt @@ -30,8 +30,8 @@ disk_setup: fs_setup: - label: ephemeral0 filesystem: ext4 - device: ephemeral0 - partition: auto + device: ephemeral0.1 + replace_fs: ntfs Default disk definitions for SmartOS @@ -47,8 +47,7 @@ disk_setup: fs_setup: - label: ephemeral0 filesystem: ext3 - device: ephemeral0 - partition: auto + device: ephemeral0.0 Cavaut for SmartOS: if ephemeral disk is not defined, then the disk will not be automatically added to the mounts. @@ -171,6 +170,7 @@ The general format is: device: <DEVICE> partition: <PART_VALUE> overwrite: <OVERWRITE> + replace_fs: <FS_TYPE> Where: <LABEL>: The file system label to be used. If set to None, no label is @@ -187,7 +187,13 @@ Where: label as 'ephemeralX' otherwise there may be issues with the mounting of the ephemeral storage layer. - <PART_VALUE>: The valid options are: + If you define the device as 'ephemeralX.Y' then Y will be interpetted + as a partition value. However, ephermalX.0 is the _same_ as ephemeralX. + + <PART_VALUE>: + Partition definitions are overwriten if you use the '<DEVICE>.Y' notation. + + The valid options are: "auto|any": tell cloud-init not to care whether there is a partition or not. Auto will use the first partition that does not contain a file system already. In the absence of a partition table, it will @@ -236,5 +242,10 @@ Where: "false": If an existing file system exists, skip the creation. + <REPLACE_FS>: This is a special directive, used for Windows Azure that + instructs cloud-init to replace a file system of <FS_TYPE>. NOTE: + unless you define a label, this requires the use of the 'any' partition + directive. + Behavior Caveat: The default behavior is to _check_ if the file system exists. If a file system matches the specification, then the operation is a no-op. |