summaryrefslogtreecommitdiff
path: root/systemd/cloud-init-generator
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2016-03-08 12:07:55 -0500
committerScott Moser <smoser@ubuntu.com>2016-03-08 12:07:55 -0500
commit93e553d64baf6f7e9b135b86f822c4af8bd192d0 (patch)
tree5643fa70cef8b4362d60f13b7aa0a34af64e2ef0 /systemd/cloud-init-generator
parent13fa076e7d9d3f04a93e6edd0db828c7e0238892 (diff)
parentf39e9b337778a0348ab08161d19c116408de5312 (diff)
downloadvyos-cloud-init-93e553d64baf6f7e9b135b86f822c4af8bd192d0.tar.gz
vyos-cloud-init-93e553d64baf6f7e9b135b86f822c4af8bd192d0.zip
No longer run pollinate by default in seed_random
The user can still choose to run pollinate here to seed their random data. And in an environment with network datasource, that would be expected to work. However, we do not want to run it any more from cloud-init because a.) pollinate's own init system jobs should get it ran before ssh, which is the primary purpose of wanting cloud-init to run it. b.) with a local datasource, there is no network guarantee when init_modules run, so pollinate -q would often cause issues then. c.) cloud-init would run pollinate and log the failure causing many cloud-init specific failures that it could do nothing about. Additionally, add documentation for the seed_random config module.
Diffstat (limited to 'systemd/cloud-init-generator')
0 files changed, 0 insertions, 0 deletions