(mirror of https://github.com/marekm72/vyos-cloud-init.git) https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=22.1 2021-12-13T17:43:58+00:00 2021-12-13T17:43:58+00:00 Brett Holman bholman.devel@gmail.com 2021-12-13T17:43:58+00:00 urn:sha1:35711700e10c47dcfa16238ba0bd395813e5a511 dh_systemd is now included in the default helper, no need to specify it anymore for impish 2021-10-29T20:39:29+00:00 James Falcon james.falcon@canonical.com 2021-10-29T20:39:29+00:00 urn:sha1:a90d8338f07b30a46887f7c133baade63129a53a When we added the install hotplug module, we forgot to update the redhet/cloud-init.spec.in file and allow for execution on /usr/libexec. This PR adds that functionality. 2021-10-12T14:31:36+00:00 Ryan Harper ryan.harper@canonical.com 2021-10-12T14:31:36+00:00 urn:sha1:b3e31ba228d32c318872fb68edda272f679e1004 In some cloud-init enabled images the sshd-keygen@.service may race with cloud-init and prevent ssh host keys from being generated or generating host keys twice slowing boot and consuming additional entropy during boot. This drop-in unit adds a condition to the sshd-keygen@.service which prevents running if cloud-init is active. 2021-08-05T16:32:36+00:00 Aleksander Baranowski aleksander.baranowski@yahoo.pl 2021-08-05T16:32:36+00:00 urn:sha1:3d9c862b6ded798031fad827328fa437bc14ac97 2021-07-19T19:13:21+00:00 James Falcon therealfalcon@gmail.com 2021-07-19T19:13:21+00:00 urn:sha1:184c836a16e9954a2cba11ae21f07923077ec904 Adds a udev script which will invoke a hotplug hook script on all net add events. The script will write some udev arguments to a systemd FIFO socket (to ensure we have only instance of cloud-init running at a time), which is then read by a new service that calls a new 'cloud-init devel hotplug-hook' command to handle the new event. This hotplug-hook command will: - Fetch the pickled datsource - Verify that the hotplug event is supported/enabled - Update the metadata for the datasource - Ensure the hotplugged device exists within the datasource - Apply the config change on the datasource metadata - Bring up the new interface (or apply global network configuration) - Save the updated metadata back to the pickle cache Also scattered in some unrelated typing where helpful 2020-10-19T20:59:16+00:00 Paride Legovini paride.legovini@canonical.com 2020-10-19T20:59:16+00:00 urn:sha1:5a7f6818083118b45828fa0b334309449881f80a bddeb builds a .deb package using the template packaging files in packages/debian/. The new --packaging-branch flag allows to specify a git branch where to pull the packaging (i.e. the debian/ directory) from. This is useful to build a .deb package from master with the very same packaging which is used for the uploads. 2020-08-27T14:37:14+00:00 Paride Legovini paride.legovini@canonical.com 2020-08-27T14:37:14+00:00 urn:sha1:575750ac4a3abb6fdfa45e2cc65186df291d8ddf 456fb55744a1acc6bd2f464b7656a9c33d0b7ac5 made tools/read-dependencies and package/brpm distinguish between build dependencies and runtime dependencies, however packages/redhat/cloud-init.spec.in expects all the dependencies to be in the 'requires' list, thus missing some build dependencies. This change makes cloud-init.spec use 'buildrequires' too. The build happens to succeed without python3-devel on the epel-8 copr chroot as it pulls in the epel-rpm-macros package, which in turn depends on python3-devel. In other words the dependency is satisfied by chance. Packages building for Python 3 need to explicitly specify BuildRequires: python3-devel, see: [1]. [1] https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ 2020-07-24T17:59:49+00:00 Ryan Harper ryan.harper@canonical.com 2020-07-24T17:59:49+00:00 urn:sha1:456fb55744a1acc6bd2f464b7656a9c33d0b7ac5 tools/read-dependencies: - Add parameters --build-requires, --runtime-requires - Sort dependency output before printing package/brpm - use --build-requires, --runtime-requires to separate build/vs runtime package reqs. LP: #1886107 2020-06-30T17:17:40+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-06-30T17:17:40+00:00 urn:sha1:66e114a660c53400e389f119781f378311b65108 caplog is only available in pytest itself from 3.0 onwards. In xenial, we only have pytest 2.8.7. However, in xenial we do have pytest-catchlog available (as python3-pytest-catchlog), so we use that where appropriate. 2020-06-08T16:49:12+00:00 Scott Moser smoser@brickies.net 2020-06-08T16:49:12+00:00 urn:sha1:3c551f6ebc12f7729a2755c89b19b9000e27cc88 This was painful, but it finishes a TODO from cloudinit/subp.py. It moves the following from util to subp: ProcessExecutionError subp which target_path I moved subp_blob_in_tempfile into cc_chef, which is its only caller. That saved us from having to deal with it using write_file and temp_utils from subp (which does not import any cloudinit things now). It is arguable that 'target_path' could be moved to a 'path_utils' or something, but in order to use it from subp and also from utils, we had to get it out of utils.