[Neutron] Distributed Virtual Routing with OVN as Backend

Slawek Kaplonski skaplons at redhat.com
Fri Feb 12 20:15:01 UTC 2021


Dnia czwartek, 11 lutego 2021 22:39:29 CET Taha Adel pisze:
> Hello OpenStack Community,
> Let me introduce myself in brief first. My name is Taha and I'm a
> communications and electronics engineering student in the fourth year.
> My graduation project is to build a cloud infrastructure suited for
> Institutions and Universities to fully utilize the idle physical resources
> on the campus.
> I'm using OpenStack Platform as the cloud orchestrator, and I have a
> question regarding the Networking service in the cloud, Neutron. In my
> project, I want to use Distributed Virtual Routing for Layer three
> forwarding, floating IPs, and SNAT to limit the management overhead in the
> could and simplify the architecture. This design should end up with one
> controller node and a bunch of distributed compute nodes across the
> university. In my design, all compute nodes are attached to the provider
> network to allow N/S traffic in a distributed manner.
> The problem here is that I read in the OpenStack documentation that the
> SNAT traffic should always traverse through a centralized gateway node, and
> I need SNAT traffic as well as the other N/S traffic to be distributed
> across the compute nodes.
> So, the question here, is there any configuration that should let me
> fulfill this requirement?

If we are speaking about solutions which we have in upstream Neutron, so 
solution based on DVR L3 agent or OVN, both have SNAT traffic centralized 
Maybe You can look at some other plugins/drivers. Maybe some providers have 
distributed snat also. 

> Sorry for taking so long, and I appreciate your help in advance.
> Best regards.
> Taha Adel
> عدم التعرض للفيروسات www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai
> gn=sig-email&utm_content=webmail>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campa
> ign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Slawek Kaplonski
Principal Software Engineer
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210212/4d8b6b13/attachment.sig>

More information about the openstack-discuss mailing list