[neutron] question: default QoS rule for all routers/fip and all future once

Florian Engelmann florian.engelmann at everyware.ch
Wed Apr 3 12:38:17 UTC 2019


the documentation about neutron and QoS talks about setting a default 
QoS rule for a project.

"Each project can have at most one default QoS policy, although it is 
not mandatory. If a default QoS policy is defined, all new networks 
created within this project will have this policy assigned, as long as 
no other QoS policy is explicitly attached during the creation process. 
If the default QoS policy is unset, no change to existing networks will 
be made.

In order to set a QoS policy as default, the parameter --default must be 
used. To unset this QoS policy as default, the parameter --no-default 
must be used."

So if a cloud provider wants to limit all router egress traffic to eg. 
1Gbits this policy has to be set as default to all projects. But what if 
the customer is allowed to create new projects? This project will not 
have any default policy applied, right?

And it looks like the is no API/logic in place to allow a self service 
customer to choose between different "network flavors"?
Is something like that on the roadmap?

All the best,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5230 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190403/7a41e436/attachment.bin>

More information about the openstack-discuss mailing list