Quality of Service (QoS) in Neutron - associating QoS policy to Floating IP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Slawek Kaplonski |
Bug Description
### Bug in documentation ###
https:/
1) Commands’ order
“The QoS bandwidth limit rules attached to a floating IP will become active when you associate the latter with a port. For example, to associate the previously created floating IP 172.16.100.12 to the instance port with fixed IP 192.168.222.5:”
After the above sentence we have “openstack port show a7f25e73-
This “SHOW” command shows port’s details only, but next command “openstack floating ip set --port a7f25e73-
2) Unknown ID “0eeb1f8a-
As potential user, I would expect to see one of the the IDs received in “openstack floating ip list” command’s output as parameter for “openstack floating ip set ...”, but actually we have “0eeb1f8a-
Ad. 1.
About order of commands I don't think it's wrong. SHOW command is there only to show port to which FIP will be later associated, nothing else. Why You think it can't/shouldn't be done before association?
Ad. 2. 3eb7-4c4f- a0f0-df04f10a06 7c in "openstack floating ip set " used.
I agree, it should be FIP with uuid=d0ed7491-