scheduler Profiles required?

openBackhaul / ethernetContainer

Technology specific interface definition for an Ethernet Container

Apache License 2.0

1 stars 0 forks source link

Closed openBackhaul closed 2 years ago

openBackhaul commented 4 years ago

To be checked, whether Devices require also scheduling to be configured on switch or device level.

openBackhaul commented 3 years ago

Status of the discussion at the DMIP call on 17th of June 2021: Alternative way of modelling the scheduler configuration:

Defining a Scheduler Profile, which contains a list of queues and facilitates configuring schedulerKind : SchedulerKindType and weighting : Integer for every queue.
Adding some _schedulerProfile : Profile attribute to the EthernetContainerConfiguration and to the EthernetContainerFdConfiguration for facilitating choosing the schedulerProfile at interface and switch level.

openBackhaul commented 3 years ago

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.

Next step would be defining such SchedulerProfile in UML.

openBackhaul commented 2 years ago

Done:

SchedulerProfile provided
schedulerProfile : Profile attribute added to the EthernetContainerConfiguration.
issues created at EthernetContainerFd for some _schedulerProfile : Profile attribute to be added to the EthernetContainerFdConfiguration

openBackhaul commented 2 years ago

Fixed with EthernetContainer_2.0.0-tsp.220405.1755.