(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/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-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-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-15T22:55:42+00:00 Chad Smith chad.smith@canonical.com 2018-11-15T22:55:42+00:00 urn:sha1:8f812a15fde01173c0dd5b7e1a77b61031fd93e4 Upon URL timeout, _poll_imds is expected to re-dhcp to get updated IP configuration. We don't want to indefinitely retry because the instance likely has invalid IP configuration. LP: #1803598 2018-11-13T03:14:58+00:00 Chad Smith chad.smith@canonical.com 2018-11-13T03:14:58+00:00 urn:sha1:6062595b83e08e0f12e1fe6d8e367d8db9d91ef8 There is an infrequent race when the booting instance can hit the IMDS service before it is fully available. This results in a requests.ConnectTimeout being raised. Azure's retry_callback logic now retries on either 404s or Timeouts. LP:1800223 2018-11-12T18:43:42+00:00 Jason Zions jasonzio@microsoft.com 2018-11-12T18:43:42+00:00 urn:sha1:6f9512049bbb594c3f01ffcd2ab25ae4e016f01e If Azure detects an ntfs filesystem type during mount attempt, it should still report the resource device as reformattable. There are slight differences in error message format on RedHat and SuSE. This patch simplifies the expected error match to work on both distributions. LP: #1799338 2018-11-12T17:16:09+00:00 asakkurr asakkurr@microsoft.com 2018-11-12T17:16:09+00:00 urn:sha1:d910ecd15de642d73a36e935704e54370f93c45b In commitish 9073951 azure datasource tried to leverage stale DHCP information obtained from EphemeralDHCPv4 context manager to report updated provisioning status to the fabric earlier in the boot process. Unfortunately the stale ephemeral network configuration had already been torn down in preparation to bring up IMDS network config so the report attempt failed on timeout. This branch introduces obtain_lease and clean_network public methods on EphemeralDHCPv4 to allow for setup and teardown of ephemeral network configuration without using a context manager. Azure datasource now uses this to persist ephemeral network configuration across multiple contexts during provisioning to avoid multiple DHCP roundtrips. 2018-11-08T04:19:09+00:00 Chad Smith chad.smith@canonical.com 2018-11-08T04:19:09+00:00 urn:sha1:093f968013f418d591d9e778a57b2f050ac30db3 2018-10-31T20:19:15+00:00 asakkurr asakkurr@microsoft.com 2018-10-31T20:19:15+00:00 urn:sha1:907395104bb5850d221924365102cc5ab0eca2f1 When reusing a preprovisioned VM, report ready to Azure fabric as soon as we get the reprovision data and the goal state so that we are not delayed by the cloud-init stage switch, saving 2-3 seconds. Also reduce logging when polling IMDS for reprovision data. LP: #1799594