Neutron-api charm can't enable qos
Bug #1705358 reported by
Jill Rouleau
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron API Charm |
Fix Released
|
Wishlist
|
Liam Young | ||
OpenStack Neutron Gateway Charm |
Fix Released
|
Wishlist
|
Liam Young | ||
OpenStack Neutron Open vSwitch Charm |
Fix Released
|
Wishlist
|
Liam Young |
Bug Description
neutron-api charm does not provide any means of enabling the qos plugin. The metadata.yaml states: "The Neutron API supports extensions to provide advanced network capabilities (e.g., QoS, ACLs, network monitoring, etc.)" leaving an impression the charm means to support it. We have customers requesting to be able to use qos features in Neutron and are unable to enable this.
Related branches
lp://staging/~gnuoy/charm-helpers/enable-qos
- charmers: Pending requested
-
Diff: 86 lines (+46/-4)2 files modifiedcharmhelpers/contrib/openstack/context.py (+12/-0)
tests/contrib/openstack/test_os_contexts.py (+34/-4)
Changed in charm-neutron-api: | |
assignee: | nobody → Liam Young (gnuoy) |
Changed in charm-neutron-api: | |
status: | New → Confirmed |
Changed in charm-neutron-api: | |
importance: | Undecided → High |
importance: | High → Wishlist |
Changed in charm-neutron-api: | |
status: | Confirmed → In Progress |
milestone: | none → 17.08 |
Changed in charm-neutron-api: | |
milestone: | 17.08 → 17.11 |
Changed in charm-neutron-gateway: | |
status: | New → In Progress |
Changed in charm-neutron-openvswitch: | |
status: | New → In Progress |
Changed in charm-neutron-gateway: | |
milestone: | none → 17.11 |
Changed in charm-neutron-openvswitch: | |
milestone: | none → 17.11 |
Changed in charm-neutron-gateway: | |
importance: | Undecided → Wishlist |
Changed in charm-neutron-openvswitch: | |
importance: | Undecided → Wishlist |
Changed in charm-neutron-gateway: | |
assignee: | nobody → Liam Young (gnuoy) |
Changed in charm-neutron-openvswitch: | |
assignee: | nobody → Liam Young (gnuoy) |
Changed in charm-neutron-api: | |
status: | In Progress → Fix Committed |
Changed in charm-neutron-gateway: | |
status: | In Progress → Confirmed |
status: | Confirmed → Fix Committed |
Changed in charm-neutron-openvswitch: | |
status: | In Progress → Fix Committed |
Changed in charm-neutron-api: | |
status: | Fix Committed → Fix Released |
Changed in charm-neutron-gateway: | |
status: | Fix Committed → Fix Released |
Changed in charm-neutron-openvswitch: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I've been following https:/ /docs.openstack .org/mitaka/ networking- guide/config- qos.html and have a set of changes ready to land. I've added support for Mitaka+
The changes do the following:
1) Add enable-qos option to the neutron-api charm. If enable-qos is set then neutron. services. qos.qos_ plugin. QoSPlugin is added to service_plugins in neutron.conf locally. The neutron- plugin- api-relation has also been updated to send the enable-qos plugin- api-relation and update NeutronAPIContext agent.ini if qos is enabled agent.ini if qos is enabled
2) Charmhelper update to read the enable-qos setting on the neutron-
3) Update neutron-openvswitch to set extensions='qos' in openvswitch_
4) Update neutron-gateway to set extensions='qos' in openvswitch_
If tested setting max-kbps and max-burst-kbps qos settings and monitoring iperf. I've tested applying the limits to both an instances' qvo interface on the compute node and a networks tap interface on the gateway.