yaml: add "critical" boolean field which can be set for remote-root scenarios
'critical: true' in YAML would set "CriticalConnection=true" in
systemd-networkd config; this is useful for remote-root scenarios where
restarting networkd would otherwise risk releasing the IP from the DHCP server,
leading to a hung system.
accept-ra: do not enable by default, default to unset
Do not always emit an IPv6AcceptRA value into network configurations.
Systemd-networkd defaults to kernel value as long as the value stays
unset in the configuration. When IPv6AcceptRA is enabled in systemd
this makes networkd wait 10 seconds for potential RAs to arrive. This
delays boot by 10 seconds always whether or not the network has an
IPV6 Router running. Leaving things unsets keeps existing behavior
of Ubuntu systems where RAs are accepted and processed at the time
they are received and boot is not delayed by waiting for an RA to arrive.
If users want to forcibly enable or disable, they may do so by including
a value for accept-ra in their yaml configuraion.
* tests/integration.py: Do a better cleanup for bridge-based tests; should
fix instability with test_mix_bridge_on_bond.
* tests/integration.py: Adjust autopkgtests to account for default behavior
change for up/down delay, arp interval, mii interval introduced in the
last upload.
bonds: default to milliseconds for unspecified values in intervals
Linux kernel bond parameter settings are exclusively in millisecond
units, save lp_interval which is in seconds. Existing configurations and
documentation indicate values for mii-monitor-interval, arp-interval,
up-delay and down-delay are expressed in milliseconds. Netplan will render
these values as milliseconds in the networkd backend unless a user has
indicated a different time unit by appending a suffix, like 's' for seconds.
