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.

Sign up for GitHub

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

Jump to bottom

scheduler Profile #3

Open

openBackhaul opened this issue Apr 5, 2022 · 0 comments

Assignees

Labels

YANG_to_be_provided

Owner

openBackhaul commented Apr 5, 2022

Status of the discussion at the DMIP call on 8th of July 2021:
All three ways of modelling should be supported:

Individual configuration of every queue at every interface (as it is today)
Referencing a Profile (which is allowing configuring every queue) at the individual interface
Referencing a Profile (which is allowing configuring every queue) for all interfaces together at the EthernetContainerFd.

Impact on ethernetContainerFd:

Adding some _schedulerProfile : Profile attribute the EthernetContainerFdConfiguration for facilitating choosing the schedulerProfile at switch level.

openBackhaul self-assigned this

openBackhaul added the UML_to_be_changed label

openBackhaul added YANG_to_be_provided and removed UML_to_be_changed labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment