(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling 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. 2021-01-01T12:58:15+00:00 Kim Wittenburg codello@wittenburg.kim 2021-01-01T12:58:15+00:00 urn:sha1:3980057ce140ea6896cd3f7cd4299cfd29cf234a The `write_files` module allows to provides files to the system at deployment. This can be useful for situations when they are required to make a configuration valid, for example - security keys, certificates, etc. 2020-12-25T15:32:44+00:00 zsdc taras@vyos.io 2020-11-13T21:20:41+00:00 urn:sha1:1607eec32641ad93ea211e447336b3366c28de06 With the new `cc_vyos_userdata.py` module is possible to set in User-Data (`#cloud-config`) new parameter `vyos_config_commands`. This parameter should be a list of VyOS configuration commands that will be applied during deployment. The module will run after the Meta-Data module `cc_vyos.py`. Commands requirements: - one command per line - if command ending by value, it must be inside single quotes: `set some option 'value'`, `delete some option 'value'` - a single-quote symbol is not allowed inside command or value The commands list produced by the `show configuration commands` command on a VyOS router should comply with all the requirements, so it is easy to get a proper commands list by copying it from another router. Usage example (User-Data content): ``` #cloud-config vyos_config_commands: - set system host-name 'demo123' - set system ntp server 1.pool.ntp.org - set system ntp server 2.pool.ntp.org - delete interfaces ethernet eth2 address - set interfaces ethernet eth2 address '192.0.2.1/24' ``` 2020-11-04T22:13:00+00:00 zsdc taras@vyos.io 2020-11-04T16:31:58+00:00 urn:sha1:d0ec0c1800097250594a17e88cae28b423a8eff2 Since partition size is hardcoded into VyOS images for virtual environments, it is not impossible to use all available space on storage. This change enables two Cloud-init modules: - `growpart` to grow persistence partition; - `resizefs_vyos` to resize filesystem size to the whole partition. The `resizefs_vyos` module forked from the main `resizefs` to allow resizing not only root partition but any custom also. 2020-09-15T14:05:20+00:00 zsdc taras@vyos.io 2020-09-15T14:05:20+00:00 urn:sha1:7cd260b313267dc7123cb99a75d4555e24909cca Merged with 20.3 tag from the upstream Cloud-init repository 2020-09-09T17:57:38+00:00 zsdc taras@vyos.io 2020-09-09T17:57:38+00:00 urn:sha1:06bd421e2ce84f9a97e28070fede86cb2be18457 VyOS-specific configuration were moved from the `cloud.cfg.tmpl` to the separated file `cloud.cfg.d/10_vyos.cfg`. With changes in the default template, some build tests failed, and everything from this default configuration can be overwritten in the config file, so there is no strict necessity to keep our changes in the configuration template. 2020-06-12T19:48:53+00:00 James Falcon TheRealFalcon@users.noreply.github.com 2020-06-12T19:48:53+00:00 urn:sha1:287bfca19d8ed386cd41dbc47753b7711ac1c848 On a system with a non-utf8 default locale, the logger will silently not log anything if the message contains an unsupported character. 2019-12-13T15:06:19+00:00 Joshua Powers josh.powers@canonical.com 2019-12-12T18:42:58+00:00 urn:sha1:7765aac637a757c736674b0eb2e2993c01442dbc Update README to specify that only files with the '.cfg' extension are read in this folder. LP: #1855006 2016-11-22T19:28:58+00:00 Joshua Harlow jxharlow@godaddy.com 2016-07-25T19:36:30+00:00 urn:sha1:11b1aba4597379051e6b934e2b8f5a455e26ef14 Instead of being dependent on the availability of syslog that various distributions may not enable or configure correctly or they do so via patches just use a known-to-work default logging mechanism. If distros want to change this, that is fine, but at least the built-in one will work reliably. LP: #1643990