-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add YANG model for FABRIC_PORT #15629
Add YANG model for FABRIC_PORT #15629
Conversation
|
||
leaf isolateStatus { | ||
description "Isolation status of a fabric port"; | ||
type string { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not use Boolean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good suggestion. I will revise it to use type stypes:boolean_type
where stypes is sonic-types.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. See latest commit. I'm waiting for the pipeline build to complete to check if any further revisions are needed.
@qiluo-msft can you help merge this PR? |
@kenneth-arista , @jfeng-arista , This PR also can not be clean cherry picked tot he azure/sonic-buildimage-msft repo 202205 branch. |
will do thank you
Jie
…On Thu, Jul 13, 2023 at 5:06 PM gechiang ***@***.***> wrote:
@kenneth-arista <https://github.com/kenneth-arista> , @jfeng-arista
<https://github.com/jfeng-arista> , This PR also can not be clean cherry
picked tot he azure/sonic-buildimage-msft repo 202205 branch.
Can you please raise a PR in the azure/sonic-buildimage-msft repo directly
and tag me to review/merge.
Thanks!
—
Reply to this email directly, view it on GitHub
<#15629 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXO4THVLG2XBF3EVDHSD3CLXQCEQZANCNFSM6AAAAAAZTY735M>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@gechiang do we need this to cherry pick to 202211/202305? could we have ADO to track? |
@StormLiangMS |
#### Why I did it Introduce YANG model for FABRIC in CONFIG_DB, which was added in sonic-net#14170. #### How I did it This is a clone of @jfeng-arista's PR sonic-net#14282 to resolve conflicts with upstream changes. #### How to verify it Passing pipeline build is sufficient.
Cherry-pick PR to 202305: #16398 |
#### Why I did it Introduce YANG model for FABRIC in CONFIG_DB, which was added in #14170. #### How I did it This is a clone of @jfeng-arista's PR #14282 to resolve conflicts with upstream changes. #### How to verify it Passing pipeline build is sufficient.
Removed request for 202211 due to this is treated as "feature" and not bug fix back port. Same reason as why it was not picked for 202205. |
#### Why I did it Introduce YANG model for FABRIC in CONFIG_DB, which was added in sonic-net#14170. #### How I did it This is a clone of @jfeng-arista's PR sonic-net#14282 to resolve conflicts with upstream changes. #### How to verify it Passing pipeline build is sufficient.
…or-fabric-monitor Add sonic-net#14390 and sonic-net#15629 to 202205.
Why I did it
Introduce YANG model for FABRIC in CONFIG_DB, which was added in #14170.
How I did it
This is a clone of @jfeng-arista's PR #14282 to resolve conflicts with upstream changes.
How to verify it
Passing pipeline build is sufficient.
Which release branch to backport (provide reason below if selected)