Open Stack

Hi,

> Wiadomość napisana przez Florian Engelmann <florian.engelmann at everyware.ch> w dniu 03.04.2019, o godz. 14:38:
> 
> Hi,
> 
> 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?

Correct. You will have to apply QoS policy to such new tenant by Your self.

> 
> 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?

Currently not.

> 
> All the best,
> Florian

— 
Slawek Kaplonski
Senior software engineer
Red Hat