Skip to content
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

[yang][smartswitch] Add YANG model for MID_PLANE_BRIDGE and DPU tables. #12

Closed
wants to merge 1 commit into from

Conversation

oleksandrivantsiv
Copy link
Owner

Why I did it

Add the YANG model according to TODO HDL.

Work item tracking
  • Microsoft ADO (number only):

How I did it

Implement new YANG model containers.

How to verify it

Run YANG model unit tests. The changes add new unit tests to cover new functionality.

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211
  • 202305

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)

leaf dpu_name {
description "Name of the DPU";
type string {
pattern "dpu[0-9]+";

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If dpu name = dpu interface why do we need this table?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we will have more information in the table later. For example PCI ID, data plane interface mapping to the DPU interface, etc.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we then add a check that midplane_interface = dpu_name? Since the interface names are created based on the DPU to which they are mapped, it is better to enforce this check

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

leaf dpu_name {
description "Name of the DPU";
type string {
pattern "dpu[0-9]+";

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we then add a check that midplane_interface = dpu_name? Since the interface names are created based on the DPU to which they are mapped, it is better to enforce this check

oleksandrivantsiv pushed a commit that referenced this pull request Jan 31, 2024
…tically (sonic-net#17847)

#### Why I did it
src/sonic-dash-api
```
* 8f481de - (HEAD -> master, origin/master, origin/HEAD) [misc]: Add utils CLI (#12) (24 hours ago) [Ze Gan]
```
#### How I did it
#### How to verify it
#### Description for the changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants