sonic-buildimage/rules/docker-fpm-frr.mk

# docker image for fpm-frr

DOCKER_FPM_FRR = docker-fpm-frr.gz
$(DOCKER_FPM_FRR)_PATH = $(DOCKERS_PATH)/docker-fpm-frr
$(DOCKER_FPM_FRR)_DEPENDS += $(FRR) $(FRR_SNMP) $(SWSS) $(LIBYANG)
$(DOCKER_FPM_FRR)_LOAD_DOCKERS += $(DOCKER_CONFIG_ENGINE_STRETCH)
SONIC_DOCKER_IMAGES += $(DOCKER_FPM_FRR)

$(DOCKER_FPM_FRR)_CONTAINER_NAME = bgp
$(DOCKER_FPM_FRR)_RUN_OPT += --net=host --privileged -t
$(DOCKER_FPM_FRR)_RUN_OPT += -v /etc/sonic:/etc/sonic:ro
$(DOCKER_FPM_FRR)_RUN_OPT += -v /etc/sonic/frr:/etc/frr:rw

$(DOCKER_FPM_FRR)_BASE_IMAGE_FILES += vtysh:/usr/bin/vtysh

SONIC_STRETCH_DOCKERS += $(DOCKER_FPM_FRR)
[build]: Adding support for Free-Range-Routing stack. (#510) - Extending SONiC building infrastructure to provide users with greater flexibility, by allowing them to elect a routing-stack different than the default one (quagga). The desired routing-stack will be defined in rules/config file. - As part of these changes I'm adding support for Free-Range-Routing (FRR) stack. Quagga will continue to be the default routing-stack. Signed-off-by: Rodny Molina <rodny@linkedin.com> 2017-04-20 11:12:27 -05:00			`# docker image for fpm-frr`

			`DOCKER_FPM_FRR = docker-fpm-frr.gz`
			`$(DOCKER_FPM_FRR)_PATH = $(DOCKERS_PATH)/docker-fpm-frr`
[FRR] Enable SNMP support (#2981) This is a follow-up of sonic-snmpagent PR 92 Now that licensing issues have been solved FRR is distributed with SNMP support compiled-in. This PR adds the last bits of configuration to get the frr-snmp debian packages added to the docker container and the config bits to enable the snmp module in FRR This PR brings the functionality of being able to poll bgpd for routes and peer status. Signed-off-by: Michel Moriniaux <m.moriniaux@criteo.com> 2019-06-19 03:24:42 -05:00			`$(DOCKER_FPM_FRR)_DEPENDS += $(FRR) $(FRR_SNMP) $(SWSS) $(LIBYANG)`
[docker-frr]: Move docker to stretch and add pythontools (#2819) 2019-04-25 15:21:20 -05:00			`$(DOCKER_FPM_FRR)_LOAD_DOCKERS += $(DOCKER_CONFIG_ENGINE_STRETCH)`
[build]: Adding support for Free-Range-Routing stack. (#510) - Extending SONiC building infrastructure to provide users with greater flexibility, by allowing them to elect a routing-stack different than the default one (quagga). The desired routing-stack will be defined in rules/config file. - As part of these changes I'm adding support for Free-Range-Routing (FRR) stack. Quagga will continue to be the default routing-stack. Signed-off-by: Rodny Molina <rodny@linkedin.com> 2017-04-20 11:12:27 -05:00			`SONIC_DOCKER_IMAGES += $(DOCKER_FPM_FRR)`

			`$(DOCKER_FPM_FRR)_CONTAINER_NAME = bgp`
			`$(DOCKER_FPM_FRR)_RUN_OPT += --net=host --privileged -t`
			`$(DOCKER_FPM_FRR)_RUN_OPT += -v /etc/sonic:/etc/sonic:ro`
Routing application split config support (#2286) * Routing application split config support Signed-off-by: nikos <ntriantafillis@gmail.com> * Routing application split config support Routing application split config support Signed-off-by: nikos <Nikos Triantafillis> 2018-11-26 20:19:12 -06:00			`$(DOCKER_FPM_FRR)_RUN_OPT += -v /etc/sonic/frr:/etc/frr:rw`
[build]: Adding support for Free-Range-Routing stack. (#510) - Extending SONiC building infrastructure to provide users with greater flexibility, by allowing them to elect a routing-stack different than the default one (quagga). The desired routing-stack will be defined in rules/config file. - As part of these changes I'm adding support for Free-Range-Routing (FRR) stack. Quagga will continue to be the default routing-stack. Signed-off-by: Rodny Molina <rodny@linkedin.com> 2017-04-20 11:12:27 -05:00
			`$(DOCKER_FPM_FRR)_BASE_IMAGE_FILES += vtysh:/usr/bin/vtysh`
[docker-frr]: Move docker to stretch and add pythontools (#2819) 2019-04-25 15:21:20 -05:00
			`SONIC_STRETCH_DOCKERS += $(DOCKER_FPM_FRR)`