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

docs(quick-start): Clarified use of fields in cloud config

Browse Source 
Updated the language to illustrate that fields in a cloud config is not
supported in all environments. This is expressed explicitly in PXE and
install to disk pages. The quick start lacked this information and is
inconsistent.
This commit is contained in:
Benjamin Campbell 2014-07-24 11:22:08 -06:00
parent 7fc67c2acf
commit 5593408be8
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/cloud-config.md
View File

@ -40,7 +40,9 @@ CoreOS tries to conform to each platform's native method to provide user data. E
#### etcd #### etcd
The `coreos.etcd.*` parameters will be translated to a partial systemd unit acting as an etcd configuration file. The `coreos.etcd.*` parameters will be translated to a partial systemd unit acting as an etcd configuration file.
We can use the templating feature of coreos-cloudinit to automate etcd configuration with the `$private_ipv4` and `$public_ipv4` fields. For example, the following cloud-config document... If the platform environment supports the templating feature of coreos-cloudinit it is possible to automate etcd configuration with the `$private_ipv4` and `$public_ipv4` fields. For example, the following cloud-config document...
Note: The $private_ipv4 and $public_ipv4 substitution variables referenced in other documents are not supported on PXE or disk installation systems.
```yaml ```yaml
#cloud-config #cloud-config