Agenda for workgroup meeting 01/15/2020

[praveen chaudhary]

Hi Team

Adding the Agenda for tomorrow's meeting.

-- Decide on YANG-models: Source Code Location, Build process, Testing and Location on Sonic Switch.

My Suggestions:

1.) Commit YANG model from Linkedin to src/sonic-yang-models in sonic-build image repo.

2.) Commit Make file changes to build wheel packages. The build process will include test cases for YANG models in Python.

3.) Commit Make file changes to attached this package with Sonic Image. And while installing this package, YANG-Models will be copied at /usr/local/yang-models on sonic switch.

4.) BRCM will commit\merge their yang models at src/sonic-yang-model too. [I can do that if needed, because both yang-models are following Guidelines ].
https://github.com/Azure/SONiC/blob/master/doc/mgmt/SONiC_YANG_Model_Guidelines.md

5.) PLY from LKDN and CVL from BRCM will change the PATH to yang-models to use these yang-models.

Regards

Praveen

[Zhenggen Xu]

Agenda for 1/29/2020 meeting:

• Update for the status

• Issues discussion:  

1, m_toSync map in Consumer class could overwrite the DEL action in some cases.

https://github.com/Azure/sonic-swss/pull/1184

2, SAI API implementation: on some platform, create_port has order restrictions when creating multiple ports in the same group, which needs to be fixed. 

3, SAI API implementation:  on some platform, sai doesn’t allow to set some attributes to default values on port object (e,g, SAI_PORT_ATTR_INGRESS_ACL). 

• Quick demo of the breakout on HW.

--
You received this message because you are subscribed to the Google Groups "sonic-breakout-workgroup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonic-breakout-wor...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonic-breakout-workgroup/CAJ_cd4qPBM1fb1nJeJ16%3D4z8K%2Bf2GRBNWjDC2Dw24NoEh68bxg%40mail.gmail.com.

[Zhenggen Xu]

This is the updated the status documents and meeting notes:

Status.   Meeting Notes.

There was a blocking issue for this feature: some vendor SAI API implementation requires create_port of multiple ports in a group to follow some particular order. This needs to be fixed in SAI implementation.

Also the demo recording is here.  Demo

Since there were not many participates in the last call, we are thinking to cancel the next meeting.  Let me know your thoughts.

Again, if you can help to review the PRs submitted, that would be helpful to finish the upstream. Thanks!