matthew/sonic-buildimage
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
bd8e2a8db9
sonic-buildimage/platform/vs/onie.mk

11 lines
740 B
Makefile
Raw Normal View History

[vs]: build sonic vs kvm image (#2269) Signed-off-by: Guohan Lu <gulv@microsoft.com>
2018-11-21 00:32:40 -06:00
ONIE_RECOVERY_IMAGE = onie-recovery-x86_64-kvm_x86_64-r0.iso
[build] Use public storage for public resources. (#18038)
2024-02-27 19:45:49 -06:00
$(ONIE_RECOVERY_IMAGE)_URL = "https://sonicstorage.blob.core.windows.net/public/onie/onie-recovery-x86_64-kvm_x86_64-r0.iso"
[vs]: build sonic vs kvm image (#2269) Signed-off-by: Guohan Lu <gulv@microsoft.com>
2018-11-21 00:32:40 -06:00
[vs][multi-asic]: Add new platforms for multi-asic vs. (#8269) Why I did it End goal: To have azure pipeline job to run multi-asic VS tests. Intermediate goal: Require multi-asic KVM image so that the test can be run. The difference between single asic and multi-asic KVM image is asic.conf file which has different NUM_ASIC values. Idea behind the approach in this PR to attain the intermediate goal above: Ease of building multi-asic KVM image so that any user or azure pipeline can use a simple make command to generate single or multi-asic KVM images as required. Use a single onie installer image and multiple KVM images for single and multi-asic images. Current scenario: For VS platform, sonic-vs.bin is generated which is the onie installer image and sonic-vs.img.gz is generated which is the KVM iamge. Scenario to be achieved: sonic-vs.bin - which will include single asic platform, 4 asic platform and 6 asic platform. sonic-vs.img.gz - single asic KVM image sonic-4asic-vs.img.gz - 4 asic KVM image sonic-6asic-vs.img.gz - 6 asic KVM image In this PR, 2 new platforms are added for 4-asic and 6-asic VS. How I did it Create 4-asic and 6-asic device directories with the required files and hwsku files. Add onie-recovery image information in vs platform. How to verify it After this PR change, no build change. sonic-vs.bin onie installer image should include information of new multi-asic vs platforms.
2021-09-01 00:45:59 -05:00
ONIE_RECOVERY_KVM_4ASIC_IMAGE = onie-recovery-x86_64-kvm_x86_64_4_asic-r0.iso
[build] Use public storage for public resources. (#18038)
2024-02-27 19:45:49 -06:00
$(ONIE_RECOVERY_KVM_4ASIC_IMAGE)_URL = "https://sonicstorage.blob.core.windows.net/public/onie/onie-recovery-x86_64-kvm_x86_64_4_asic-r0.iso"
[vs][multi-asic]: Add new platforms for multi-asic vs. (#8269) Why I did it End goal: To have azure pipeline job to run multi-asic VS tests. Intermediate goal: Require multi-asic KVM image so that the test can be run. The difference between single asic and multi-asic KVM image is asic.conf file which has different NUM_ASIC values. Idea behind the approach in this PR to attain the intermediate goal above: Ease of building multi-asic KVM image so that any user or azure pipeline can use a simple make command to generate single or multi-asic KVM images as required. Use a single onie installer image and multiple KVM images for single and multi-asic images. Current scenario: For VS platform, sonic-vs.bin is generated which is the onie installer image and sonic-vs.img.gz is generated which is the KVM iamge. Scenario to be achieved: sonic-vs.bin - which will include single asic platform, 4 asic platform and 6 asic platform. sonic-vs.img.gz - single asic KVM image sonic-4asic-vs.img.gz - 4 asic KVM image sonic-6asic-vs.img.gz - 6 asic KVM image In this PR, 2 new platforms are added for 4-asic and 6-asic VS. How I did it Create 4-asic and 6-asic device directories with the required files and hwsku files. Add onie-recovery image information in vs platform. How to verify it After this PR change, no build change. sonic-vs.bin onie installer image should include information of new multi-asic vs platforms.
2021-09-01 00:45:59 -05:00
ONIE_RECOVERY_KVM_6ASIC_IMAGE = onie-recovery-x86_64-kvm_x86_64_6_asic-r0.iso
[build] Use public storage for public resources. (#18038)
2024-02-27 19:45:49 -06:00
$(ONIE_RECOVERY_KVM_6ASIC_IMAGE)_URL = "https://sonicstorage.blob.core.windows.net/public/onie/onie-recovery-x86_64-kvm_x86_64_6_asic-r0.iso"
[vs][multi-asic]: Add new platforms for multi-asic vs. (#8269) Why I did it End goal: To have azure pipeline job to run multi-asic VS tests. Intermediate goal: Require multi-asic KVM image so that the test can be run. The difference between single asic and multi-asic KVM image is asic.conf file which has different NUM_ASIC values. Idea behind the approach in this PR to attain the intermediate goal above: Ease of building multi-asic KVM image so that any user or azure pipeline can use a simple make command to generate single or multi-asic KVM images as required. Use a single onie installer image and multiple KVM images for single and multi-asic images. Current scenario: For VS platform, sonic-vs.bin is generated which is the onie installer image and sonic-vs.img.gz is generated which is the KVM iamge. Scenario to be achieved: sonic-vs.bin - which will include single asic platform, 4 asic platform and 6 asic platform. sonic-vs.img.gz - single asic KVM image sonic-4asic-vs.img.gz - 4 asic KVM image sonic-6asic-vs.img.gz - 6 asic KVM image In this PR, 2 new platforms are added for 4-asic and 6-asic VS. How I did it Create 4-asic and 6-asic device directories with the required files and hwsku files. Add onie-recovery image information in vs platform. How to verify it After this PR change, no build change. sonic-vs.bin onie installer image should include information of new multi-asic vs platforms.
2021-09-01 00:45:59 -05:00
SONIC_ONLINE_FILES += $(ONIE_RECOVERY_IMAGE) $(ONIE_RECOVERY_KVM_4ASIC_IMAGE) $(ONIE_RECOVERY_KVM_6ASIC_IMAGE)
Reference in New Issue Copy Permalink