Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 2040852

Summary: COPP table doesn't have name or externalIDs
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Surya Seetharaman <surya>
Component: OVNAssignee: lorenzo bianconi <lorenzo.bianconi>
Status: CLOSED CURRENTRELEASE QA Contact: ying xu <yinxu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: FDP 21.CCC: ctrautma, jiji, lorenzo.bianconi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-13 07:02:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Surya Seetharaman 2022-01-14 19:36:25 UTC
Description of problem:

Not exactly a bug, but a wishlist of improvements for COPP feature from user persepctive:

1) Since the COPP table only has UUID and Meters fields of which the latter is a map, its hard to query the table efficiently, specially when we want to reuse the same copp for multiple switches/routers:

sh-5.1# ovn-nbctl list copp
_uuid               : f1af4257-65b4-46e4-a412-d56fb8de39b9
meters              : {arp=rate-limiter, arp-resolve=rate-limiter, bfd=rate-limiter, event-elb=rate-limiter, icmp4-error=rate-limiter, icmp6-error=rate-limiter, reject=rate-limiter, tcp-reset=rate-limiter}

2) ovn-nbctl lr-copp-add <router> <proto> <meter>
This doesn't allow specifying an existing copp UUID, always duplicates and creates a new copp and associates that to the router.

3) Having a standalone copp creation command would be good, just like we have meter-add, but since ovn-k uses libovsdb, we don't mind even if its not there.

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


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 lorenzo bianconi 2022-02-11 21:11:06 UTC
the patch has been applied upstream and it will be available d/s in 22.03 release