** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: neutron (Ubuntu)
Status: New => Fix Released
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: neutron
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1841700
Title:
instance ingress bandwidth limiting doesn't works in ocata.
Status in Ubuntu Cloud Archive:
New
Status in neutron:
Fix Released
Status in neutron package in Ubuntu:
Fix Released
Status in neutron source package in Xenial:
New
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
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
