(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.1 2019-10-31T14:45:29+00:00 2019-10-31T14:45:29+00:00 Ryan Harper ryan.harper@canonical.com 2019-10-31T14:45:29+00:00 urn:sha1:8888ca1af7f1fed33e79b56694834310ed35559a In Centos/RHEL 8, NetworkManager is installed as the networking service. cloud-init.service needs to run After this service to allow the OS to bring networking up first. LP: #1843334 2019-09-26T14:39:27+00:00 Robert Schweikert rjschwei@suse.com 2019-09-26T14:39:27+00:00 urn:sha1:66ef979a2d7b8003def1ee4d7a6b6a261b37e0ee Change the startup order. On SUSE distros cloud-init.service should start after wicked.service. This reflects the same start up order other distributions utilize. 2019-06-19T17:16:08+00:00 Ryan Harper ryan.harper@canonical.com 2019-06-19T17:16:08+00:00 urn:sha1:e1795a5cd1cb216e5514f55bdb1cddc605f40df3 Update the template to use libexec prefix path to ds-identify on redhat systems. LP: #1833264 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. 2018-10-24T14:34:50+00:00 Robert Schweikert rjschwei@suse.com 2018-10-24T14:34:50+00:00 urn:sha1:e0084a599d5259e507298175dad8a1e719017895 With db50bc0d9 the sysconfig renderer was enabled for openSUSE and SUSE Linux Enterprise. This requires that cloud-init.service starts before wicked. LP: #1799709 2018-05-14T19:38:22+00:00 Scott Moser smoser@ubuntu.com 2018-05-14T19:38:22+00:00 urn:sha1:d5374bba2f1b4607a773ebff00e1ee7d66e23033 This makes cloud-config.service (and as a result cloud-final.service) run After snap.seeded.service. This is required to ensure that pre-seeded snaps can be used by cloud-init or user-data input. The snap.seeded.service was added to snapd at:   https://github.com/snapcore/snapd/pull/5124 Note that the following would be a workaround:  snap:   commands:    00: snap wait system seed.loaded LP: #1767131 2017-12-11T21:56:14+00:00 Robert Schweikert rjschwei@suse.com 2017-11-19T20:51:24+00:00 urn:sha1:022e8688050f19977842ee807bf2e699625b2ff8 On openSUSE and SLES systemd is allowed to pull the default dependencies, thus setting "Before=basic.target" is incorrect and creates a cycle leading to the deletion of the cloud-init-local.service 2017-10-03T14:09:13+00:00 Robert Schweikert rjschwei@suse.com 2017-09-18T16:32:10+00:00 urn:sha1:7fd04255ef238e06d1d9c9a5cc35060d36d83f2b Depending on distribution the default number of tasks (threads) maybe unexpectedly low or it may be the default systemd setting (512). Setting TasksMax to "infinity" in cloud-init-final.service removes the restriction on tasks created. LP: #1717969 2017-10-02T19:27:17+00:00 Robert Schweikert rjschwei@suse.com 2017-09-24T19:10:36+00:00 urn:sha1:6f2aaf7b0fa9fd9376561e9b6233b4d36de51da1 Ordering on apt service should only be set up on Debian based distributions. This changes is really a net-zero in runtime result. But, mentioning apt on a rpm based distro could be confusing. 2017-09-21T18:15:50+00:00 Robert Schweikert rjschwei@suse.com 2017-09-21T11:38:48+00:00 urn:sha1:0451a9f60960da56e3af4f97bbcece3d98482f86 Things done here: - identify 'suse' as a variant in util.system_info and also tools/render-cloudcfg. - update systemd and cloud.cfg templates for suse specific changes. LP: #1718640