(mirror of https://github.com/marekm72/vyos-cloud-init.git) https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=circinus 2021-10-29T20:39:29+00:00 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-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-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-05-02T00:57:24+00:00 Paride Legovini paride.legovini@canonical.com 2020-05-02T00:57:24+00:00 urn:sha1:4d2684848722cb2d469ad4fa60999bf81cf7056e Since upstream cloud-init has dropped python2 support, adapt remaining package build scripts and tools to python3 only Changes: * Do not template debian/rules as python3 is the only supported version * Drop six from requirements.txt * Makefile: drop everything related to Python 2 * run-container: install the CI deps only on ubuntu|debian * read-version: update the shebang to use Python 3 * brpm: read_dependencies(): drop unused argument * read-dependencies: switch to Py3 and drop the --python-version option * pkg-deps.json: drop the Python version field and update the redhat deps * pkg-deps.json: drop the unittest2 and contextlib2 renames * Update RPM the spec file to use Python 3 when building the RPM * bddeb: drop support for Python 2 2019-04-19T21:38:44+00:00 Daniel Watkins daniel.watkins@canonical.com 2019-04-19T21:38:44+00:00 urn:sha1:69251d5b4431204c1e768fdf6e9f268edceb2e96 LP: #1825444 2018-10-25T20:01:39+00:00 Jason Zions jasonzio@microsoft.com 2018-10-25T20:01:39+00:00 urn:sha1:744c42361317eaa23f860104f152432e5bb5b996 2018-05-23T18:41:11+00:00 Scott Moser smoser@ubuntu.com 2018-05-23T18:41:11+00:00 urn:sha1:2ab8960402677ab66583d56dcb7704369a1256f5 This makes the necessary changes to patch the full packaged version into the trunk maintained redhat and suse spec files. 2018-04-18T01:07:59+00:00 Ryan Harper ryan.harper@canonical.com 2018-04-18T01:07:59+00:00 urn:sha1:6a979bb2fabd187efc392de7b0852cd0361bc9b8 In bash shells with bash_completion enabled, now the cloud-init sub commands and parameters/flags will be shown. 2017-09-15T17:14:18+00:00 Balint Reczey balint.reczey@canonical.com 2017-09-15T15:50:52+00:00 urn:sha1:a2f8ce9c80debdb788e7ab37401aa98c2c270f26 Revert "centos: do not package systemd-fsck drop-in." Revert "systemd: make systemd-fsck run after cloud-init.service" The systemd-fsck drop-in caused regressions by introducing ordering The change reverts the original commit that added systemd-fsck drop-in and another commit that had removed that from the centos packaging: 1f5489c258a26f4e26261c40786537951d67df1e 8a5296c41db45be3a172862f324ad44e732a2250 The result is to no longer provide the systemd-fsck drop-in. LP: #1717477