<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/net/tests, branch 20.1</title>
<subtitle> (mirror of https://github.com/marekm72/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=20.1</id>
<link rel='self' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=20.1'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/'/>
<updated>2020-01-29T21:55:39+00:00</updated>
<entry>
<title>Replace mock library with unittest.mock (#186)</title>
<updated>2020-01-29T21:55:39+00:00</updated>
<author>
<name>Daniel Watkins</name>
<email>oddbloke@ubuntu.com</email>
</author>
<published>2020-01-29T21:55:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=5f8f85bb38cc972d3d2c705a1ec73db3f690f323'/>
<id>urn:sha1:5f8f85bb38cc972d3d2c705a1ec73db3f690f323</id>
<content type='text'>
* cloudinit: replace "import mock" with "from unittest import mock"

* test-requirements.txt: drop mock

Co-authored-by: Chad Smith &lt;chad.smith@canonical.com&gt;
</content>
</entry>
<entry>
<title>dhcp: Support RedHat dhcp rfc3442 lease format for option 121 (#76)</title>
<updated>2019-12-10T00:48:37+00:00</updated>
<author>
<name>Eric Lafontaine</name>
<email>eric.lafontaine@bell.ca</email>
</author>
<published>2019-12-10T00:48:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=a47405af306219d804ed262d6f7e2039a75883f2'/>
<id>urn:sha1:a47405af306219d804ed262d6f7e2039a75883f2</id>
<content type='text'>
RedHat dhcp client writes out rfc3442 classless-static-routes in a different format[1]
than what is found in isc-dhcp clients.  This patch adds support for the RedHat format.

1. Background details on the format
 https://bugzilla.redhat.com/show_bug.cgi?id=516325
 https://github.com/vaijab/fedora-dhcp/blob/e83fb19c51765442d77fa60596bfdb2b3b9fbe2e/dhcp-rfc3442-classless-static-routes.patch#L252 
 https://github.com/heftig/NetworkManager/blob/f56c82d86122fc45304fc829b5f1e4766ed51589/src/dhcp-manager/nm-dhcp-client.c#L978

LP: #1850642</content>
</entry>
<entry>
<title>network_state: handle empty v1 config (#45)</title>
<updated>2019-12-07T04:11:12+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2019-12-07T04:11:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=34ec440c1ad61c23c34b46f1798813d0f3ada952'/>
<id>urn:sha1:34ec440c1ad61c23c34b46f1798813d0f3ada952</id>
<content type='text'>
Sending a valid but empty v1 network config resulted in a
stacktrace during execution.  Update the network_state
parse path to specific check if the 'config' key is None
(not present) versus being present but explicitly empty.
Also add some network_state unittests.

LP: #1852496</content>
</entry>
<entry>
<title>get_interfaces: don't exclude bridge and bond members</title>
<updated>2019-10-04T15:34:41+00:00</updated>
<author>
<name>Daniel Watkins</name>
<email>oddbloke@ubuntu.com</email>
</author>
<published>2019-10-04T15:34:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=a7d8d032a65e807007f1467a9220b7f161625668'/>
<id>urn:sha1:a7d8d032a65e807007f1467a9220b7f161625668</id>
<content type='text'>
The change that introduced this issue was handling interfaces that are
bonded in the kernel, in a way that doesn't present as "a bond" to
userspace in the normal way.  Both members of this "bond" will share a
MAC address, so we filter one of them out to avoid incorrect MAC address
collision warnings.

Unfortunately, the matching condition was too broad, so that change also
affected normal bonds and bridges.  This change specifically excludes
bonds and bridges from that determination, to address that regression.

LP: #1846535
</content>
</entry>
<entry>
<title>net: add is_master check for filtering device list</title>
<updated>2019-09-17T10:11:00+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2019-09-17T10:11:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=059d049c57cac02cdeaca832233a19712e0b4ded'/>
<id>urn:sha1:059d049c57cac02cdeaca832233a19712e0b4ded</id>
<content type='text'>
Some network devices are transformed into a bond via kernel magic
and do not have the 'bonding' sysfs attribute, but like a bond they
have a duplicate MAC of other bond members.  On Azure Advanced
Networking SRIOV devices are auto bonded and will have the same MAC
as the HyperV nic.  We can detect this via the 'master' sysfs attribute
in the device sysfs path and this patch adds this to the list of devices
we ignore when enumerating device lists.

LP: #1844191
</content>
</entry>
<entry>
<title>net,Oracle: Add support for netfailover detection</title>
<updated>2019-09-09T21:13:01+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2019-09-09T21:13:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=fa47d527a03a00319936323f0a857fbecafceaf7'/>
<id>urn:sha1:fa47d527a03a00319936323f0a857fbecafceaf7</id>
<content type='text'>
Add support for detecting netfailover[1] device 3-tuple in networking
layer.  In the Oracle datasource ensure that if a provided network
config, either fallback or provided config includes a netfailover master
to remove any MAC address value as this can break under 3-netdev
as the other two devices have the same MAC.

1. https://www.kernel.org/doc/html/latest/networking/net_failover.html
</content>
</entry>
<entry>
<title>azure/net: generate_fallback_nic emits network v2 config instead of v1</title>
<updated>2019-08-13T20:13:05+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2019-08-13T20:13:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=7f674256c1426ffc419fd6b13e66a58754d94939'/>
<id>urn:sha1:7f674256c1426ffc419fd6b13e66a58754d94939</id>
<content type='text'>
The function generate_fallback_config is used by Azure by default when
not consuming IMDS configuration data. This function is also used by any
datasource which does not implement it's own network config. This simple
fallback configuration sets up dhcp on the most likely NIC. It will now
emit network v2 instead of network v1.

This is a step toward moving all components talking in v2 and allows us
to avoid costly conversions between v1 and v2 for newer distributions
which rely on netplan.
</content>
</entry>
<entry>
<title>net: update net sequence, include wait on netdevs, opensuse netrules path</title>
<updated>2019-07-17T20:23:42+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2019-07-17T20:23:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=b3a87fc0a2c88585cf77fa9d2756e96183c838f7'/>
<id>urn:sha1:b3a87fc0a2c88585cf77fa9d2756e96183c838f7</id>
<content type='text'>
On systems with many interfaces, processing udev events may take a while.
Cloud-init expects devices included in a provided network-configuration
to be present when attempting to configure them.  This patch adds a step
in net configuration where it will check for devices provided in the
configuration and if not found, issue udevadm settle commands to wait
for them to appear.

Additionally, the default path for udev persistent network rules
70-persistent-net.rules may also be written to systems which include
the 75-net-generator.rules.  During boot, cloud-init and the
generator may race and interleave values causing issues.  OpenSUSE
will now use a newer file, 85-persistent-net-cloud-init.rules which
will take precedence over values created by 75-net-generator and
avoid collisions on the same file.

LP: #1817368
</content>
</entry>
<entry>
<title>net: add rfc3442 (classless static routes) to EphemeralDHCP</title>
<updated>2019-07-16T22:40:15+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2019-07-16T22:40:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=07b17236be5665bb552c7460102bcd07bf8f2be8'/>
<id>urn:sha1:07b17236be5665bb552c7460102bcd07bf8f2be8</id>
<content type='text'>
The EphemeralDHCP context manager did not parse or handle
rfc3442 classless static routes which prevented reading
datasource metadata in some clouds.  This branch adds support
for extracting the field from the leases output, parsing the
format and then adding the required iproute2 ip commands to
apply (and teardown) the static routes.

LP: #1821102
</content>
</entry>
<entry>
<title>git tests: no longer show warning about safe yaml.</title>
<updated>2019-04-27T02:40:47+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2019-04-27T02:40:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=784d3300f213c78d197a7ac8ad42cb098fd82356'/>
<id>urn:sha1:784d3300f213c78d197a7ac8ad42cb098fd82356</id>
<content type='text'>
Currently on 18.04, running tox -e py27 will spew errors like:
.tests/unittests/test_net.py:2649: YAMLLoadWarning: calling yaml.load()
without Loader=... is deprecated, as the default Loader is unsafe.
Please read https://msg.pyyaml.org/load for full details.

The change here just uses cloud-init's yaml, which does safeloading
by default.
</content>
</entry>
</feed>
