QosConfig and ForwardingClass need to be named differently
Bug #1602553 reported by
Vedamurthy Joshi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juniper Openstack |
New
|
Wishlist
|
Naveen N | ||
| R3.1 |
Won't Fix
|
Wishlist
|
Naveen N | ||
Bug Description
QoSConfig table/object – This seems to be too generic a name to indicate anything. Since we are doing traffic classification here, can we rename it accordingly ? Suggestion : "QoSClassifier"
“ForwardingClass” object seems to do fc-queue mapping and remark the packet also. It will be confusing in the field, since in Juniper terminology, a forwarding class is analogous to a queue
| tags: | added: qos |
| Changed in juniperopenstack: | |
| importance: | High → Wishlist |
To post a comment you must log in.
