forwarding class id could be auto-computed while creating qos fcs
Bug #1598091 reported by
Vedamurthy Joshi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juniper Openstack |
New
|
Wishlist
|
Naveen N | ||
Bug Description
R3.1.0.0 2738 Kilo
Today, while creating ForwardingClass, if id is not specified, it is set to None
It will be hard for the user to keep track of FC ids
We should auto-compute these ids while creating fcs.
Per discussion with Praveen, Naveen, it is also suggested that while creating qos-config entries, the user would just specify the fc object's uuid/name could be specified instead of directly using the id
FC id can only be internal to contrail and the user need not be aware of it
| tags: | added: qos |
Revision history for this message
| Naveen N (naveenn) wrote | #1 |
| Changed in juniperopenstack: | |
| importance: | High → Wishlist |
To post a comment you must log in.
FC id has to be user known value, for now we will only put validity check for unique forwarding class