Comment 2 for bug 1796410

I had looked at Neutron QoS policies, but it looked like these were network policies, not per-flavor policies. We need the ability for flavors to define the policy since our users will create their own projects, create their own networks, and launch their own VMs, and should not have the ability to affect the QoS policy on their own infrastructure.

If you know of a way to do the above with Neutron QoS policies, I will follow your lead.

Thanks!

Eric