(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=crux 2021-02-13T21:16:49+00:00 2021-02-13T21:16:49+00:00 zsdc taras@vyos.io 2021-02-13T17:56:29+00:00 urn:sha1:b481bfb90b96c70d5d7c988b111058137b1ca60e After the commit 377d1bbbdd45aad25c36ab15ce15c93a39df4ce9 dhclient should be run by Cloud-init properly even without calls from datasources, if this is necessary. This change solves the problems caused by always active dhclient on eth0 interface when Ec2, GCE, or Azure datasource is used. 2019-12-03T13:30:28+00:00 Kim Hagen kim.sidney@gmail.com 2019-12-03T13:24:10+00:00 urn:sha1:e71ea889ff0b3904c1d39f2f7c9ce608f63e047a 2019-11-12T14:43:05+00:00 Kim Hagen kim.sidney@gmail.com 2019-11-12T14:43:05+00:00 urn:sha1:e8f7f71683b752956e7c3fc7113b787527217eea 2019-04-15T13:19:14+00:00 Kim Hagen kim.sidney@gmail.com 2019-04-15T13:19:14+00:00 urn:sha1:0bbc3eb3a1de27fae09c478775c2e4d8c6f02f31 2019-02-28T20:20:31+00:00 Kim Hagen kim.sidney@gmail.com 2019-02-28T20:20:31+00:00 urn:sha1:45b8ef0342b4254844cd46d5b94b10972ea9eec7 2019-01-23T12:22:45+00:00 Scott Moser smoser@ubuntu.com 2018-12-20T20:52:05+00:00 urn:sha1:65318379314278e19eb990d58000c5c66b08da24 Transport functions (transport_iso9660 and transport_vmware_guestinfo) would return a tuple of 3 values, but only the first was ever used outside of test. The other values (device and filename) were just ignored. This just simplifies the transport functions to now return content (in string format) or None indicating that the transport was not found. 2019-01-23T12:22:33+00:00 Scott Moser smoser@ubuntu.com 2018-12-20T17:22:45+00:00 urn:sha1:d7952d075666122f480f0a5820ac01dfbaa7da1a This adds support for reading OVF information over the 'com.vmware.guestInfo' tranport. The current implementation requires vmware-rpctool be installed in the system. LP: #1807466 2019-01-23T12:20:25+00:00 Kim Hagen kim.sidney@gmail.com 2019-01-23T12:20:25+00:00 urn:sha1:c4da1a5cddacaa7c2a15df9170f21c3fce78fb15 release 18.5 Bump the version on cloudinit/version.py to be 18.5 and update ChangeLog LP: #1808380 Conflicts: config/cloud.cfg.tmpl 2018-12-03T22:06:47+00:00 Scott Moser smoser@ubuntu.com 2018-12-03T22:06:47+00:00 urn:sha1:adbd950af07a4b613a14bd83049915abdd6ca348 NoCloud's 'network-config' file was originally expected to contain network configuration without the top level 'network' key. This was because the file was named 'network-config' so specifying 'network' seemed redundant. However, JuJu is currently providing a top level 'network' config when it tries to disable networking ({"network": {"config": "disabled"}). Other users have also been surprised/confused by the fact that a network config in /etc/cloud/cloud.cfg.d/network.cfg differed from what was expected in 'network-config'. LP: #1798117 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