QoS Classiers terms should be ordered list
rszarecki opened this issue · 2 comments
rszarecki commented
Currently Classier terms is list with "id" being a key, while "id" is of string type.
This do not allow to unambiguisly tell the order of terms, what is critical, since condition of terma may be overlaping.
Also adding of ne term would not be possible.
It is suggested to replace Id with sequence-Id similiarly to sedulers[seq-id] of uint32 type. And mandate taht terms are evaluated always in ascending order.
dplore commented
I think sequence id is a good approach and as noted there is precedence in the QoS module to use a sequence id.
/qos/scheduler-policies/scheduler-policy/schedulers/scheduler/config/sequence is used for ordering scheduler policy.