This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2222289 - [RFE] Support OVS SR-IOV TC Hardware Offload
Summary: [RFE] Support OVS SR-IOV TC Hardware Offload
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 9.4
Assignee: NetworkManager Development Team
QA Contact: Vladimir Benes
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-12 14:41 UTC by Gris Ge
Modified: 2023-08-17 12:23 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-17 12:23:21 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-666 0 None None None 2023-07-12 14:45:18 UTC
Red Hat Issue Tracker   RHEL-1441 0 None None None 2023-08-17 12:23:20 UTC
Red Hat Issue Tracker RHELPLAN-162122 0 None None None 2023-07-12 14:45:23 UTC

Description Gris Ge 2023-07-12 14:41:36 UTC 
Description of problem:

OpenStack team is expecting NetworkManager provide support of
OVS SR-IOV TC Hardware Offload describe in

https://docs.openstack.org/neutron/queens/admin/config-ovs-offload.html


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Given a OpenStack system based on RHEL 9.4+,
When user apply nmstate YML containing OpenvSwitch TC hardware offloading config,
Then nmstate will instruct NetworkManager to setup the OVS TC hardware offload describe in https://docs.openstack.org/neutron/queens/admin/config-ovs-offload.html

Story point would be 5.
Note You need to log in before you can comment on or make changes to this bug.