Some ifupdown/ifenslave parameters have no netplan equivalent

[Mike Pontillo]

Today I went through and compared the `ifenslave`-handled parameters, with what is available in Netplan. I found that the following paramters have no netplan equivalent:

    bond-active-slave
    bond-fail-over-mac*
    bond-master
    bond-num-unsol-na**
    bond-primary
    bond-queue-id
    bond-slaves
    bond-use-carrier

Which of these parameters should be added to netplan, and which might be calculated implicitly by the existing netplan modeling?

*: netplan allows a fail-over-mac-policy, but it looks like ifupdown allows a specific failover MAC to be specified. So for this one, we could most likely derive the user's intent (unless they got the MAC wrong, in which case the config would be broken anyway).

**: It wouldn't be terrible to use the current netplan 'gratuitous-arp' parameter for this, but ifupdown allows a separate setting for IPv4 ARP and IPv6 neighbour solicitation. (Should netplan simply use the IPv4 configuration to IPv6, or should it be kept separate?)

I've pasted the full mapping below[1], just for your information.

ifenslave_to_netplan = {
    # The keys in this dictionary match what is understood by ifupdown, via
    # the `ifenslave` pacakge. The values represent their netplan equivalents.
    # The most current netplan documentation can be found at:
    # https://git.launchpad.net/netplan/tree/doc/netplan.md
    # Last updated:
    # ifenslave-2.7ubuntu1 (See README.Debian, ifenslave.if-pre-up)
    # netplan git: e41215b (See doc/netplan.md)
    "bond-ad-select": "ad-select",
    "bond-arp-interval": "arp-interval",
    # Note: this can be a list. (and must be a list in netplan)
    "bond-arp-ip-target": "arp-ip-targets",
    "bond-arp-validate": "arp-validate",
    "bond-downdelay": "down-delay",
    "bond-give-a-chance": "up-delay",
    "bond-lacp-rate": "lacp-rate",
    "bond-miimon": "mii-monitor-interval",
    "bond-mode": "mode",
    "bond-num-grat-arp": "gratuitous-arp",
    "bond-primary-reselect": "primary-reselect-policy",
    "bond-updelay": "up-delay",
    "bond-xmit-hash-policy": "transmit-hash-policy",
    # The following parameters were found in the docs, but don't
    # appear to be used in the ifenslave package:
    "bond-packets-per-slave": "packets-per-slave",
    # These parameters are available in Netplan, but not documented
    # in `ifenslave`:
    "bond-all-slaves-active": "all-slaves-active",
    "bond-arp-all-targets": "arp-all-targets",
    "bond-fail-over-mac-policy": "fail-over-mac-policy",
    "bond-learn-packet-interval": "learn-packet-interval",
    "bond-min-links": "min-links",
    # The following parameters are not documented or defined in Netplan:
    "bond-active-slave": None,
    "bond-fail-over-mac": None,
    "bond-master": None,
    "bond-num-unsol-na": None, # XXX: use bond-num-grat-arp?
    "bond-primary": None,
    "bond-queue-id": None,
    "bond-slaves": None,
    "bond-use-carrier": None,
}

[Mike Pontillo (mpontillo)]

I need to look deeper to see if this has a large impact on MAAS or not. My gut feeling is that this is potentially low to medium impact.

[Daniel Axtens (daxtens)]

FWIW, the kernel treats grat-arp and unsolicited-na as the same variable, so setting one sets the other.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team