Bug 1951061 - [RFE] Distributed SNAT on OVN [NEEDINFO]
Summary: [RFE] Distributed SNAT on OVN
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-ovn
Version: 16.1 (Train)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Udi Shkalim
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-19 14:16 UTC by Ganesh Kadam
Modified: 2022-03-24 13:58 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
gkadam: needinfo? (rhos-maint)

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-3176 0 None None None 2021-12-01 04:03:11 UTC

Comment 2 François Rigault 2021-05-04 18:45:49 UTC 
fyi https://mail.openvswitch.org/pipermail/ovs-discuss/2021-May/051132.html
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
Note You need to log in before you can comment on or make changes to this bug.