Bug 2217663 - [TestOnly] Support for xmit hash policy for ports in VFLAG mode in NFV deployment scenarios
Summary: [TestOnly] Support for xmit hash policy for ports in VFLAG mode in NFV deploy...
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-openvswitch
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z3
: ---
Assignee: Haresh Khandelwal
QA Contact: OSP Team
URL:
Whiteboard: DFG:NFV
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-26 22:05 UTC by Gurpreet Singh
Modified: 2023-08-09 10:42 UTC (History)
6 users (show)

Fixed In Version: 5.14.0-283.el9.x86_64
Doc Type: Technology Preview
Doc Text:
In RHOSP 17.1, a technology preview is available for the VF-LAG transmit hash policy offload that enables load balancing at NIC hardware for offloaded traffic/flows. This hash policy is only available for layer3+4 base hashing.
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-26077 0 None None None 2023-06-26 22:08:49 UTC

Description Gurpreet Singh 2023-06-26 22:05:47 UTC 
Description of problem:

The VFLAG implementation used to implement LACP | mode=4 bond for the OVS Hardware Offload | Nvidia solution does not provide a way to select a specific xmit hash policy. The customer is Verizon and requires a way to implement a VFLAG with xmit hash policy layer3+4

The feature support was added in RHEL 8.6 and is available in RHEL 9.2 as well. 

This requirement is to validate/test the functionality in OSP for GA support. The feature is available as TP in OSP 17.1




This Jira is opened to build, and validate this feature end-to-end in RHOSP.

[1] : https://bugzilla.redhat.com/show_bug.cgi?id=2037510

[2]: https://bugzilla.redhat.com/show_bug.cgi?id=2049449


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


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