(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=crux 2018-12-11T17:24:11+00:00 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-11-26T17:37:31+00:00 Chad Smith chad.smith@canonical.com 2018-11-26T17:37:31+00:00 urn:sha1:ef0611a51a98a273cfa37b0daeb3e9d151888b88 We add a new Optional parameter: connectivity_url This is used in __enter__ to verify if a connection already exists. If it does exist, no operations are performed. 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-10-09T17:31:33+00:00 Scott Moser smoser@ubuntu.com 2018-10-09T17:31:33+00:00 urn:sha1:00e36d3ded0b0f81f352de993036fc9f89e14a7a Previously we explicitly excluded mac address '00:00:00:00:00:00'. But then some nics (tunl0 and sit0) ended up having a mac address like '00:00:00:00'. The change here just ignores all 00[:00[:00...]]. LP: #1796917 2018-09-26T17:59:07+00:00 Mark Goddard mark@stackhpc.com 2018-09-26T17:59:07+00:00 urn:sha1:e7b0e5f72e134779cfe22cd07b09a42c22d2bfe1 OpenStack ironic references Infiniband interfaces via a 6 byte 'MAC address' formed from bytes 13-15 and 18-20 of interface's hardware address. This address is used as the ethernet_mac_address of Infiniband links in network_data.json in configdrives generated by OpenStack nova. We can use this address to map links in network_data.json to their corresponding interface names. When generating interface configuration files, we need to use the interface's full hardware address as the HWADDR, rather than the 6 byte MAC address provided by network_data.json. This change allows IB interfaces to be referenced in this dual mode - by MAC address and hardware address, depending on the context. Support TYPE=InfiniBand for sysconfig configuration of IB interfaces. 2018-09-13T22:15:39+00:00 Scott Moser smoser@ubuntu.com 2018-09-13T22:15:39+00:00 urn:sha1:12066fc8f6518d294501aa126b5332ea90c4896c On OpenStack based OVH public cloud, we got DHCP response with   fixed-address 54.36.113.86;   option subnet-mask 255.255.255.255;   option routers 54.36.112.1; The router clearly is not on the subnet. So 'ip' would fail when we tried to add the default route. The solution here is to add an explicit route on that interface to the router and then add the default route. Also add 'bgpovs' to the list of 'physical' types for OpenStack network configuration. That type is used on OVH public cloud. LP: #1792415 2018-09-05T16:02:25+00:00 Scott Moser smoser@ubuntu.com 2018-09-05T16:02:25+00:00 urn:sha1:a8dcad9ac62bb1d2a4f7489960395bad6cac9382 In many cases, cloud-init uses 'util.subp' to run a subprocess. This is not really desirable in our unit tests as it makes the tests dependent upon existance of those utilities. The change here is to modify the base test case class (CiTestCase) to raise exception any time subp is called. Then, fix all callers. For cases where subp is necessary or actually desired, we can use it via   a.) context hander CiTestCase.allow_subp(value)   b.) class level self.allowed_subp = value Both cases the value is a list of acceptable executable names that will be called (essentially argv[0]). Some cleanups in AltCloud were done as the code was being updated. 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-06T19:33:54+00:00 Scott Moser smoser@ubuntu.com 2018-08-06T19:33:54+00:00 urn:sha1:41f508da4f1e421f454136f3c84527a9911c63ff When converting network config v1 to netplan, we were not correctly rendering the 'macaddress' key on a bond. Not that the difference in spelling between v1 'mac_address' and v2 'macaddress' is intentional. Also fixed here is rendering of the macaddress for bridges. LP: #1784699 2018-06-12T15:23:08+00:00 Chad Smith chad.smith@canonical.com 2018-06-12T15:23:08+00:00 urn:sha1:c3f1ad9abd4a28c1b4c1f34db28ac72a646cdca6 When network configuration for any interface defines maximum transmission values (MTU) the netplan, eni and sysconfig renders will take into account any device-level, or subnet-level mtu values. When network configuration has conflicting device-level and ipv4 subnet mtu values, the subnet-specific value is honored and a warning will be logged about any ignored device-level setting. LP: #1774666