feat: allow previous connection for deploy-l1#21909
Merged
yejianquan merged 1 commit intosonic-net:masterfrom Jan 16, 2026
Merged
feat: allow previous connection for deploy-l1#21909yejianquan merged 1 commit intosonic-net:masterfrom
yejianquan merged 1 commit intosonic-net:masterfrom
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sdszhang
reviewed
Jan 12, 2026
auspham
force-pushed
the
austinpham/36386319-deploy-l1-keep-old-connection
branch
from
c434026 to
f6ad4a0
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Austin Pham <[email protected]>
auspham
force-pushed
the
austinpham/36386319-deploy-l1-keep-old-connection
branch
from
f6ad4a0 to
4f4d033
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sdszhang
approved these changes
Jan 14, 2026
Contributor
sdszhang
left a comment
sdszhang
left a comment
There was a problem hiding this comment.
I don't see any update from Riff yet. Let's go with current method first without changing the behavior for NUT testbed.
PriyanshTratiya
pushed a commit
to PriyanshTratiya/sonic-mgmt
that referenced
this pull request
Jan 21, 2026
Description of PR Summary: Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top. However, this will also not allow us to re-use l1. New changes add a parameter allow_previous_connection which helps to allow existing connections. It only remove if the connection is overlap with the second connection Signed-off-by: Austin Pham <[email protected]> Signed-off-by: Priyansh Tratiya <[email protected]>
AndoniSanguesa
pushed a commit
to AndoniSanguesa/sonic-mgmt
that referenced
this pull request
Jan 21, 2026
Description of PR Summary: Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top. However, this will also not allow us to re-use l1. New changes add a parameter allow_previous_connection which helps to allow existing connections. It only remove if the connection is overlap with the second connection Signed-off-by: Austin Pham <[email protected]> Signed-off-by: Andoni Sanguesa <[email protected]>
AndoniSanguesa
pushed a commit
to AndoniSanguesa/sonic-mgmt
that referenced
this pull request
Jan 21, 2026
Description of PR Summary: Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top. However, this will also not allow us to re-use l1. New changes add a parameter allow_previous_connection which helps to allow existing connections. It only remove if the connection is overlap with the second connection Signed-off-by: Austin Pham <[email protected]> Signed-off-by: Andoni Sanguesa <[email protected]>
saravanan-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Jan 22, 2026
Description of PR Summary: Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top. However, this will also not allow us to re-use l1. New changes add a parameter allow_previous_connection which helps to allow existing connections. It only remove if the connection is overlap with the second connection Signed-off-by: Austin Pham <[email protected]> Signed-off-by: Saravanan Sellappa <[email protected]>
justin-oliver
pushed a commit
to justin-oliver/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
Description of PR Summary: Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top. However, this will also not allow us to re-use l1. New changes add a parameter allow_previous_connection which helps to allow existing connections. It only remove if the connection is overlap with the second connection Signed-off-by: Austin Pham <[email protected]>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
Description of PR Summary: Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top. However, this will also not allow us to re-use l1. New changes add a parameter allow_previous_connection which helps to allow existing connections. It only remove if the connection is overlap with the second connection Signed-off-by: Austin Pham <[email protected]> Signed-off-by: Yael Tzur <[email protected]>
abhishek-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Feb 6, 2026
Description of PR Summary: Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top. However, this will also not allow us to re-use l1. New changes add a parameter allow_previous_connection which helps to allow existing connections. It only remove if the connection is overlap with the second connection Signed-off-by: Austin Pham <[email protected]>
nnelluri-cisco
pushed a commit
to nnelluri-cisco/sonic-mgmt
that referenced
this pull request
Feb 12, 2026
Description of PR Summary: Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top. However, this will also not allow us to re-use l1. New changes add a parameter allow_previous_connection which helps to allow existing connections. It only remove if the connection is overlap with the second connection Signed-off-by: Austin Pham <[email protected]> Signed-off-by: nnelluri-cisco <[email protected]>
rraghav-cisco
pushed a commit
to rraghav-cisco/sonic-mgmt
that referenced
this pull request
Feb 13, 2026
Description of PR Summary: Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top. However, this will also not allow us to re-use l1. New changes add a parameter allow_previous_connection which helps to allow existing connections. It only remove if the connection is overlap with the second connection Signed-off-by: Austin Pham <[email protected]> Signed-off-by: Raghavendran Ramanathan <[email protected]>
anilal-amd
pushed a commit
to anilal-amd/anilal-forked-sonic-mgmt
that referenced
this pull request
Feb 19, 2026
Description of PR Summary: Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top. However, this will also not allow us to re-use l1. New changes add a parameter allow_previous_connection which helps to allow existing connections. It only remove if the connection is overlap with the second connection Signed-off-by: Austin Pham <[email protected]> Signed-off-by: Zhuohui Tan <[email protected]>
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
… automatically (sonic-net#21909) #### Why I did it src/sonic-platform-common ``` * f679a67 - (HEAD -> 202411, origin/202411) Restore optoe page to default 0 for active cables (sonic-net#550) (7 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
abhishek-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Mar 17, 2026
Description of PR Summary: Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top. However, this will also not allow us to re-use l1. New changes add a parameter allow_previous_connection which helps to allow existing connections. It only remove if the connection is overlap with the second connection Signed-off-by: Austin Pham <[email protected]> Signed-off-by: Abhishek <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
Description of PR Summary: Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top. However, this will also not allow us to re-use l1. New changes add a parameter allow_previous_connection which helps to allow existing connections. It only remove if the connection is overlap with the second connection Signed-off-by: Austin Pham <[email protected]>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description of PR
Summary:
Fixes # (issue) Currently, deploy-l1 is using overwrite mode. Which replace all the previous connection and add a new one on top.
However, this will also not allow us to re-use l1.
New changes add a parameter
allow_previous_connectionwhich helps to allow existing connections.It only remove if the connection is overlap with the second connection
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation