Merge ~raharper/cloud-init:fix/netplan-ipv6-mtu into cloud-init:master
Status: | Merged |
---|---|
Approved by: | Ryan Harper |
Approved revision: | 8f46b8a1c633f8a6b112a92ccb2ba34268971dfa |
Merge reported by: | Server Team CI bot |
Merged at revision: | not available |
Proposed branch: | ~raharper/cloud-init:fix/netplan-ipv6-mtu |
Merge into: | cloud-init:master |
Diff against target: |
190 lines (+54/-10) 3 files modified
cloudinit/cmd/devel/net_convert.py (+2/-0) cloudinit/net/netplan.py (+27/-8) tests/unittests/test_net.py (+25/-2) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Server Team CI bot | continuous-integration | Approve | |
Dan Watkins | Approve | ||
Review via email: mp+374627@code.launchpad.net |
Commit message
net/netplan: use ipv6-mtu key for specifying ipv6 mtu values
netplan introduced an 'info' subcommand which emits yaml describing
implemented features that indicate new or changed fields and values
in the yaml that it accepts. Previously, cloud-init emitted the key
'mtu6' for ipv6 MTU values. This is not correct and netplan will
fail to parse these values. Netplan as of 0.98 supports both the
info subcommand and the ipv6-mtu key.
This branch modifies the netplan renderer to collect the netplan
info output into a 'features' property which is a list of available
feature flags which the renderer can use to modify its output. If
the command is not available, no feature flags are set and
cloud-init will render IPv6 MTU values just as MTU for the subnet.
One inline question, but the main implementation LGTM.