summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorBen Howard <bh@digitalocean.com>2016-08-19 16:28:26 -0600
committerScott Moser <smoser@brickies.net>2016-09-29 09:57:13 -0400
commit9f83bb8e80806d3dd79ba426474dc3c696e19a41 (patch)
tree90f695169bec78c544c9f2f345514360089231fd /doc
parent6d1edc3f5a18b328bdd307426056539d5b9071fd (diff)
downloadvyos-cloud-init-9f83bb8e80806d3dd79ba426474dc3c696e19a41.tar.gz
vyos-cloud-init-9f83bb8e80806d3dd79ba426474dc3c696e19a41.zip
DigitalOcean: use meta-data for network configruation
On DigitalOcean, Network information is provided via Meta-data. It changes the datasource to be a local datasource, meaning it will run before fallback networking is configured. The advantage of that is that before networking is configured it can bring up a network device with ipv4 link-local and hit the metadata service that lives at 169.254.169.254 to find its networking configuration. It then takes down the link local address and lets cloud-init configure networking. The configuring of a network device to go looking for a metadata service is gated by a check of data in the smbios. This guarantees that the code will not run on another system.
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions