Feat(eos_designs): Interface "LACP Fallback Individual" Support

[bjmeuer]

Change Summary

Adding "LACP Fallback Individual" to the eos_designs. This is a common requirement for automated server deployments in order to bootstrap bare-metal servers via a different VLAN or interface type (for example) than is configured against the port-channel interface. Also adding the ability to specify different interface configuration parameters at the member interface level than are specified at the port-channel level by using port_profiles.

Related Issue(s)

Fixes #3367

Component(s) name

arista.avd.eos_designs

Proposed changes

The option "individual" was added to the "mode" key of the lacp_fallback setting. Additionally added the setting "individual" with the key "profile" where you can reference a port_profile from which you want to inherit configuration for the member interfaces. The following config from a port_profile will be inherited: mode, vlans, native_vlan, native_vlan_tag.

servers:
  - name: server1
    adapters:
    - switch_ports: ['Ethernet10/1', 'Ethernet10/1']
      ...
        lacp_fallback: 
          mode: individual
          individual:
            profile: ESX_TRUNK

How to test

From the molecule tests:

servers:
  # port-channel with lacp fallback individual
  - name: INDIVIDUAL_1
    adapters:
      - switches: [connected_endpoints, connected_endpoints]
        switch_ports: [Ethernet12, Ethernet13]
        port_channel:
          mode: "active"
          description: "INDIVIDUAL_1"
          lacp_fallback:
            mode: individual
  # port-channel with lacp fallback individual and profile for member interfaces
  - name: INDIVIDUAL_2
    adapters:
      - switches: [connected_endpoints, connected_endpoints]
        switch_ports: [Ethernet14, Ethernet15]
        port_channel:
          mode: "active"
          description: "INDIVIDUAL_2"
          lacp_fallback:
            mode: individual
            individual:
              profile: INDIVIDUAL_TRUNK

port_profiles:
  - profile: INDIVIDUAL_TRUNK
    mode: trunk
    vlans: "1,2,3,4,5,6,7,123,234"
    native_vlan_tag: False
    native_vlan: 123

Checklist

User Checklist

• N/A

Repository Checklist

• My code has been rebased from devel before I start
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation and documentation have been updated accordingly.
• I have updated molecule CI testing accordingly. (check the box if not applicable)

[ClausHolbechArista]

Minor code optimization. Done by hand so may require linting.

[ankudinov]

LGTM. Tested various combinations in Codespace