[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
Corey Bryant
corey.bryant at canonical.com
Mon Sep 23 19:45:45 UTC 2019
** Changed in: cloud-archive/ocata
Status: New => Triaged
** Changed in: cloud-archive/ocata
Importance: Undecided => Medium
** Changed in: cloud-archive/ocata
Importance: Medium => Wishlist
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1841700
Title:
instance ingress bandwidth limiting doesn't works in ocata.
Status in Ubuntu Cloud Archive:
Invalid
Status in Ubuntu Cloud Archive ocata series:
Triaged
Status in neutron:
Fix Released
Status in neutron package in Ubuntu:
Fix Released
Status in neutron source package in Xenial:
Invalid
Bug description:
[Environment]
Xenial-Ocata deployment
[Description]
The instance ingress bandwidth limit implementation was targeted for
Ocata [0], but the full implementation ingress/egress was done during
the pike [1] cycle.
However, isn't reported or explicit that ingress direction isn't
supported in ocata, which causes the following exception when
--ingress is specified.
$ openstack network qos rule create --type bandwidth-limit --max-kbps 300 --max-burst-kbits 300 --ingress bw-limiter
Failed to create Network QoS rule: BadRequestException: 400: Client Error for url: https://openstack:9696/v2.0/qos/policies/xxxx/bandwidth_limit_rules, Unrecognized attribute(s) 'direction'
It would be desirable for this feature to be available on Ocata for being able to
set ingress/egress bandwidth limits on the ports.
[0] https://blueprints.launchpad.net/neutron/+spec/instance-ingress-bw-limit
[1] https://bugs.launchpad.net/neutron/+bug/1560961
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1841700/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list