[Backport #1507761] qos wrong units in max-burst-kbps option (per-second is wrong)

[Sergii]

We need to backport https://bugs.launchpad.net/neutron/+bug/1507761

Steps to reproduce:

1) neutron qos-policy-create limiter
2) neutron qos-bandwidth-limit-rule-create limiter --max-kbps 4000 --max-burst-kbps 1000

Expected result:
Parameter "max-burst-kbps" has got wrong units suggested. Burst should be given in kb (kilobits) instead of kbps (kilobits per second)

Actual result:
Burst is given in kbps (kilobits per second)

Original discription:
In neutron in qos bw limit rule table in database and in API extension parameter "max-burst-kbps" has got wrong units suggested. Burst should be given in kb (kilobits) instead of kbps (kilobits per second)

Reproducibility:
Reproduce continuously on iso 45, 97, 113

fuel_build_id 113
fuel_build_number 113
fuel_release 9.0
fuel_openstack_version liberty-9.0

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

version

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Ann Taraday (akamyshnikova)]

Upstream change https://review.openstack.org/#/c/291633/ won't be backported to stable/mitaka as it requires API change(restricted by stable backport guideline), backporting it manually is dangerous as this change is too big.

This will be documented in upstream release notes of Mitaka, though.

[Dina Belova (dbelova)]

Added move-to-10.0 tag due to the fact bug was transferred from 9.0 to 10.0

[Alexander Ignatov (aignatov)]

As per Ann's comment in #2 this bug will not going to be fixed in stable/mitaka since it requires API changes. So I'd suggest to leave it in 10.0 as is. Probably "move-to-10.0" can be removed as well.

[Eugene Nikanorov (enikanorov)]

Have not been fixed in upstream, see original bug