From 4f762839171fdb6ad772c2be790913996282dc7a Mon Sep 17 00:00:00 2001 From: kayrus Date: Fri, 28 Aug 2015 12:56:47 +0200 Subject: [PATCH 1/2] Filled cloud providers cloud-config URLs --- Documentation/cloud-config-locations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/cloud-config-locations.md b/Documentation/cloud-config-locations.md index b1c5036..2b39e1c 100644 --- a/Documentation/cloud-config-locations.md +++ b/Documentation/cloud-config-locations.md @@ -8,7 +8,7 @@ On every boot, coreos-cloudinit looks for a config file to configure your host. * `/var/lib/coreos-install/user_data` when you install CoreOS manually using the [coreos-install](/os/docs/latest/installing-to-disk.html) tool. Usually used in bare metal installations. * OEM images use `/usr/share/oem/cloud-config.yml` path. * Azure platform uses OEM path for first Cloud-Config initialization and then `/var/lib/waagent/CustomData` to apply your settings. -* DigitalOcean and EC2 use URLs to download Cloud-Config. +* DigitalOcean, EC2 and Packet cloud providers use URLs to download Cloud-Config. `http://169.254.169.254/metadata/v1/user-data`, `http://169.254.169.254/2009-04-04/user-data` and `https://metadata.packet.net/userdata` correspondingly. You can also run the `coreos-cloudinit` tool manually and provide a path to your custom Cloud-Config file: From 61e3595520e879723cf3244bbacead78e0a4b7ee Mon Sep 17 00:00:00 2001 From: kayrus Date: Mon, 31 Aug 2015 11:41:59 +0200 Subject: [PATCH 2/2] Added table for cloud-config locations --- Documentation/cloud-config-locations.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/Documentation/cloud-config-locations.md b/Documentation/cloud-config-locations.md index 2b39e1c..fd8c2e7 100644 --- a/Documentation/cloud-config-locations.md +++ b/Documentation/cloud-config-locations.md @@ -2,13 +2,15 @@ On every boot, coreos-cloudinit looks for a config file to configure your host. Here is a list of locations which are used by the Cloud-Config utility, depending on your CoreOS platform: -* Mount point with [config-2](/os/docs/latest/config-drive.html#contents-and-format) label. It should contain a `openstack/latest/user_data` relative path. An absolute path inside CoreOS should look like `/media/configvirtfs/openstack/latest/user_data`. Usually used by cloud providers or in VM installations. -* FAT or ISO9660 filesystem with [config-2](/os/docs/latest/config-drive.html#qemu-virtfs) label. A `/media/configdrive/` mount point should contain a `/media/configdrive/openstack/latest/user_data` absolute path to the config file. Usually used in VM installations. -* Kernel command line: `cloud-config-url=http://example.com/user_data`. You can find this string using this command `cat /proc/cmdline`. Usually used in [PXE](/os/docs/latest/booting-with-pxe.html) or [iPXE](/os/docs/latest/booting-with-ipxe.html) boots. -* `/var/lib/coreos-install/user_data` when you install CoreOS manually using the [coreos-install](/os/docs/latest/installing-to-disk.html) tool. Usually used in bare metal installations. -* OEM images use `/usr/share/oem/cloud-config.yml` path. -* Azure platform uses OEM path for first Cloud-Config initialization and then `/var/lib/waagent/CustomData` to apply your settings. -* DigitalOcean, EC2 and Packet cloud providers use URLs to download Cloud-Config. `http://169.254.169.254/metadata/v1/user-data`, `http://169.254.169.254/2009-04-04/user-data` and `https://metadata.packet.net/userdata` correspondingly. +Location | Description +--- | --- | --- +|`/media/configvirtfs/openstack/latest/user_data`|`/media/configvirtfs` mount point with [config-2](/os/docs/latest/config-drive.html#contents-and-format) label. It should contain a `openstack/latest/user_data` relative path. Usually used by cloud providers or in VM installations.| +|`/media/configdrive/openstack/latest/user_data`|FAT or ISO9660 filesystem with [config-2](/os/docs/latest/config-drive.html#qemu-virtfs) label and `/media/configdrive/` mount point. It should also contain a `openstack/latest/user_data` relative path. Usually used in installations which are configured by USB Flash sticks or CDROM media.| +|Kernel command line: `cloud-config-url=http://example.com/user_data`.| You can find this string using this command `cat /proc/cmdline`. Usually used in [PXE](/os/docs/latest/booting-with-pxe.html) or [iPXE](/os/docs/latest/booting-with-ipxe.html) boots.| +|`/var/lib/coreos-install/user_data`| When you install CoreOS manually using the [coreos-install](/os/docs/latest/installing-to-disk.html) tool. Usually used in bare metal installations.| +|`/usr/share/oem/cloud-config.yml`| Path for OEM images.| +|`/var/lib/waagent/CustomData`| Azure platform uses OEM path for first Cloud-Config initialization and then `/var/lib/waagent/CustomData` to apply your settings.| +|`http://169.254.169.254/metadata/v1/user-data` `http://169.254.169.254/2009-04-04/user-data` `https://metadata.packet.net/userdata`|DigitalOcean, EC2 and Packet cloud providers correspondingly use these URLs to download Cloud-Config.| You can also run the `coreos-cloudinit` tool manually and provide a path to your custom Cloud-Config file: