The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.
Bug 2120546 - [RFE] Add OpenFlow extension to allow more extensive filtering when flushing conntrack.
Summary: [RFE] Add OpenFlow extension to allow more extensive filtering when flushing ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux Fast Datapath
Classification: Red Hat
Component: openvswitch3.1
Version: FDP 22.E
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Ales Musil
QA Contact: Jiying Qiu
URL:
Whiteboard:
Depends On:
Blocks: 1839103
TreeView+ depends on / blocked
 
Reported: 2022-08-23 08:35 UTC by Dumitru Ceara
Modified: 2023-05-16 10:33 UTC (History)
5 users (show)

Fixed In Version: openvswitch3.1-3.1.0-3.el8fdp
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-16 10:33:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FD-2246 0 None None None 2022-08-23 08:43:08 UTC

Description Dumitru Ceara 2022-08-23 08:35:41 UTC
Description of problem:

OVS currently supports an OpenFlow extension (OFPRAW_NXT_CT_FLUSH_ZONE) to flush all conntrack entries in a given zone:

https://github.com/openvswitch/ovs/blob/ff55e8f3858ae153ef1996df3d52938f3df6d950/include/openvswitch/ofp-msgs.h#L515

/* NXT_CT_FLUSH_ZONE.
 *
 * Flushes the connection tracking table. */
struct nx_zone_id {
    uint8_t zero[6];            /* Must be zero. */
    ovs_be16 zone_id;           /* Connection tracking zone. */
}

It would be desirable to be able to flush a subset of the conntrack entries in a zone.  The subset could be defined by a (potentially partial) tuple of the form: IP, L4 proto, L4 port.

For example, OVN would use this feature to clear conntrack entries that correspond to a load balancer backend ("IP:PROTO:PORT") that was recently removed (bug 1839103).  This means that all conntrack records that use IP, PROTO and PORT either in the original or in the reply direction need to be flushed.

Note: OVS must be able to indicate to the controller whether this extension is supported or not, for example, via the vswitchd.Datapath.capabilities column in the local OVSDB.


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