Support OSPF tuning/configuration parameters

[pvinci-arista]

Enhancement summary

Support ospf configuration parameters at the high-level design layer.

Which component of AVD is impacted

eos_designs

Use case example

BGP EVPN overlay over a partially-meshed routed OSPF core with a partial mesh between the cores.

Describe the solution you would like

Add keys to support tuning of ospf, at the high-level design level, similar to:

• ospf_auto_cost_reference_bandwidth
• ospf_maximum_paths
• ospf_log_adjacency_changes_detail
• ospf_max_lsa
• ospf_timers
  • lsa
    • arrival
  • out_delay
  • throttle
    • lsa
    • spf
• ospf_max_metric
  • router_lsa
    • on_startup
• ospf_bfd_adjacency_state_any

Describe alternatives you have considered

This can be rendered today using:

custom_structured_configuration_router_ospf:
  process_ids:
    100:
      bfd_enable: true
      max_lsa: 12000
      auto_cost_reference_bandwidth: 1000000
      maximum_paths: 64
      log_adjacency_changes_detail: true

Additional context

No response

Contributing Guide

• I agree to follow this project's Code of Conduct

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 15 days

[forcecity]

Would also be a good idea to support structured_config in "network services -> VRF OSPF configuration" section. But as a workaround now, we defined it at the "node type settings -> structured_config -> router_ospf -> - id" to make sure it works only for specific devices:
structured_config:
router_ospf:
process_ids:
- id: 1
auto_cost_reference_bandwidth: xxxxx

[ClausHolbechArista]

Sounds reasonable :)
Please open a new enhancement request for this, thanks.

[forcecity]

OK, I have created a new one: #4924. Thank you for your support!!