[FRR]Upgrade FRR to 8.5.4 #85
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dgsudharsan
force-pushed
the
frr-8.5.4
branch
from
30efc52 to
6a63a39
Compare
dgsudharsan
pushed a commit
that referenced
this pull request
Mar 27, 2024
…e latest HEAD automatically (sonic-net#18450) #### Why I did it src/wpasupplicant/sonic-wpa-supplicant ``` * 3c7fd8e10 - (HEAD -> master, origin/master, origin/HEAD) Make Openssl CMAC API (omac1_aes_vector) Availalable in Non FIPs Mode (#85) (2 hours ago) [wumiao_nokia] ``` #### How I did it #### How to verify it #### Description for the changelog
…bg.gz build (sonic-net#18485) Why I did it Reproducible build fails when building dbg containers make INSTALL_DEBUG_TOOLS=y target/docker-orchagent-dbg.gz Work item tracking How I did it How to verify it export SONIC_VERSION_CONTROL_COMPONENTS=all make configure PLATFORM=broadcom make INSTALL_DEBUG_TOOLS=y target/docker-orchagent-dbg.gz
### Why I did it Added support for `minicom` , a terminal based communication tool in the sonic image for enabling communication to other devices. ### How I did it Added `minicom` to the list of packages to be installed in `sonic_debian_extension.j2` in the platform specific section for mellanox
…atically (sonic-net#18666) #### Why I did it src/sonic-utilities ``` * 9f962299 - (HEAD -> master, origin/master, origin/HEAD) Update intfutil and sfpshow to support DPC role (sonic-net#3242) (29 hours ago) [Vivek] ``` #### How I did it #### How to verify it #### Description for the changelog
…tomatically (sonic-net#18665) #### Why I did it src/sonic-platform-pde ``` * 8b44c3c - (HEAD -> master, origin/master, origin/HEAD) Merge pull request #36 from sg893052/PL_PDE_BOOKWORM_MIGRATION (27 hours ago) [賓少鈺] * 9f7ac0f - PDE Migration to bookworm (2 weeks ago) [sg893052] ``` #### How I did it #### How to verify it #### Description for the changelog
… automatically (sonic-net#18664) #### Why I did it src/sonic-platform-common ``` * de130c4 - (HEAD -> master, origin/master, origin/HEAD) [sfp] Ignore processing ports that are not front-panel (sonic-net#447) (29 hours ago) [Vivek] ``` #### How I did it #### How to verify it #### Description for the changelog
…D automatically (sonic-net#18614) #### Why I did it src/sonic-platform-daemons ``` * b5f838d - (HEAD -> master, origin/master, origin/HEAD) Fix intermittent build failure for test_SfpStateUpdateTask_task_run_stop (sonic-net#461) (3 days ago) [mihirpat1] ``` #### How I did it #### How to verify it #### Description for the changelog
- Why I did it CMIS management feature enablement - How I did it Add new variable with value 1 for CMIS management feature enablement under specific HWSKU folder. Not the default one - How to verify it Install image on switch with same HWSKU and check "show interfaces status" (Type column)
…gs (sonic-net#18668) - Why I did it python-sdk-api is failing in bookworm because it's triggering python2 bindings. - How I did it Fix the invocation by updating the env variable - How to verify it Compile python-sdk-api from source on bookworm environment and verify on sonic-mgmt tests
…t#18531) - Why I did it Add sensor files for MSN4700 simulation platform - How I did it Add the missing files to simulate platform part. - How to verify it Run sonic-mgmt sensor test to verify all is working Signed-off-by: Stephen Sun <stephens@nvidia.com>
… HWSKU folders (sonic-net#18441) - Why I did it The pmon_daemon_control.json file currently has a platform-specific scope, resulting in all SKUs of the same platform sharing the same pmon daemon configuration. Consequently, this restricts the ability to have distinct pmon daemon configurations for different SKUs. The proposed change aims to enhance flexibility by allowing PMON to load this file from both the platform folder and the HWSKU folder. In case a pmon_daemon_control.json file exists in the HWSKU folder, it will take precedence over the one in the platform folder. - How I did it The pmon docker init script will be updated to prioritize the HWSKU folder when searching for the pmon_daemon_control.json file. If the file is present in the HWSKU folder, it will be utilized. However, if the file does not exist in the HWSKU folder, the script will then fallback to utilizing the one located in the platform folder. - How to verify it Build image with this change, put the file in 1. platform folder, 2. in HWSKU folder 3. in both folders make sure the pmon daemons started according to the configuration. Signed-off-by: Kebo Liu <kebol@nvidia.com>
- Why I did it Align ACS-SN5600 buffer templates to reduce redundant code Support Mellanox-SN5600-O128 - How I did it Add relevant files to support the new SKU Update the SN5600 device files to align with the buffer configuration required. - How to verify it Regression test Signed-off-by: Stephen Sun <stephens@nvidia.com>
* Move mrvl-prestera and sonic-platform-marvell submodule 'mrvl-prestera' and 'sonic-platform-marvell' submodules are moved from 'marvell-arm64'to 'marvell'. Additionaly submodules are changed to support multi-architecture build. Signed-off-by: Pavan Naregundi <pnaregundi@marvell.com>
… automatically (sonic-net#18675) #### Why I did it src/sonic-platform-common ``` * dff8d48 - (HEAD -> master, origin/master, origin/HEAD) Separate common code for remote target FW upgrade supported optics (sonic-net#453) (20 hours ago) [mihirpat1] ``` #### How I did it #### How to verify it #### Description for the changelog
- Why I did it Get the container name for a service according to the ASIC ID - How I did it Add new function to get the requested data - How to verify it Add unit test to cover the new added function
…onic-net#18438) - Why I did it For multi asic platform, the container name is not the same as service name. For example, service name swss, the container in namespace asic0 will have container name swss0. This PR is to support multi ASIC platform. - How I did it Add a global variable service_name and use it to match DB key. - How to verify it Manual test Unit test
Signed-off-by: Neetha John <nejo@microsoft.com>
…omatically (sonic-net#18689) #### Why I did it src/sonic-swss-common ``` * 5a73792 - (HEAD -> master, origin/master, origin/HEAD) [subnet_decap] Introduce subnet decap tables (sonic-net#861) (33 minutes ago) [Longxiang Lyu] ``` #### How I did it #### How to verify it #### Description for the changelog
…omatically (sonic-net#18688) #### Why I did it src/sonic-mgmt-common ``` * 72e0df9 - (HEAD -> master, origin/master, origin/HEAD) CVL Sort issue in target TABLE with multi-list (10 hours ago) [Mohammed Faraaz] ``` #### How I did it #### How to verify it #### Description for the changelog
…t#18466) - Why I did it Add support for new Nvidia-bluefield BF-3 DPU. - How I did it Define a new nvidia-bluefield platform with a set of makefiles to compile an image with all dependencies. Impleme PMON platform API - How to verify it The added changes don't affect the compilation of the existing platforms. Signed-off-by: Oleksandr Ivantsiv <oivantsiv@nvidia.com>
…ic-net#18414) - Why I did it Adjust nvidia platform API log content for module host management feature - How I did it Add log content for EEPROM read/write Add log content for module detection thread Adjust existing log level/content for module detection thread - How to verify it Manual test
…16957) - Why I did it Added Banner feature related services according to HLD: sonic-net/SONiC#1361 - How I did it Added banner-config systemd service, YANG model for new ConfDB table and YANG model tests - How to verify it Manual test Co-authored-by: Sviatoslav Boichuk <sviatoslavb@nvidia.com>
…cific platforms (sonic-net#18487) - Why I did it Enable forwarding of packets with link local SIP/DIP on specific platforms and SKUs. - How I did it Setting SAI key value pair SAI_NOT_DROP_SIP_DIP_LINK_LOCAL=1 - How to verify it Manual test to verify that packets with link local SIP/DIP are not dropped
…009d3b600SVAA BF-3 DPUs. (sonic-net#18467) -Why I did it Add support for new Nvidia-9009d3b600CVAA and Nvidia-9009d3b600SVAA BF-3 DPU devices. - How I did it Define new platforms with the basic configuration and SKUs. - How to verify it The changes don't affect the SONiC compilation process or run-time. Signed-off-by: Oleksandr Ivantsiv <oivantsiv@nvidia.com> Co-authored-by: Vivek Reddy <vkarri@nvidia.com> Co-authored-by: Yakiv Huryk <yhuryk@nvidia.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
Upgrading FRR to 8.5.4
Work item tracking
How I did it
Realigned the patches. Updated submodule
How to verify it
Running regression
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)