matthew/sonic-buildimage
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
3f3dceb96a
sonic-buildimage/platform/broadcom/docker-syncd-brcm-rpc.mk

31 lines
1.4 KiB
Makefile
Raw Normal View History

[docker-syncd-%-rpc]: Integrate syncd dockers with rpc (#431) * Build docker-syncd-*-rpc for brcm and mlnx * Fix errors * Update make files for rpc * Fix mistypes
2017-03-24 20:36:56 -05:00
# docker image for brcm syncd with rpc
DOCKER_SYNCD_BRCM_RPC = docker-syncd-brcm-rpc.gz
$(DOCKER_SYNCD_BRCM_RPC)_PATH = $(PLATFORM_PATH)/docker-syncd-brcm-rpc
[syncd-rpc.mk] install ptf dependancy (#4279) Signed-off-by: Mykola Faryma <mykolaf@mellanox.com>
2020-03-18 13:59:39 -05:00
$(DOCKER_SYNCD_BRCM_RPC)_DEPENDS += $(SYNCD_RPC) $(LIBTHRIFT) $(PTF)
[buildsystem] Install debug packages in syncd when INSTALL_DEBUG_TOOLS=y (#2702) * [buildsystem] Install debug packages in syncd when INSTALL_DEBUG_TOOLS=y Signed-off-by: Stepan Blyschak <stepanb@mellanox.com>
2019-04-18 04:25:51 -05:00
ifeq ($(INSTALL_DEBUG_TOOLS), y)
$(DOCKER_SYNCD_BRCM_RPC)_DEPENDS += $(SYNCD_RPC_DBG) \
$(LIBSWSSCOMMON_DBG) \
$(LIBSAIMETADATA_DBG) \
$(LIBSAIREDIS_DBG)
endif
[docker-syncd]: Restart SwSS, syncd and dependent services if a critical process in syncd container exits unexpectedly (#3534) Add the same mechanism I developed for the SwSS service in #2845 to the syncd service. However, in order to cause the SwSS service to also exit and restart in this situation, I developed a docker-wait-any program which the SwSS service uses to wait for either the swss or syncd containers to exit.
2019-11-09 12:26:39 -06:00
$(DOCKER_SYNCD_BRCM_RPC)_FILES += $(DSSERVE) $(BCMCMD) $(SUPERVISOR_PROC_EXIT_LISTENER_SCRIPT)
[docker-brcm-syncd]: build brcm syncd from stretch Signed-off-by: Guohan Lu <gulv@microsoft.com>
2019-05-03 04:15:54 -05:00
$(DOCKER_SYNCD_BRCM_RPC)_LOAD_DOCKERS += $(DOCKER_SYNCD_BASE)
[docker-syncd-%-rpc]: Integrate syncd dockers with rpc (#431) * Build docker-syncd-*-rpc for brcm and mlnx * Fix errors * Update make files for rpc * Fix mistypes
2017-03-24 20:36:56 -05:00
SONIC_DOCKER_IMAGES += $(DOCKER_SYNCD_BRCM_RPC)
Add ENABLE_SYNCD_RPC option (#642) Under rules/config now there's additional configuration option ENABLE_SYNCD_RPC that allows building SONIC installer with docker-syncd-*-rpc for evaluation purposes. Signed-off-by: marian-pritsak <marianp@mellanox.com>
2017-05-30 18:17:03 -05:00
ifeq ($(ENABLE_SYNCD_RPC),y)
SONIC_INSTALL_DOCKER_IMAGES += $(DOCKER_SYNCD_BRCM_RPC)
endif
$(DOCKER_SYNCD_BRCM_RPC)_CONTAINER_NAME = syncd
[dockers] change RPC, DBG dockers version: put RPG, DBG sign in build metadata part of the version (#8920) - Why I did it In case an app.ext requires a dependency syncd^1.0.0, the RPC version of syncd will not satisfy this constraint, since 1.0.0-rpc < 1.0.0. This is not correct to put 'rpc' as a prerelease identifier. Instead put 'rpc' as build metadata in the version: 1.0.0+rpc which satisfies the constraint ^1.0.0. - How I did it Changed the way how to version in RPC and DBG images are constructed. - How to verify it Install app.ext with syncd^1.0.0 dependency on a switch with RPC syncd docker. Signed-off-by: Stepan Blyshchak <stepanb@nvidia.com>
2021-11-01 12:02:57 -05:00
$(DOCKER_SYNCD_BRCM_RPC)_VERSION = 1.0.0+rpc
[dockers] label SONiC Docker with manifest (#5939) Signed-off-by: Stepan Blyschak stepanb@nvidia.com This PR is part of SONiC Application Extension Depends on #5938 - Why I did it To provide an infrastructure change in order to support SONiC Application Extension feature. - How I did it Label every installable SONiC Docker with a minimal required manifest and auto-generate packages.json file based on installed SONiC images. - How to verify it Build an image, execute the following command: admin@sonic:~$ docker inspect docker-snmp:1.0.0 | jq '.[0].Config.Labels["com.azure.sonic.manifest"]' -r | jq Cat /var/lib/sonic-package-manager/packages.json file to verify all dockers are listed there.
2021-04-26 15:51:50 -05:00
$(DOCKER_SYNCD_BRCM_RPC)_PACKAGE_NAME = syncd
[docker/brcm-syncd-rpc]: remove duplicated "--net" options in broadcom syncd rpc (#4296) In the file "files/build_templates/docker_image_ctl.j2", it adds the option "--net" to the docker create command through the commit "abe7ef7e2e2e1215c97cee19a83aab0b130cebe5" (#3856). Remove the "--net" option in "docker-syncd-brcm-rpc.mk" to avoid specifying duplicated "--net" options. Signed-off-by: charlie_chen <charlie_chen@edge-core.com>
2020-03-21 20:47:31 -05:00
$(DOCKER_SYNCD_BRCM_RPC)_RUN_OPT += --privileged -t
Add ENABLE_SYNCD_RPC option (#642) Under rules/config now there's additional configuration option ENABLE_SYNCD_RPC that allows building SONIC installer with docker-syncd-*-rpc for evaluation purposes. Signed-off-by: marian-pritsak <marianp@mellanox.com>
2017-05-30 18:17:03 -05:00
$(DOCKER_SYNCD_BRCM_RPC)_RUN_OPT += -v /host/machine.conf:/etc/machine.conf
[syncd-rpc-brcm]: Fix syncd terminated in broadcom rpc image (#3391) Signed-off-by: chiourung_huang <chiourung_huang@edge-core.com>
2019-08-28 13:55:27 -05:00
$(DOCKER_SYNCD_BRCM_RPC)_RUN_OPT += -v /host/warmboot:/var/warmboot
Add ENABLE_SYNCD_RPC option (#642) Under rules/config now there's additional configuration option ENABLE_SYNCD_RPC that allows building SONIC installer with docker-syncd-*-rpc for evaluation purposes. Signed-off-by: marian-pritsak <marianp@mellanox.com>
2017-05-30 18:17:03 -05:00
$(DOCKER_SYNCD_BRCM_RPC)_RUN_OPT += -v /var/run/docker-syncd:/var/run/sswsyncd
$(DOCKER_SYNCD_BRCM_RPC)_RUN_OPT += -v /etc/sonic:/etc/sonic:ro
[broadcom]: Add bcmcmd and bcmsh to docker-syncd-brcm-rpc (#3739) Signed-off-by: chiourung_huang <chiourung_huang@edge-core.com>
2019-11-20 09:41:04 -06:00
$(DOCKER_SYNCD_BRCM_RPC)_BASE_IMAGE_FILES += bcmcmd:/usr/bin/bcmcmd
$(DOCKER_SYNCD_BRCM_RPC)_BASE_IMAGE_FILES += bcmsh:/usr/bin/bcmsh
New sonic-buildimage images for Broadcom DNX ASIC family. (#7598) Introduce new sonic-buildimage images for Broadcom DNX ASIC family. sonic-broadcom-dnx.bin sonic-aboot-broadcom-dnx.swi How I did it NO CHANGE to existing make commands make init; make configure PLATFORM=broadcom; make target/sonic-aboot-broadcom.swi; make target/sonic-broadcom.bin The difference now is that it will result in new broadcom images for DNX asic family as well. sonic-broadcom.bin, sonic-broadcom-dnx.bin sonic-aboot-broadcom.swi, sonic-aboot-broadcom-dnx.swi Note: This PR also adds support for Broadcom SAI 5.0 (based on 1.8 SAI ) for DNX based platform + changes in platform x86_64-arista_7280cr3_32p4 bcm config files and platform_env.conf files
2021-06-22 13:12:22 -05:00
$(DOCKER_SYNCD_BRCM_RPC)_MACHINE = broadcom
Reference in New Issue Copy Permalink