Ryan Chetcuti
Ryan Chetcuti
### Enhancement summary At the moment, if we want to use Postcard telemetry, we need to add the eos_cli commands. Ideally this would be supported in the `eos_cli_config_gen` data model....
# Overview At the moment, the repository offers an example AVD configuration that would configure a L3LS using CVP. However the arbitrary choices of configuration would require changes before being...
### Enhancement summary The data model for `monitor_layer1` currently required that `logging_transceiver` have either `dom` or `communication` defined to create separate commands: ``` monitor layer1 logging transceiver dom logging transceiver...
### Enhancement summary At the moment, to configure Telegraf on EOS devices using AVD, we have to add all the configuration in the `eos_cli` field. An improvement on this, if...
### Enhancement summary For a design type **mpls** , when the underlay is `isis-*` and bfd is being used, there is no easy way to have the command `isis bfd`...
# Overview I would like to propose adding linting and unittesting as a github action that would run on each branch. # Adds - a new workflow to run on...
### Enhancement summary Add support for the configuration of Connectivity Fault Management data model and associated config generation. ### Which component of AVD is impacted eos_cli_config_gen ### Use case example...
### Enhancement summary When using Priority Flow Control configuration, `custom_structured_configuration` still needs to be used to define pfc values. Ideally `eso_designs` would support the same schema of PFC as `eos_cli_config_gen`...
### Enhancement summary Once ECN configuration is supported by `eos_cli_config_gen`, currently proposed in #2770, the schema & keys should be support the ECN configuration. Ideally this would also make it...
### Enhancement summary In large fabrics, a large number of endpoints may be dual homed to two leafs. Currently in AVD this has to be done via individual configuration for...