unistack-org/cloudinit
4
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Filled cloud providers cloud-config URLs

Browse Source
This commit is contained in:
kayrus 2015-08-28 12:56:47 +02:00
parent 9c4aca6c9a
commit 4f76283917
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/cloud-config-locations.md
View File

@ -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. * `/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. * 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. * 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: You can also run the `coreos-cloudinit` tool manually and provide a path to your custom Cloud-Config file: