Bug 1999874 - Apply QoS policy to entire external network.
Summary: Apply QoS policy to entire external network.
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux Fast Datapath
Classification: Red Hat
Component: ovn2.13
Version: FDP 20.D
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: OVN Team
QA Contact: ying xu
URL:
Whiteboard:
Depends On:
Blocks: 2012877
TreeView+ depends on / blocked
 
Reported: 2021-08-31 20:59 UTC by Priscila
Modified: 2023-07-13 07:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2012877 (view as bug list)
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FD-1517 0 None None None 2021-08-31 21:00:14 UTC

Description Priscila 2021-08-31 20:59:33 UTC
Description of problem:

We need to be able to apply the qos policy to the entire external network. In this situation an instance with the network directly connected (port) works, but the floating IPs that belong to the network if the policy is not applied specifically ignore that policy applied to the network, the same happens with the external gateway of the router 

openstack floating ip set --qos-policy test_qos_10Mb xxxxxxxxxxxxxxxx

openstack router set --qos-policy qos-2Mbps_up-2Mbps_down Router-Admin

BadRequestException: 400: Client Error for url: https://mysite.com:1234/v2.0/routers/xxxxxxxxxxxxxx, Invalid input for external_gateway_info. Reason: Unexpected keys supplied: qos_policy_id.

We have created the corresponding entry and exit policies and rules. Instances directly connected to an external network, works, but in instances that have a geneve network and go to the internet through SNAT, when we do a speed test against the internet, we see that they are not being limited by not respecting that limit in the gateway of the router

  OVNQosDriver: 'ovn-qos'
  NeutronSriovAgentExtensions: 'qos'


Note You need to log in before you can comment on or make changes to this bug.