a171e6c5e4
- Support for non-template based FRR configurations (BGP, route-map, OSPF, static route..etc) using config DB schema. - Support for save & restore - Jinja template based config-DB data read and apply to FRR during startup **- How I did it** - add frrcfgd service - when frr_mgmg_framework_config is set, frrcfgd starts in bgp container - when user changed the BGP or other related table entries in config DB, frrcfgd will run corresponding VTYSH commands to program on FRR. - add jinja template to generate FRR config file to be used by FRR daemons while bgp container restarted **- How to verify it** 1. Add/delete data on config DB and then run VTYSH "show running-config" command to check if FRR configuration changed. 1. Restart bgp container and check if generated FRR config file is correct and run VTYSH "show running-config" command to check if FRR configuration is consistent with attributes in config DB Co-authored-by: Zhenhong Zhao <zhenhong.zhao@dell.com>
15 lines
506 B
Django/Jinja
15 lines
506 B
Django/Jinja
{
|
|
"frr_mgmt_framework_config":
|
|
{% if "frr_mgmt_framework_config" in DEVICE_METADATA["localhost"].keys() %}
|
|
"{{ DEVICE_METADATA["localhost"]["frr_mgmt_framework_config"] }}"
|
|
{% else %}
|
|
""
|
|
{% endif %},
|
|
"docker_routing_config_mode":
|
|
{% if "docker_routing_config_mode" in DEVICE_METADATA["localhost"].keys() %}
|
|
"{{ DEVICE_METADATA["localhost"]["docker_routing_config_mode"] }}"
|
|
{% else %}
|
|
""
|
|
{% endif %}
|
|
}
|