(mirror of https://github.com/marekm72/vyos-cloud-init.git) https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=crux 2019-01-23T12:22:45+00:00 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 2018-12-11T23:05:39+00:00 Joshua Powers josh.powers@canonical.com 2018-12-11T23:05:39+00:00 urn:sha1:e1da348a968567a765c34a8c6f04f6ea9930721b 2018-12-11T17:24:11+00:00 Ryan Harper ryan.harper@canonical.com 2018-12-11T17:24:11+00:00 urn:sha1:6aef6c7d402b17ebc04516a088a91f8e6ed86510 It is possible to have a metric value in a per-subnet route. This is currently missing in all renderers. Update each renderer to emit the correct metric value from the config. LP: #1805871 2018-12-06T18:26:32+00:00 James Baxter j.w.baxter@gmail.com 2018-12-06T18:26:32+00:00 urn:sha1:a4007d063f96b82545aa678ef2cb472ea3b48b1e Add 'append: true' to write_files entries to append 'content' to file specified by 'path' key. This modifies the file open mode to append. 2018-12-03T22:07:59+00:00 Scott Moser smoser@ubuntu.com 2018-12-03T22:07:59+00:00 urn:sha1:230e67ebd489c0d895243a2fc66ca95af2cea13b I noticed a bug in dhclient_hook on the 'down' event, using 'is' operator rather than '==' (if self.net_action is 'down'). This refactors/simplifies the code a bit for easier testing and adds tests. The reason for the rename of 'action' to 'event' is to just be internally consistent. The word and Namespace 'action' is used by cloud-init main, so it was not really usable here. Also adds a main which can easily be debugged with: CI_DHCP_HOOK_DATA_D=./my.d python -m cloudinit.dhclient_hook up eth0 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 2018-11-29T21:53:18+00:00 Tamilmani Manoharan tamanoha@microsoft.com 2018-11-29T21:53:18+00:00 urn:sha1:bf7917159dbb292c9fcdef82b004e0f5ecb32c16 Replace Azure pre-provision polling on IMDS with a blocking call which watches for netlink link state change messages. The media change event happens when a pre-provisioned VM has been activated and is connected to the users virtual network and cloud-init can then resume operation to complete image instantiation. 2018-11-28T18:23:33+00:00 Scott Moser smoser@ubuntu.com 2018-11-28T18:23:33+00:00 urn:sha1:4ce8a2858dffcb1f9518b50d884b341f68ac5e63 The order of parameters to test_handle_zfs_root did not match the order of the mocks applied. Thanks to Jason Zions for pointing this out.