(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.1 2019-04-19T21:38:44+00:00 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 2017-07-26T15:43:59+00:00 Scott Moser smoser@brickies.net 2017-07-26T14:51:20+00:00 urn:sha1:8a5296c41db45be3a172862f324ad44e732a2250 The change here fixes the build of CentOS 7 rpm. The systemd 'drop-in' file systemd-fsck@.service.d/cloud-init.conf is not expected to work on CentOS at the moment. There, the cloud-init-local.service currently runs without DefaultDependencies=no. That would likely cause a dependency loop. The drop-in was added for bug 1691489. It may well be needed at a later date in CentOS also. 2017-07-19T21:52:32+00:00 Ryan Harper ryan.harper@canonical.com 2017-06-13T14:06:41+00:00 urn:sha1:dcbe479575fac9f293c5c4089f4bcb46ab887206 Under el7, cloud-init systemd files need some unit tweaks to ensure they run at the right time. Pull in current el7 downstream systemd unit changes. 2017-06-14T02:13:34+00:00 Chad Smith chad.smith@canonical.com 2017-06-07T23:26:52+00:00 urn:sha1:744e648eaf6325758282ef23bffcc4194faa6bac This change adds a couple of makefile targets for ci environments to install all necessary dependencies for package builds and test runs. It adds a number of arguments to ./tools/read-dependencies to facilitate reading pip dependencies, translating pip deps to system package names and optionally installing needed system-package dependencies on the local system. This relocates all package dependency and translation logic into ./tools/read-dependencies instead of duplication found in packages/brpm and packages/bddeb. In this branch, we also define buildrequires as including all runtime requires when rendering cloud-init.spec.in and debian/control files because our package build infrastructure will also be running all unit test during the package build process so we need runtime deps at build time. Additionally, this branch converts packages/(redhat|suse)/cloud-init.spec.in from cheetah templates to jinja to allow building python3 envs. 2017-06-09T18:01:45+00:00 Ryan Harper ryan.harper@canonical.com 2017-06-09T15:34:58+00:00 urn:sha1:b9cd8a82ee41e235df66801a02b2244226bee5ee The typical rpm build process will examine the spec file to determine which packages should be installed in the boot root. This requires the specfile to declare that it needs system. Provide this information by checking which version in which the rpm is being built and exporting requirements for systemd. 2017-06-08T17:02:55+00:00 Scott Moser smoser@brickies.net 2017-06-07T15:32:56+00:00 urn:sha1:914822a765007be7e17539e456b3e6ff12b19442 Many changes here to get us able to build rpms on CentOS 5 or 6 and RHEL. * add 'Requires' as 'BuildRequires' also. This allows us to run cloud-init tools in the build environment, and also will allow us to run tests in the build process. * build for both systemd and upstart (centos 5) init systems. * Add 'centos' as a variant Adding the variant means we can use the 'centos' user as default on centos rather than a 'fedora' or 'rhel'. * drop argparse from the requirements. On any system other than python 2.6, having a 'requirements' that mentions argparse just causes problems. Instead we add that Requires to the spec directly. * list dependency on dmidecode (as redhat distro spec had) * remove duplicate line in files section ({_unitdir}/cloud-*) * Use rpm macros for init-system chunks and drop use of init_system variable template * Add el6 only build-req on python-argparse * python-cheetah is not required in the build environment as the the spec is already rendered. (We will soon move the spec to jinja).