(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=cla 2024-06-07T10:27:59+00:00 2024-06-07T10:27:59+00:00 zsdc taras@vyos.io 2024-06-06T11:38:44+00:00 urn:sha1:77862f882245a62efef6095e2739d6edfb91d674 Added an unattended installer, compatible with similar from VyOS 1.3. Check the `config/cloud.cfg.d/20_vyos_install.cfg` for configuration details. 2024-05-16T00:13:51+00:00 zsdc taras@vyos.io 2024-05-16T00:12:08+00:00 urn:sha1:70304ff90d931265cb736ace692967242c9b9729 Cloud-init in environments where Meta-data is available via network configures the main interface and keeps the config in `/etc/network/interfaces.d/`. This config later interferes with the VyOS configuration. To avoid the problem previously the code in the `cc_vyos.py` module was used, but this is not enough. The module is running only once during instance deployment. But Cloud-init will re-add the config file with each boot. There are two ways to solve this incompatibility (within Cloud-init) - disable network config or perform cleanup during each boot. Disabling network config is not correct in this context, because it blocks the ability to fetch Meta-data after the first boot, which in turn blocks the ability to run per-boot modules with an updated config. Therefore, the cleanup code was extracted to an independent `cc_vyos_ifupdown.py` module that performs proper cleanup with each boot. 2022-03-25T19:42:00+00:00 zsdc taras@vyos.io 2022-03-25T18:58:01+00:00 urn:sha1:31448cccedd8f841fb3ac7d0f2e3cdefe08a53ba Merged with 22.1 tag from the upstream Cloud-init repository. Our modules were slightly modified for compatibility with the new version. 2022-01-20T22:26:02+00:00 vteratipally 67723486+vteratipally@users.noreply.github.com 2022-01-20T22:26:02+00:00 urn:sha1:2a08d592f7fbdb64452eb2da14592ae5aec806ea 2022-01-12T14:37:32+00:00 maxnet bos@je-eigen-domein.nl 2022-01-12T14:37:32+00:00 urn:sha1:5147e8d4764e368ab8ccea7433b02e4ff9d6c901 Adds a new module to allow setting keyboard layout, for use-cases in which cloud-init is used to configure OS images meant for physical computers instead of the cloud. This initial release only implements support for Linux distributions that allow layout to be set through systemd's localectl. LP: #1951593 2021-12-07T14:23:45+00:00 Haruki TSURUMOTO fortune.rocket42@gmail.com 2021-12-07T14:23:45+00:00 urn:sha1:0ed00ad9cdebc2d4dabd8bd6d7c901584963def5 2021-10-27T14:43:34+00:00 James Falcon james.falcon@canonical.com 2021-10-27T14:43:34+00:00 urn:sha1:1d01da5d9916d97ef463ba61a36b3f98f8911419 This commit removes automatically installing udev rules for hotplug and adds a module to install them instead. Automatically including the udev rules and checking if hotplug was enabled consumed too many resources in certain circumstances. Moving the rules to a module ensures we don't spend extra extra cycles on hotplug if hotplug functionality isn't desired. LP: #1946003 2021-10-25T19:31:07+00:00 Lucendio github+dev@lucendio.com 2021-10-25T19:31:07+00:00 urn:sha1:a4236c375ddf78258a8f9252c1d79c665aa4f88b The main idea is to introduce a second module that takes care of writing files, but in the 'final' stage. While the introduction of a second module would allow for choosing the appropriate place withing the order of modules (and stages), there is no addition top-level directive being added to the cloud configuration schema. Instead, 'write-files' schema is being extended to include a 'defer' attribute used only by the 'write-deffered-files' modules. The new module 'write-deferred-files' reuses as much as possible of the 'write-files' functionality. 2021-09-13T18:21:28+00:00 zhuzaifangxuele 52022596+zhuzaifangxuele@users.noreply.github.com 2021-09-13T18:21:28+00:00 urn:sha1:f4c47e3e25d1fb79e2673e37f8fc67750d025be2 openEuler Homepage: https://www.openeuler.org/en/ 2021-09-01T19:01:09+00:00 Alexandr Kravchenko sasha121196@mail.ru 2021-09-01T19:01:09+00:00 urn:sha1:f6c71fd758a3589ac5f62fd251d60b00edf5bb1c https://www.cloudlinux.com/