(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.1 2019-01-28T17:51:57+00:00 2019-01-28T17:51:57+00:00 Robert Schweikert rjschwei@suse.com 2019-01-28T17:51:57+00:00 urn:sha1:09dcecf37628c5809ae21d7785693cb7358ca94c The systemd generator used had a hard coded path for the location target file to create. This path does not apply to all distributions. Make the generator and template to have the path set during build time. 2017-02-04T02:24:55+00:00 Scott Moser smoser@ubuntu.com 2017-02-04T02:24:55+00:00 urn:sha1:9698b0ded3d7e72f54513f248d8da41e08472f68 ds-identify is run here from the generator. If ds-identify does not see any datasources, it can completely disable cloud-init. The big value in this is that if there is no datasource, no python will ever be loaded, and cloud-init will be disabled.o The default policy being added here is: search,found=all,maybe=all,notfound=disabled That means: - enable (in 'datasource_list') all sources that are found. - if none are found, enable all 'maybe'. - if no maybe are found, then disable cloud-init. On platforms without DMI (everything except for aarch64 and x86), the default 'notfound' setting is 'enabled'. This is because many of the detection mechanisms rely on dmi data, which is present only on x86 and aarch64. 2016-08-22T20:20:10+00:00 Scott Moser smoser@brickies.net 2016-08-18T16:25:29+00:00 urn:sha1:64522efe710faf6fa1615dbb60a2fc4cc8a7c278 This adds some function to the generator to maintain the presense of a flag file '/run/cloud-init/enabled' indicating that cloud-init is enabled. Then, only run the dhclient hooks if on Azure and cloud-init is enabled. The test for is_azure currently only checks to see that the board vendor is Microsoft, not actually that we are on azure. Running should not be harmful anywhere, other than slowing down dhclient. The value of this additional code is that then dhclient having run does not task the system with the load of cloud-init. Additionally, some changes to config are done here. * rename 'dhclient_leases' to 'dhclient_lease_file' * move that to the datasource config (datasource/Azure/dhclient_lease_file) Also, it removes the config in config/cloud.cfg that set agent_command to __builtin__. This means that by default cloud-init still needs the agent installed. The suggested follow-on improvement is to use __builtin__ if there is no walinux-agent installed. 2016-05-27T21:03:49+00:00 Scott Moser smoser@ubuntu.com 2016-05-27T21:03:49+00:00 urn:sha1:b16533714e02fc71d463ca73abee5c9f6237f115 This didn't really work. See bug for more info. LP: #1577844 2016-03-19T00:40:54+00:00 Scott Moser smoser@ubuntu.com 2016-03-19T00:40:54+00:00 urn:sha1:519c0936e3e80fc14225e500fbb61d0d12d28c35 Note, still broken as cloud-init local is not going to ever touch the CI_NET_READY file (/run/cloud-init/network-config-ready). So as this is , it will actually just block for 60 seconds and go on. 2016-03-14T13:44:21+00:00 Scott Moser smoser@ubuntu.com 2016-03-14T13:44:21+00:00 urn:sha1:24bd640d20383116d1285361d7e86eda9e9d20e8 2016-03-10T15:41:48+00:00 Scott Moser smoser@ubuntu.com 2016-03-10T15:41:48+00:00 urn:sha1:b1d9c92f5bc6f711e104ceb981ded658249c3255 2016-03-10T15:35:17+00:00 Scott Moser smoser@ubuntu.com 2016-03-10T15:35:17+00:00 urn:sha1:2f29e70d99906dd7bff0c64109a77f609577f063 This might need cleaning up in the future as I believe in some containers /proc/cmdline is provided, and in that case it would be preferred to pid 1's command line. 2016-03-04T03:46:37+00:00 Scott Moser smoser@ubuntu.com 2016-03-04T03:46:37+00:00 urn:sha1:d02a257063db96f487510b9841a9a396ef2675af 2016-03-03T22:49:01+00:00 Scott Moser smoser@ubuntu.com 2016-03-03T22:49:01+00:00 urn:sha1:fa5c11836cec515dd23efcfabe9b736edd47c22a