Bug 1905118 - [TestOnly] Stateless security groups
Summary: [TestOnly] Stateless security groups
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: 17.1
Assignee: OSP Team
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On: 1827598
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-07 15:17 UTC by Karrar Fida
Modified: 2024-04-10 04:25 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1827598
Environment:
Last Closed: 2023-12-11 07:38:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NFV-1913 0 None None None 2022-01-06 14:45:48 UTC
Red Hat Issue Tracker OSP-1393 0 None None None 2021-11-18 15:10:10 UTC

Comment 1 Sanjay Upadhyay 2021-06-24 07:57:03 UTC
It is not clear on what is the feature and what needs to be tested. We would need more details. A conditional ack is provided for now.

Comment 2 Ihar Hrachyshka 2021-07-29 21:09:32 UTC
This feature is to support stateless ACL rules for OSP17+ and OVN. This is achieved by setting stateless=True for a security group. In which case, SG rules that belong to the group will be stateless (no connection tracking enabled). It should save some CPU cycles since conntrack tables are omitted. We expect to see somewhere around 10-15% bandwidth and latency savings, depending on protocol and scenario. Both stateful and stateless rules can be defined for a port (in OSP context they would have to belong to different SGs). All stateless rules take precedence over stateful rules (it's an implementation detail). 

Some info on neutron API here: https://docs.openstack.org/api-ref/network/v2/#stateful-security-groups-extension-stateful-security-group

This should now be available in OSP17. This should probably be moved to ON_QA, but I will let the assignee do it.

Comment 11 Gurpreet Singh 2022-10-19 02:31:35 UTC
Hi Eran

We will have to get this in 17.1 for Verizon as well. Going through their requirements, I see that they have explicitly listed it. To make their upgrade to 17.1 and OVN migration successful, we will have to support this.

If QE capacity is a challenge, we should escalate the concern now. 

Regards
Gurpreet

Comment 26 Red Hat Bugzilla 2024-04-10 04:25:02 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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