Closed jonxstill closed 2 years ago
I think the model shoud be short_esi: auto
so we can only have one or the other. The template should be part of our templates
or maybe node_type_keys
default tree, where we point to standard templates, but allow the user to override.
I'd also consider short esi auto as default. Means, if it's missing - it's auto.
I'd also consider short esi auto as default. Means, if it's missing - it's auto.
Good idea, but since we detect A/A vs. mlag based on the presence of this key, it will require some other logic changes, which might be too much for a minor release. Let's see when Jon get started.
Enhancement summary
Provide a mechanism by which ESIs for port-channels in EVPN AA Multihoming setups can be auto-generated.
Which component of AVD is impacted
eos_designs
Use case example
At present ESIs are manually-generated by the user and configured on the relevant port-channel, for example using the short_esi variable. There should be the option to auto-generate this, for example instead of:
We could use:
Describe the solution you would like
The user should be able to choose from multiple options, for example:
The user should be able to set esi_auto_method: hash | id | user_defined. If set to user_defined, esi_auto_template must be set. auto_esi should be set to true on a port channel for this to be used.
Describe alternatives you have considered
N/A
Additional context
I will assign this to myself.
Contributing Guide