Bug 1951061

Summary: [RFE] Distributed SNAT on OVN
Product: Red Hat OpenStack Reporter: Ganesh Kadam <gkadam>
Component: puppet-ovnAssignee: OSP Team <rhos-maint>
Status: NEW --- QA Contact: Udi Shkalim <ushkalim>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: astupnik, francois.rigault, frigo, rhos-maint, sboyron
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: gkadam: needinfo? (rhos-maint)
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Comment 5 François Rigault 2022-02-21 05:32:37 UTC
what info is missing?

Comment 7 François Rigault 2022-03-12 07:07:02 UTC
Hi
I don't think there is much hope for this bz, from a [recent exchange][1]

> And OVN doesn't support distributed snat.  And I'm not sure if it is even possible (I could be wrong) 

I would like to ask a different question: is it possible to use IPv6 and not rely on any natting at all?

Something like:
- each routed subnet, or hypervisor, would have a prefix associated. This prefix would be used to pick up IPs for the VM running there...
- the egress traffic would leave through the hypervisor running the VM, without snat, so traffic is well distributed

[1]: https://mail.openvswitch.org/pipermail/ovs-discuss/2022-March/051754.html