33bf592f09
Why I did it why In order to apply different config across different platform, and use the code with a unified format, reuse syncd init script to init saiserver. How I did it how Reuse syncd init script How to verify it Test Test in DUT s6000 and dx010 with sonic 202205
28 lines
1.3 KiB
Makefile
28 lines
1.3 KiB
Makefile
# docker image for brcm saiserver
|
|
|
|
DOCKER_SAISERVER_BRCM = docker-saiserver$(SAITHRIFT_VER)-brcm.gz
|
|
$(DOCKER_SAISERVER_BRCM)_PATH = $(PLATFORM_PATH)/docker-saiserver-brcm
|
|
$(DOCKER_SAISERVER_BRCM)_DEPENDS += $(SAISERVER)
|
|
|
|
# Use syncd_init_common.sh to init hardware platform
|
|
SYNCD_INIT_COMMON_SCRIPT = syncd_init_common.sh
|
|
$(SYNCD_INIT_COMMON_SCRIPT)_PATH = $(SRC_PATH)/sonic-sairedis/syncd/scripts
|
|
SONIC_COPY_FILES += $(SYNCD_INIT_COMMON_SCRIPT)
|
|
|
|
$(DOCKER_SAISERVER_BRCM)_FILES += $(DSSERVE) $(BCMCMD) $(SYNCD_INIT_COMMON_SCRIPT)
|
|
$(DOCKER_SAISERVER_BRCM)_LOAD_DOCKERS += $(DOCKER_CONFIG_ENGINE_BUSTER)
|
|
SONIC_DOCKER_IMAGES += $(DOCKER_SAISERVER_BRCM)
|
|
SONIC_BUSTER_DOCKERS += $(DOCKER_SAISERVER_BRCM)
|
|
|
|
#Support two versions of saiserver
|
|
$(DOCKER_SAISERVER_BRCM)_CONTAINER_NAME = saiserver$(SAITHRIFT_VER)
|
|
|
|
$(DOCKER_SAISERVER_BRCM)_RUN_OPT += --privileged -t
|
|
$(DOCKER_SAISERVER_BRCM)_RUN_OPT += -v /host/machine.conf:/etc/machine.conf
|
|
$(DOCKER_SAISERVER_BRCM)_RUN_OPT += -v /var/run/docker-saiserver:/var/run/sswsyncd
|
|
$(DOCKER_SAISERVER_BRCM)_RUN_OPT += -v /etc/sonic:/etc/sonic:ro
|
|
$(DOCKER_SAISERVER_BRCM)_RUN_OPT += -v /host/warmboot:/var/warmboot
|
|
|
|
$(DOCKER_SAISERVER_BRCM)_BASE_IMAGE_FILES += bcmcmd:/usr/bin/bcmcmd
|
|
$(DOCKER_SAISERVER_BRCM)_BASE_IMAGE_FILES += bcmsh:/usr/bin/bcmsh
|