diff options
| author | Scott Moser <smoser@ubuntu.com> | 2013-09-27 19:38:05 -0400 |
|---|---|---|
| committer | Scott Moser <smoser@ubuntu.com> | 2013-09-27 19:38:05 -0400 |
| commit | cafa32eb35e6ef7eba70a49e56dfeda51fd1f8a1 (patch) | |
| tree | 25596b8dc52d4e355805dfdff2032763e57d73cc /doc/sources | |
| parent | 4063358ec2f20bcff4328fb659cecbed668a9a48 (diff) | |
| parent | fdf5a48420b670b4b07c745b2b80c1cb23f253db (diff) | |
| download | vyos-cloud-init-cafa32eb35e6ef7eba70a49e56dfeda51fd1f8a1.tar.gz vyos-cloud-init-cafa32eb35e6ef7eba70a49e56dfeda51fd1f8a1.zip | |
Enable filesystem creation on Azure, many disk_setup cleanups
There are a lot of cleanups here around Azure, SmartOS and disk_setup.
disk_setup correctly identifies disk "aliases" (block device mappings
from ec2), anywhere where you would use a device name.
You can also specify these mappings to the Azure or SmartOS datasource
in their datasource config (device_aliases).
Also, stop Azure from calling blkid repeatedly in its tests, which
really pounded my laptop.
Diffstat (limited to 'doc/sources')
| -rw-r--r-- | doc/sources/smartos/README.rst | 28 |
1 files changed, 17 insertions, 11 deletions
diff --git a/doc/sources/smartos/README.rst b/doc/sources/smartos/README.rst index e2d3312e..8b63e520 100644 --- a/doc/sources/smartos/README.rst +++ b/doc/sources/smartos/README.rst @@ -73,15 +73,21 @@ or not to base64 decode something: (i.e. /etc/cloud/cloud.cfg.d) that sets which values should not be base64 decoded. -ephemeral_disk: +disk_aliases and ephemeral disk: --------------- - -In order to instruct Cloud-init which disk to auto-mount. By default, -SmartOS only supports a single ephemeral disk. - -The default SmartOS configuration will prepare the ephemeral disk and format -it for you. SmartOS does not, by default, prepare the ephemeral disk for you. - -If you change ephemeral_disk, you should also consider changing -the default disk formatting parameters. See -doc/examples/cloud-config-disk-setup.txt for information on using this. +By default, SmartOS only supports a single ephemeral disk. That disk is +completely empty (un-partitioned with no filesystem). + +The SmartOS datasource has built-in cloud-config which instructs the +'disk_setup' module to partition and format the ephemeral disk. + +You can control the disk_setup then in 2 ways: + 1. through the datasource config, you can change the 'alias' of + ephermeral0 to reference another device. The default is: + 'disk_aliases': {'ephemeral0': '/dev/vdb'}, + Which means anywhere disk_setup sees a device named 'ephemeral0' + then /dev/vdb will be substituted. + 2. you can provide disk_setup or fs_setup data in user-data to overwrite + the datasource's built-in values. + +See doc/examples/cloud-config-disk-setup.txt for information on disk_setup. |