(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling 2022-02-12T04:40:45+00:00 2022-02-12T04:40:45+00:00 Chris Patterson cpatterson@microsoft.com 2022-02-12T04:40:45+00:00 urn:sha1:0b41b359a70bbbf3a648862a9b849d60b9ff6c3b Raise runtime errors for unhandled cases which would cause other exceptions. Ignore types for a few cases where a non-trivial refactor would be required to prevent the warning. Signed-off-by: Chris Patterson <cpatterson@microsoft.com> 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-16T02:16:38+00:00 James Falcon james.falcon@canonical.com 2021-12-16T02:16:38+00:00 urn:sha1:bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf Applied Black and isort, fixed any linting issues, updated tox.ini and CI. 2021-12-07T14:23:45+00:00 Haruki TSURUMOTO fortune.rocket42@gmail.com 2021-12-07T14:23:45+00:00 urn:sha1:0ed00ad9cdebc2d4dabd8bd6d7c901584963def5 2021-12-03T04:36:37+00:00 James Falcon james.falcon@canonical.com 2021-12-03T04:36:37+00:00 urn:sha1:ffa6fc88249aa080aa31811a45569a45e567418a Given that there are additional network management tools that we haven't yet supported with activators, we should log a warning and continue without network activation here, especially since this was a no-op for years. LP: #1948681 2021-10-28T18:08:53+00:00 Daniel Watkins oddbloke@ubuntu.com 2021-10-28T18:08:53+00:00 urn:sha1:d4fe4bf5d5a09747bc8e5faed13356210fb89a32 This was fixed in 1bbc4908ff7a2be19483811b3b6fee6ebc916235 2021-10-20T20:58:27+00:00 Andy Fiddaman omnios@citrus-it.co.uk 2021-10-20T20:58:27+00:00 urn:sha1:8c89009e75c7cf6c2f87635b82656f07f58095e1 Various modules restart services and they all have logic to try and detect if they are running on a system that needs 'systemctl' or 'service', and then have code to decide which order the arguments need to be etc. On top of that, not all modules do this in the same way. The duplication and different approaches are not ideal but this also makes it hard to add support for a new distribution that does not use either 'systemctl' or 'service'. This change adds a new manage_service() method to the distro class and updates several modules to use it. 2021-10-07T16:27:36+00:00 James Falcon james.falcon@canonical.com 2021-10-07T16:27:36+00:00 urn:sha1:9c147e8341e287366790e60658f646cdcc59bef2 In #919 (81299de), we refactored some of the code used to bring up networks across distros. Previously, the call to bring up network interfaces during 'init' stage unintentionally resulted in a no-op such that network interfaces were NEVER brought up by cloud-init, even if new network interfaces were found after crawling the metadata. The code was altered to bring up these discovered network interfaces. On ubuntu, this results in a 'netplan apply' call during 'init' stage for any ubuntu-based distro on a datasource that has a NETWORK dependency. On GCE, this additional 'netplan apply' conflicts with the google-guest-agent service, resulting in an instance that can no be connected to. This commit adds a 'disable_network_activation' option that can be enabled in /etc/cloud.cfg to disable the activation of network interfaces in 'init' stage. LP: #1938299 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/