154a6ab6c5
- 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>
14 lines
648 B
Makefile
14 lines
648 B
Makefile
# sonic-frr-mgmt-framework package
|
|
|
|
SONIC_FRR_MGMT_FRAMEWORK = sonic_frr_mgmt_framework-1.0-py3-none-any.whl
|
|
$(SONIC_FRR_MGMT_FRAMEWORK)_SRC_PATH = $(SRC_PATH)/sonic-frr-mgmt-framework
|
|
# These dependencies are only needed because they are dependencies
|
|
# of sonic-config-engine and frrcfgd explicitly calls sonic-cfggen
|
|
# as part of its unit tests.
|
|
# TODO: Refactor unit tests so that these dependencies are not needed
|
|
|
|
$(SONIC_FRR_MGMT_FRAMEWORK)_DEPENDS += $(SONIC_CONFIG_ENGINE_PY3)
|
|
$(SONIC_FRR_MGMT_FRAMEWORK)_DEBS_DEPENDS += $(PYTHON_SWSSCOMMON)
|
|
$(SONIC_FRR_MGMT_FRAMEWORK)_PYTHON_VERSION = 3
|
|
SONIC_PYTHON_WHEELS += $(SONIC_FRR_MGMT_FRAMEWORK)
|