(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=circinus-public-unmaintained 2021-12-16T02:16:38+00:00 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-07-01T19:43:07+00:00 James Falcon therealfalcon@gmail.com 2021-07-01T19:43:07+00:00 urn:sha1:81299de5fe3b6e491a965a6ebef66c6b8bf2c037 Currently _bring_up_interfaces() is a no-op for any distro using renderers. We need to be able to support bringing up a single interfaces, a list of interfaces, and all interfaces. This should be independent of the renderers, as the network config is often generated independent of the mechanism used to apply it. Additionally, I included a refactor to remove "_supported_write_network_config". We had a confusing call chain of apply_network_config->_write_network_config->_supported_write_network_config. The last two have been combined. 2021-06-18T16:53:44+00:00 sshedi 53473811+sshedi@users.noreply.github.com 2021-06-18T16:53:44+00:00 urn:sha1:35aa9db6f8e2ba05d366776c0e8d97f52217e930 Also added a new (currently experimental) systemd-networkd renderer, and includes a small refactor to cc_resolv_conf.py to support the resolved.conf used by systemd-resolved. 2021-01-07T16:14:10+00:00 Daniel Watkins oddbloke@ubuntu.com 2021-01-07T16:14:10+00:00 urn:sha1:75eb007f68d3a75c094f0daccd66eb412359e78e 2020-01-28T15:45:27+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-01-28T15:45:27+00:00 urn:sha1:88b09643787c55b700cfadc25bbe0ddbfe0368e6 2019-10-24T20:16:47+00:00 Ryan Harper ryan.harper@canonical.com 2019-10-24T20:16:47+00:00 urn:sha1:f1c788e2bb7c86069d43a015267facfb8aefcdf0 netplan introduced an 'info' subcommand which emits yaml describing implemented features that indicate new or changed fields and values in the yaml that it accepts. Previously, cloud-init emitted the key 'mtu6' for ipv6 MTU values. This is not correct and netplan will fail to parse these values. Netplan as of 0.98 supports both the info subcommand and the ipv6-mtu key. This branch modifies the netplan renderer to collect the netplan info output into a 'features' property which is a list of available feature flags which the renderer can use to modify its output. If the command is not available, no feature flags are set and cloud-init will render IPv6 MTU values just as MTU for the subnet. 2019-10-24T20:02:15+00:00 Scott Moser smoser@brickies.net 2019-10-24T20:02:15+00:00 urn:sha1:5bec6b0e2a2ce5fd03bb04f441536fc130e67997 Here we replace uses of the pyyaml module directly with functions provided by cloudinit.safeyaml. Also, change/move cloudinit.util.yaml_dumps to cloudinit.safeyaml.dumps LP: #1849640 2018-12-03T18:43:21+00:00 Ryan Harper ryan.harper@canonical.com 2018-12-03T18:43:21+00:00 urn:sha1:cb44ad6f42ac015d7d8eaf2ab0bb5ab125ed04b6 Move routes under the nic's subnet rather than use top-level ("global") route config ensuring all net renderers will provide the configured route. Also updated cloudinit/cmd/devel/net_convert.py:  - Add input type 'vmware-imc' for OVF customization config files  - Fix bug when output-type was netplan which invoked netplan   generate/apply and attempted to write to   /etc/netplan/50-cloud-init.yaml instead of joining with the   output directory. LP: #1806103 2018-09-05T14:17:16+00:00 Ryan Harper ryan.harper@canonical.com 2018-09-05T14:17:16+00:00 urn:sha1:db50bc0d999e3a90136864a774f85e4e15b144e8 Multiple distros use sysconfig format but have different content and paths to certain files. Update distros to specify these template paths in their renderer_configs dictionary. 2018-08-17T20:24:58+00:00 Chad Smith chad.smith@canonical.com 2018-08-17T20:24:58+00:00 urn:sha1:47548df9ded4ad4088d3d846f1876b29b16aa7d1 Azure datasource now queries IMDS metadata service for network configuration at link local address http://169.254.169.254/metadata/instance?api-version=2017-12-01. The azure metadata service presents a list of macs and allocated ip addresses associated with this instance. Azure will now also regenerate network configuration on every boot because it subscribes to EventType.BOOT maintenance events as well as the 'first boot' EventType.BOOT_NEW_INSTANCE. For testing add azure-imds --kind to cloud-init devel net_convert tool for debugging IMDS metadata. Also refactor _get_data into 3 discrete methods:   - is_platform_viable: check quickly whether the datasource is     potentially compatible with the platform on which is is running   - crawl_metadata: walk all potential metadata candidates, returning a     structured dict of all metadata and userdata. Raise InvalidMetaData on     error.   - _get_data: call crawl_metadata and process results or error. Cache     instance data on class attributes: metadata, userdata_raw etc.